Crypto hacks remained a major risk in the first half of 2026, but there is no single industry-wide total. TRM Labs counted 207 hacks and about $972 million in losses, while CertiK and Global Ledger reported roughly $1.32 billion using broader or different datasets. The reports are not necessarily contradictory: they differ in what they classify as an incident, when they close their data, and whether they publish gross or adjusted losses.
The most reliable conclusion is therefore not one headline number. Across the reports, attacks were frequent, a small number of incidents caused a large share of the damage, and compromised wallets, signing systems, credentials, and other operational infrastructure remained especially costly.
Three reports, three counting methods
The following figures should be read within each publisher's own methodology. An incident count from one report should not be combined with the loss total from another.
| Publisher | Reported incidents | Reported losses | Important context |
|---|---|---|---|
| TRM Labs | 207 hacks | About $972 million | Hack-focused dataset; compares the total with $2.3 billion in H1 2025. |
| CertiK | 344 incidents | $1,315,676,432 gross; $1,200,364,925 after frozen or returned funds | Broader security-incident categories, including phishing and wallet compromise. |
| Global Ledger | 224 publicly disclosed hacks | About $1.32 billion | Emphasizes loss concentration, attribution, laundering, and recovery. |
What the TRM Labs dataset shows
TRM Labs recorded 207 hacks in H1 2026, the highest number in its six-month dataset, but estimated losses of about $972 million. Its comparison period, H1 2025, had approximately $2.3 billion in losses. This means a higher incident count did not produce a higher aggregate loss in TRM's data.
The quarterly breakdown also matters. TRM counted 123 incidents in Q2 2026. That figure replaces the unsupported Q2 count previously stated in this article.
TRM classified 125 of the 207 incidents as smart-contract exploits. Infrastructure and operational compromises represented about 15% of incidents but approximately 76% of losses. This distinction helps explain why incident frequency alone does not show the financial severity of a period.
Two April incidents involving Drift Protocol and Kelp were responsible for roughly $577 million in combined losses in TRM's account. TRM attributed about $643 million, or 66% of H1 losses, to actors linked to North Korea. Attribution can change as investigations develop, so these figures should be treated as the publisher's assessment rather than a permanent legal finding.
What the CertiK report adds
CertiK reported 344 security incidents and $1,315,676,432 in gross losses for H1 2026. After accounting for funds that were frozen or returned, its adjusted figure was $1,200,364,925. This gross-versus-adjusted distinction is one reason two accurate reports can show different totals.
CertiK's category data also gives a broader view of user and operational risk. It attributed $444,531,691 across 33 incidents to wallet compromise, $366,312,027 across 63 incidents to phishing, and $151,591,472 across 204 incidents to code vulnerabilities. These categories do not map directly onto every other publisher's taxonomy.
What the Global Ledger report adds
Global Ledger identified 224 publicly disclosed hacks with approximately $1.32 billion in losses. It found that the three largest incidents accounted for 63.9% of the total, reinforcing the importance of loss concentration when interpreting a six-month headline.
Its analysis also follows stolen funds beyond the initial exploit, including laundering routes, asset freezing, and recovery. That focus can produce a different view from a report designed primarily to count exploit events.
Why the totals differ
- Definitions: One publisher may count only hacks, while another includes phishing, wallet compromise, scams, or other security incidents.
- Gross versus adjusted losses: A headline may show the amount initially taken, or it may subtract funds later frozen, returned, or recovered.
- Disclosure and cutoff dates: Incidents can be discovered, confirmed, or reclassified after a report closes its dataset.
- Attribution: Links to a threat group or state actor are assessments based on evidence available at the time and may be revised.
- Coverage: Publishers use different monitoring systems, public disclosures, partner data, and thresholds for inclusion.
For comparison, always keep a report's incident count, loss figure, categories, and cutoff date together. Mixing fields from different datasets creates a number that no source actually reported.
Security checklist for crypto users
- Verify the exact website or app domain before connecting a wallet, entering credentials, or downloading software.
- Reject unexpected signature and token-approval requests. Read the asset, spender, amount, network, and action before confirming.
- Use a separate wallet for routine interactions and keep only the amount needed for the task in it.
- Review and revoke approvals that are no longer required, using a trusted explorer or the project's official tools.
- For material holdings, consider an offline or hardware signing setup and follow the device maker's official instructions.
- Keep recovery information offline and private. No legitimate support agent needs a seed phrase or private key.
- If a project reports an incident, pause interactions until its official channels publish clear remediation steps.
Security checklist for projects and teams
- Separate key generation, storage, transaction preparation, signing, and broadcasting where practical.
- Use strong authentication, hardware-backed credentials, least-privilege access, and documented staff offboarding.
- Apply multisignature controls, allowlists, transaction limits, and time delays according to the risk and operating model.
- Monitor front-end deployments, DNS, third-party scripts, cloud accounts, bridges, oracles, and other dependencies—not only smart contracts.
- Prepare an incident-response plan covering containment, evidence preservation, user communication, asset tracing, and recovery coordination.
- Treat audits as one control, not a guarantee. Reassess operational and infrastructure risks after code deployment.
Methodology and sources
This article compares figures as published by the original report authors and does not merge their datasets. Figures and source pages were reviewed on 11 November 2026. Later recoveries, reclassifications, or attribution updates may change the publishers' totals.
- TRM Labs: H1 2026 Crypto Hacks Reach Record High as Losses Fall Below $1 Billion
- CertiK: Hack3d H1 2026 Report
- Global Ledger: Crypto Hacks in H1 2026
For the user-side response after an exchange incident, see exchange hack response and user rights. The broader source-checked event list is in Crypto News in H1 2026.


