TL;DR: Q2 2026 saw roughly 70 DeFi exploits and $746 million in losses, with FYEO linking the damage to repeated control failures across contracts, oracle trust, and privileged authority. Protocols need continuous governance of logic, dependencies, and signer identities to contain blast radius after launch.
Editorial analysis by NHI Mgmt Group, based on content published by FYEO: “Q2 2026: DeFi Hacks Surge to All-Time High”.
Key questions
Q: Why do bridge attacks and oracle manipulation create outsized risk for DeFi protocols?
A: Bridge attacks and oracle manipulation are high impact because they can distort the rules that smart contracts rely on.
Q: What are the signs that privileged wallet governance is failing?
A: Warning signs include too few signers, unclear key ownership, manual emergency access that nobody tests, and upgrade authority concentrated in a small set of wallets.
Q: What breaks when DeFi protocols do not continuously govern contract and key risk?
A: The protocol may still function technically while becoming economically unsafe.
Practitioner guidance
- Audit contract logic on a recurring cycle Reassess core contracts after every material code change, dependency change, or governance update, and include cross-contract interactions in scope.
- Harden oracle-dependent decision paths Use redundant data sources, feed validation, and anomaly thresholds for any function that changes pricing, collateral, or liquidation state.
- Treat signer keys as privileged identities Map every upgrade, pause, treasury, and emergency key to an owner, rotation process, and revocation path, then test break-glass use.
Bottom line: The quarter’s record loss pattern shows that DeFi risk is driven by repeated control failures across contracts, oracle trust, and privileged authority.
Glossary terms: Smart Contract Vulnerability, Oracle Manipulation, Privileged Signer, Blast Radius
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
DeFi hack volume is now a governance problem, not just a code-quality problem. A quarter with roughly 70 exploits shows that protocol risk accumulates across contracts, governance flows, and operational access points. Traditional audit cycles can reduce defects, but they do not continuously govern the changing trust relationships that DeFi depends on. The practitioner conclusion is that control ownership must extend beyond code review into runtime governance.
A question worth separating out:
Q: Should teams prioritise audits or runtime monitoring for DeFi security?
A: They need both, but runtime monitoring deserves priority once a protocol is live. Audits reduce known defects before deployment, while monitoring detects exploitation patterns, price anomalies, and suspicious privilege use after release. In a fast-moving DeFi environment, the control that sees live state often determines whether loss is contained.
👉 Read our full editorial: DeFi hacks hit a record 70 exploits and $746 million lost