TL;DR: Less than 10% of DeFi issues in the past year were due to code base problems, according to FYEO citing Isaac Patka, shifting attention toward operational failures, phishing, supply chain weaknesses, oracle manipulation, and weak incident response. Code audits alone do not close the real loss pathways in DeFi; error correction and operational controls now define the security baseline.
Editorial analysis by NHI Mgmt Group, based on content published by FYEO: “DeFi Requires Error Correction, Operational Security…”.
By the numbers:
- Less than 10% of DeFi issues in the past year were due to code base problems.
Key questions
Q: Why do smart contract bugs create such large losses in DeFi?
A: Because the contract is the control plane for value movement, a flaw in permissions or state logic can be executed at machine speed across many transactions.
Q: How can DeFi teams know whether error correction controls are actually working?
A: Test whether approvals, time-locks, alerting, and pause mechanisms can interrupt a harmful sequence before settlement or widespread impact.
Q: What breaks in DeFi when teams rely on audits instead of operational controls?
A: Audits can validate contract logic, but they do not stop key compromise, bad approvals, oracle manipulation, or unsafe deployment workflows.
Practitioner guidance
- Map the full DeFi attack surface Review administration, key handling, upgrade paths, oracle inputs, third-party dependencies, and incident response as one control environment rather than separate workstreams.
- Deploy runtime containment controls Use multi-signature approvals, time-locks, and circuit breakers for high-risk actions so a bad transaction can be delayed or stopped before settlement.
- Harden operational workflows Restrict who can deploy, upgrade, and move assets, and require explicit approvals for sensitive actions that could change protocol behaviour.
Bottom line: The article argues that DeFi losses are driven more by operational breakdowns than by direct code defects, which changes where security teams should focus.
Glossary terms: Operational security, Error Correction Mechanism, Oracle Manipulation, Multisignature Approval
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Operational security is the real DeFi control plane. The article's central claim is that code defects account for a minority of losses, which means the dominant risk sits in administration, monitoring, deployment discipline, and recovery design. That shifts security ownership away from audit-only thinking and toward full lifecycle governance. For practitioners, the lesson is that DeFi risk is an operating model problem before it is a code problem.
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 should teams do after a DeFi protocol admin path is compromised?
A: Contain the active path first by revoking or gating the affected permissions, pausing sensitive workflows where possible, and checking whether any pending upgrades or transfers can still be blocked. Then validate dependencies, oracle inputs, and signer integrity before resuming operations. Recovery should focus on preserving control, not restoring speed.
👉 Read our full editorial: Operational security now outweighs code flaws in DeFi losses