Aave V3 Hack

TOTAL LOST $27.8M
High #181 All-Time CAPO Oracle Misconfiguration ethereum

Summarize with AI

Affected Chain ethereum Incident surface
Recovered - No recovery reported
All-Time Rank #181 By amount stolen
Auditors 1 Prior security audit

Incident Overview

Aave (AAVE) is a cryptocurrency and operates on the Ethereum platform. Aave has a current supply of 16,000,000 with 15,374,583.59191952 in circulation. The last known price of Aave is 110.50904122 USD and is down -6.73 over the last 24 hours.

It is currently trading on 1271 active market(s) with $374,012,733.12 traded over the last 24 hours. More information can be found at https://aave.com/.

Incident Report

Protocol / Project Aave V3
Date of Incident
Affected Chain(s) ethereum
Attack Technique CAPO Oracle Misconfiguration
Classification Ecosystem
Primary Source View Post-Mortem

Protocol Information

Protocol Type Lending
Smart Contract Language Solidity
Official Website aave.com/
Protocol Twitter/X @aave

Market Context at Time of Hack

Token Categories
DeFi DAO Ethereum Ecosystem Yield Farming Three Arrows Capital Portfolio Governance HECO Ecosystem Avalanche Ecosystem

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of capo oracle misconfiguration and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with ethereum smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Aave V3's contract logic - root cause: ecosystem
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Yes — skilled auditors routinely flag CAPO Oracle Misconfiguration vulnerabilities in code review
Audited by Audit Report 1 — still lost $27.8M. Prior audits don't guarantee safety, especially after post-audit code changes.

If you're auditing a protocol with similar architecture to Aave V3, these are the critical security checks that could have prevented this incident (March 2026).

  • Verify all logic paths related to CAPO Oracle Misconfiguration are guarded by proper access controls and input validation - see the Oracle Manipulation & Price Manipulation attack class for patterns
  • Audit oracle price feeds for manipulation risks - ensure time-weighted average prices (TWAPs) or multi-source aggregators are used, not spot prices
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Security Audit History

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Oracle Manipulation & Price Manipulation examples →

Sources & References

Learn to Prevent the Next Aave V3

The Aave V3 hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial