Core Insights - A misconfigured Oracle system in Aave led to $27 million in forced liquidations on March 10, undervaluing wrapped staked Ether by 2.85% against its actual market rate [1] - The incident involved 34 high-leverage E-Mode positions being liquidated due to a significant gap between the applied exchange rate and the live on-chain rate [1][3] Liquidation Details - The liquidation resulted in the loss of 10,938 wstETH, with liquidation bots capturing 499 ETH in profits, approximately $1.2 million [2][3] - Aave confirmed that it incurred no bad debt from the incident and is working to compensate all affected users [2][3] Recovery Efforts - Aave managed to recapture 141 ETH ($285,000) through BuilderNet refunds and an additional 13 ETH in liquidation fees, which will be used to compensate affected users [4] - The DAO treasury will cover any remaining shortfall up to the full 345 ETH identified as excess liquidation windfall [4] Incident Analysis - Lido contributors clarified that the issue was not related to wstETH or the Lido staking protocol, but was entirely due to Aave's oracle configuration layer [5] - Chaos Labs confirmed that the incident was a result of an on-chain configuration misalignment, not a design flaw in the CAPO system or Aave's core oracle infrastructure [6] Response and Remediation - Chaos Labs quickly contained the situation by reducing borrow caps on wstETH and manually realigning snapshot parameters to restore oracle accuracy [7] - Aave's configuration issue was remediated by the time the post-mortem was published, highlighting the team's effective response in limiting broader DeFi risk contagion [7]