TL;DR: Valid signatures still led to unsafe outcomes in 2026, Hypernative reports, across Drift, Hyperbridge and Kelp DAO's combined $578 million in losses. DeFi protocols need hard limits on privileged actions so authentication cannot trigger oversized mints, admin changes or withdrawals on its own.
Editorial analysis by NHI Mgmt Group, based on content published by Hypernative: “Valid Signatures, Invalid Outcomes: What 2026's Biggest Hacks Have in Common”.
By the numbers:
- Drift Protocol lost $285 million.
- Kelp DAO lost $292 million and triggered $13 billion in DeFi withdrawals over the 48 hours that followed.
Key questions
Q: Why do audits miss some onchain attack paths?
A: Audits usually confirm that code behaves as written, but they do not keep pace with changing governance settings, signer sets, challenge windows or execution thresholds.
Q: How do security teams tell whether policy enforcement is working in a protocol?
A: Look for evidence that unsafe transactions are blocked before state changes occur, even when authentication or proof verification succeeds.
Q: What breaks when a protocol trusts valid signatures without constraining the resulting action?
A: Authentication can still succeed while the protocol enters an unsafe state.
Practitioner guidance
- Define execution limits for privileged actions Set hard constraints on actions that can mint, withdraw, reconfigure or change governance state so a valid authorization cannot produce an unsafe outcome.
- Review governance parameter drift continuously Track timelocks, signer composition, challenge periods and market thresholds as living controls, not one-time audit artifacts.
- Add supply and value reconciliation checks Require onchain checks that compare requested value movement against source balances, supply ceilings and protocol-specific invariants before execution.
Bottom line: The article’s central risk is not broken verification but trusted execution without enough constraints on the resulting state change.
Glossary terms: Operational Envelope, Bounded Authorisation, Policy Enforcement Layer, Governance Evidence Drift
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Authentication without bounded authorization is the real failure mode here. These incidents show that proving who signed, verified or attested is no longer enough when the resulting action can still create unsafe protocol state. The industry has over-invested in identity proof and under-invested in execution constraints. Practitioners should treat this as a governance design problem, not a signer quality problem.
A question worth separating out:
Q: What should teams do when privileged actions can change protocol state too freely?
A: Reduce the blast radius by separating permission to act from permission to change state, then define caps, delays and reconciliation checks around the highest-risk functions. The point is to make unsafe outcomes impossible or at least non-trivial, even when the actor is legitimate. That is a governance design choice, not just an operational one.
👉 Read our full editorial: Authorized actions without bounded policy drive 2026 DeFi losses