TL;DR: Operational compromises drove 74% of stolen crypto value in H1 2026, according to FYEO's analysis of Blockaid reporting. Signer access, deployments, and dependencies now need continuous governance because audits alone miss post-release drift.
Editorial analysis by NHI Mgmt Group, based on content published by FYEO: “Web3 Security Shifts: Infrastructure Failures &…”.
By the numbers:
- 74% of stolen crypto value in H1 2026 resulted from infrastructure and operational compromises, according to FYEO.
- The number of incidents recorded in H1 2026 was approximately 3.4 times the total for all of 2025, according to FYEO.
Key questions
Q: Why do compromised signers create more risk than isolated contract bugs?
A: A contract bug usually affects a specific code path, but a compromised signer can authorise many actions across the protocol.
Q: How can security teams tell whether dependency risk is being managed well in web3?
A: Look for a complete inventory of external services, explicit trust boundaries, and monitoring for changes in those dependencies.
Q: What breaks when a web3 protocol does not govern signer access properly?
A: The protocol can still be drained or altered even when the smart contract code is sound, because attackers abuse the signing path rather than the logic.
Practitioner guidance
- Implement signer lifecycle governance Inventory every signing key, multisig role, and delegated approval path, then assign owners, review cadence, and revocation rules.
- Map protocol dependencies and trust boundaries Document every bridge, oracle, node provider, identity service, and shared component that can affect transaction integrity or availability.
- Replace audit-only assurance with continuous monitoring Track changes in exposure, signer behaviour, dependency drift, and anomalous onchain activity after deployment.
Bottom line: Web3 loss events are increasingly driven by operational control failures rather than direct contract exploitation.
Glossary terms: Signer, Onchain Monitoring, Dependency Mapping, Post-Audit Exposure Drift
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Web3 has crossed from code risk into identity and operations risk. The report's central finding is that the dominant failure mode is no longer a contract flaw but a control failure around who or what can sign, deploy, or modify protocol behaviour. That is an identity governance problem as much as a blockchain security problem, because the approval path itself has become the attack surface. Practitioners should treat operational authority as the primary security boundary.
A question worth separating out:
Q: Should web3 teams rely on audits or continuous monitoring first?
A: Audits remain important, but they only prove a point-in-time view. Continuous monitoring is necessary when signers, dependencies, and deployments keep changing after release. Teams should use audits to validate architecture and monitoring to catch drift, because the highest-risk failures in this article come from operational change rather than static code defects.
👉 Read our full editorial: Infrastructure failures are driving most web3 crypto losses