Aave suffers $27M liquidations after wstETH oracle config glitch
About $27 million of borrower positions were liquidated on DeFi lending protocol Aave on March 10 after a temporary pricing discrepancy involving Lido’s wrapped staked ETH token (wstETH). Blockchain-risk firm Chaos Labs flagged a spike in liquidations and later attributed the event to a configuration mismatch in Aave’s CAPO risk oracle: stale smart-contract parameters (an exchange rate and timestamp) were out of sync, which temporarily capped the allowed exchange rate for yield-bearing tokens. That caused wstETH to be valued about 2.85% lower than market, pushing some loans below collateral thresholds and triggering liquidations. Chaos Labs said no bad debt occurred; liquidators captured roughly 499 ETH in bonuses/profits. Market liquidity for wstETH was low (~$10M 24h volume) and Aave did not comment. Lido contributors said the issue was with the oracle mechanism, not wstETH or Lido. Past similar incidents (e.g., Moonwell misconfigured oracle valuing cbETH near $1) highlight how oracle/configuration errors can create outsized liquidations in DeFi. Key keywords: Aave, liquidations, wstETH, oracle glitch, CAPO risk oracle.
Neutral
This incident is primarily a technical/configuration failure rather than a fundamental collapse of Aave or wstETH. The direct market effect is limited: Chaos Labs reports no bad debt and liquidators captured the arbitrage, while Aave’s protocol remained solvent. Short-term impacts could include localized selling pressure on AAVE and wstETH as traders reassess risk, an increase in volatility for yield-bearing tokens, and heightened scrutiny of oracle and risk-parameter configurations across DeFi — potentially prompting temporary risk-off behavior. However, because the cause was an oracle configuration mismatch (not a market-driven price crash or protocol insolvency) and liquidity impact was moderate, long-term confidence in major liquid staking tokens and Aave is unlikely to be severely damaged if fixes and governance actions follow promptly. Historical precedent (e.g., Moonwell’s cbETH oracle mispricing) shows such events can cause sharp, short-lived dislocations and stricter oracle/risk controls afterward. Traders should expect short-term volatility and monitor protocol governance fixes, oracle parameter updates, and on-chain liquidator activity; the structural market impact should be neutral if remediation is effective.