A quarterly finding, reported on October 15

Cointelegraph’s October 15 coverage of Hacken’s Q3 report describes 107 recorded incidents with gross losses of about $1.18 billion. According to that coverage, approximately 77% of the losses involved compromised suppliers, developer tooling, unimplemented fixes or other components outside security reviews. The reporting period is the third quarter; this is not a claim that all those funds were stolen on October 15.

The report also distinguishes returned or reversed funds from compensation paid by operators. Those are different outcomes: a customer may be reimbursed while the original stolen assets remain unrecovered. Chain Daily is reporting the published findings, not independently auditing each incident or reproducing the report’s full incident database.

Why a contract audit does not cover the whole journey

A wallet user interacts with more than a blockchain contract. A website prepares a transaction, software interprets it, a device displays or signs it, and sometimes an outside service supplies data. A security assessment of one component does not automatically establish the integrity of every component in that chain.

That is the useful question behind the quarterly total: what did a particular audit actually examine, and when? An old audit badge on a new interface is not a complete answer. Likewise, an unchanged recovery phrase does not establish that every approval signed with that wallet was safe. These are separate failure paths and call for different checks.

What to look at before the next signature

Use a known publisher’s distribution and update channels, and compare the transaction’s destination and requested permissions with the action you intended. A routine purchase should not become an unexplained request to hand over a recovery phrase. If a service announces an incident, its specific affected versions, contracts and official remediation instructions matter more than a generic social-media warning.

Avoid interpreting the aggregate loss number as evidence that a particular unaffected wallet is compromised. Nor does the number prove that every user will be reimbursed after a future incident. The reader’s task is to identify the product, software and permissions actually involved. This article does not name a newly affected device or ask anyone to migrate funds through a link.

Original source

Cointelegraph / Hacken — External source
Event / reporting period
2026-Q3
Report published
Source checked

AI-assisted text and translations based on the linked sources. No affiliation with the companies covered.

Information only. Not investment advice. Cryptoassets can lose value; availability and fees vary by provider and region.