In the early hours of March 11, decentralized lending protocol Aave experienced a rare abnormal liquidation event. Without a market crash or external attack, approximately $27 million worth of lending positions were forcibly closed within hours. On-chain data shows 34 accounts holding a total of 10,938 wstETH were swept by liquidation bots.
CAPO Parameter Misalignment: Undervaluation by 2.85%
Chaos Labs, Aave's risk management partner, published a post-mortem on the governance forum revealing the root cause. The underlying oracle price feed was accurate; the culprit was an internal security module called CAPO (Capped Asset Price Oracle), designed to prevent price manipulation. This time, however, the 'guardian' itself triggered the liquidations.
CAPO relies on two parameters synced together: snapshotRatio (capped by on-chain constraints, max 3% increase every 3 days) and snapshotTimestamp (no equivalent rate limit). When misaligned, the computed 'maximum allowed rate' diverges from the true market price.
The misalignment unfolded as follows: the system attempted to update the snapshot ratio from approximately 1.1572 to the target 1.2282, but the rate constraint only allowed it to reach 1.1919. Simultaneously, the timestamp jumped without obstruction to a point corresponding to 7 days earlier. The parameters drifted apart, causing CAPO to calculate a maximum allowed wstETH price of roughly 1.1939, about 2.85% below the real market price.
E-Mode Amplification: Highly Leveraged Positions Breached
A 2.85% deviation might be noise for normal positions, but Aave's E-Mode (Efficiency Mode) allows users to borrow with significantly higher leverage, making positions extremely sensitive to price discrepancies. The systematic undervaluation pushed a batch of positions that were above safe thresholds into liquidation territory, and on-chain bots completed the rest.
Regarding profit flows, liquidators earned about 116 ETH in normal liquidation rewards. Another 382 ETH came from arbitrageurs exploiting the gap between the protocol's undervalued price and the market price. Combined, roughly 499 ETH (~$1.27M) left the affected user positions. The outcome at the protocol level was clean: zero bad debt, the pool remained intact, and losses were confined to the 34 liquidated addresses.
Chaos Labs Steps Up: Up to 345 ETH for Affected Accounts
Chaos Labs CEO Omer Goldberg stated clearly on X: "Every affected user will receive full compensation." He acknowledged the configuration error as a serious lesson and said the team would review parameter update procedures. For execution, Chaos Labs recovered approximately 141.5 ETH via BuilderNet, and together with Aave DAO treasury funds, the compensation cap is estimated at 345 ETH (~$870K) to cover all damaged accounts.
During emergency response, the team temporarily slashed the wstETH borrow cap on affected instances (Core and Prime) to 1, manually realigned the snapshot parameters via the Risk Steward mechanism, then restored caps to original levels (Core: 180k, Prime: 70k).
Not the First: DeFi Lessons from Oracle Misconfigurations
This is not the first time DeFi has been hit by an oracle issue. On February 18, lending protocol Moonwell priced cbETH at ~$1 (market ~$2,200) due to an oracle error, causing nearly $1.8M in bad debt. Earlier incidents like Mango Markets manipulation and the Euler Finance exploit left hundreds of millions in losses.
But this Aave incident is unique. The error didn't come from external data; it came from the protocol's own security layer built specifically to fight manipulation. That 'shield' became a blade under certain conditions. 'Code is Law' is the creed of decentralized finance—smart contract automation removes human intervention, but it also means any parameter misalignment can execute an irreversible action without the user ever noticing.