Why can an audited smart contract still be exploited? An audit is a review of specified code, assumptions, and questions at a particular point in time. It can find important defects, but it cannot certify every interaction, deployment decision, market condition, or later code change. The useful question is not whether an audit “failed” in the abstract; it is what the review covered and what risks remained outside it.
An audit is a scoped review, not a permanent safety label
A code review can examine whether a contract implements its intended rules and whether an attacker might violate those rules. The audit report should identify the version or commit reviewed, the contracts in scope, assumptions, findings, and whether fixes were checked. A report for one implementation does not automatically cover a later implementation, a proxy’s current target, a front-end, an oracle, or another protocol the contract depends on.
Ethereum’s security guidance describes an audit as an additional round of independent review and cautions against treating it as a silver bullet. It recommends using audits alongside testing, static and dynamic analysis, and secure development practices. That distinction is practical: reviewers work within available time, code, documentation, tools, and stated scope. A finding can also be missed or misunderstood, and a fix can introduce a new interaction that was not part of the original design.
Euler’s 2023 exploit shows how a patch can change the risk
Euler’s first-party account of its March 2023 exploit describes a chain of events around its V1 lending protocol. The team says a first-depositor issue had been reported earlier and that a patch included a new donateToReserves function for certain existing markets. Euler says that solution was sent to an auditor and that the function was audited; the team later identified a missing health check in the function. The exploit used that missing check to put a position into an unhealthy state through a reserve donation.
This account is Euler’s own retrospective, so it should be read as a first-party description rather than an independent forensic report. It does not support the claim that “audited contracts are no safer” or that a particular audit provider was negligent. It does illustrate a narrower point: code added to fix one problem can create a new path through the system, and an audit cannot guarantee that every path or assumption has been identified.
That is why a reader should distinguish the code that was originally deployed from the patch, the exact markets affected, and the function involved in the exploit. Saying only “Euler was audited and hacked” leaves out the technical sequence and implies more than the evidence proves.
A cautious inference from this case is that reviewers need to trace patched code through the complete transaction flow, including how it changes balances and whether a resulting position remains healthy. Testing a function only against its intended use can miss a path created by interactions with other functions. The example does not establish that this was the only relevant control or that every audit should have caught the same issue; it shows why scope and test assumptions need to be explicit.
Risks can sit outside the reviewed contract
A contract may call another contract, rely on an oracle for prices, or route value through a bridge or lending market. Each dependency adds assumptions about data quality, permissions, liquidity, timing, and failure behavior. A review focused on the local code may not establish that the entire composed system behaves safely in every market condition.
Upgradeable systems add another question. In a proxy design, users continue interacting with one address while that proxy can route calls to an implementation contract. Ethereum’s documentation explains that upgrading can change the logic users interact with while preserving state. The review should therefore identify who controls upgrades, which implementation is active, how changes are authorized, and whether the deployed bytecode still matches the audited version. Admin key security and governance delays are part of the trust model, not details that an audit badge resolves.
Economic assumptions matter too. Code can follow its specified rules while those rules produce an unsafe result during a liquidity crunch, a price shock, or a series of unusual transactions. An audit of implementation correctness is not automatically an assessment of whether the protocol’s incentives, collateral parameters, or liquidation model remain robust under every scenario.
What a useful audit report can tell you
Look for the exact contracts and version in scope, the date of the review, the named assumptions, and a clear list of findings. Check whether critical and high-severity issues were fixed and whether the fix was reviewed. Compare the reviewed commit or deployed address with the code users will actually interact with. For an upgradeable system, check the active implementation and the permissions that can change it.
Then look beyond the report. Does the project run tests and monitoring? Is there a public process for reporting vulnerabilities? Are emergency controls documented, and who can use them? Can users see how upgrades are proposed or delayed? A bug bounty can invite more independent scrutiny, but its existence is not proof that no undiscovered bug remains. No single control replaces a layered security process.
What an audit does not prove
An audit does not prove that funds cannot be lost, that a project will recover from an exploit, that every dependency is safe, or that the current deployed code is the version reviewed. It also does not guarantee that a protocol’s incentives are sensible or that the people controlling upgrades will act in users’ interests. Those are separate factual questions and should be checked separately.
The most accurate way to describe an audit is as evidence about a defined review: who examined what, when, under which assumptions, and what remained unresolved. That information is valuable. Treating it as a blanket safety guarantee hides the limits that readers need in order to evaluate the system.
Related Articles
- How Do Crypto Bridges Work—and Why Are They Such a Hack Target?
- The Drift Protocol Exploit Explained: Durable Nonces, Social Engineering, and Recovery
- What Is MEV—and Why Every Ethereum Transaction Is a Game
Related Glossary Terms
See Also
Sources
- ethereum.org, “Smart Contract Security” — explains that audits add an independent review but cannot find every bug, and recommends layered testing and security practices.
- Euler Labs, “War & Peace: Behind the Scenes of Euler’s $240M Exploit Recovery” — Euler’s first-party account of the V1 patch, audit, missing health check, exploit, and recovery.
- ethereum.org, “Upgrading Smart Contracts” — describes proxy and other upgrade patterns and the trust and diligence questions they introduce.
- Trail of Bits / Crytic, “Building Secure Contracts” — provides complementary training and development guidance rather than comparative audit-failure statistics.