TL;DR: Web3 incident frequency hit a record high even as losses fell 57% to approximately $972 million, because attackers shifted toward more frequent and varied exploitation, according to FYEO. Web3 security now has to account for a broader mix of entry points and incident types.
Editorial analysis by NHI Mgmt Group, based on content published by FYEO: “Unpacking the $972M Crypto Loss in H1 2026: A Deeper…”.
By the numbers:
- Crypto losses fell 57% to approximately $972 million in H1 2026.
- The number of security incidents reached an all-time high in H1 2026.
Key questions
Q: Why do front-end and dependency weaknesses matter as much as smart contract bugs?
A: Because they often give attackers a path to the user, the wallet, or the project team before any contract logic is touched.
Q: What are the first controls to prioritise in a Web3 security programme?
A: Start with the controls that reduce access abuse and repeatable compromise: MFA, least privilege for operational accounts, dependency review, and monitoring for unusual transaction behaviour.
Q: How should Web3 teams respond when incident frequency rises but losses fall?
A: They should not treat lower losses as proof that controls are working.
Practitioner guidance
- Expand assurance beyond smart contracts Review front-end code, integrations, and third-party dependencies as part of the same security boundary as on-chain logic.
- Harden key and wallet access paths Treat operational wallets, signers, and administrative accounts as privileged assets with MFA, least privilege, and rapid revocation procedures.
- Increase detection for low-and-slow abuse Instrument monitoring to spot repeated smaller anomalies, unusual transaction patterns, and suspicious dependency behaviour before they accumulate into larger loss.
Bottom line: The core risk is no longer just large-scale theft. It is the growing number of smaller Web3 incidents that collectively weaken the environment.
Glossary terms: Web3 Operational Security, Front-end Vulnerability, Supply Chain Attack, Operational Wallet
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Web3 security is shifting from concentration risk to dispersion risk. The article shows that fewer catastrophic losses can coexist with more total incidents, which means the control problem is no longer only about stopping one major exploit. Teams need to understand the distribution of smaller failures across wallets, front ends, dependencies, and user workflows. Practitioner conclusion: security posture has to be judged by attack surface breadth, not just loss magnitude.
A few things that frame the scale:
- Organisations that rely heavily on static credentials reported a 20-percentage-point increase in security incidents compared with those with low reliance, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between on-chain security and Web3 operational security?
A: On-chain security focuses on the contract and protocol logic itself. Web3 operational security covers the people, tools, dependencies, wallets, front ends, and access paths that attackers often exploit first. Teams need both, because a secure contract can still be undermined by a compromised operational environment.
👉 Read our full editorial: Record crypto attacks outpace losses as web3 threats spread