How Aave Recovered From Its $293M Bridge Exploit in 40 Days
On April 18, 2026, a single forged message inside a cross-chain bridge triggered what became the biggest decentralized finance exploit of the year. The target was not Aave's code. It was the bridge Aave trusted.
Kelp's LayerZero V2 bridge from Unichain to Ethereum was running a one-of-one verification setup, meaning one signer confirmed every cross-chain transaction. That signer got compromised through an RPC-poisoning attack. The result was 116,500 rsETH released onto Ethereum mainnet with no corresponding burn on the source chain. An attacker used those tokens as collateral on Aave and walked out with roughly $230 million in real assets.
What happened after is less covered but more important. Aave did not collapse. Within 90 minutes, the Protocol Guardian froze the affected markets. Within 48 hours, a coalition of DeFi protocols was already forming to restore backing for affected users.
That coalition, called DeFi United, eventually pulled together over $300 million in recovery commitments. Lido, EtherFi, Ethena, Mantle, KelpDAO, LayerZero, Compound, and Consensys all contributed. Aave Improvement Proposal 478 liquidated the attacker's eight positions on May 6. Five tranches of rsETH then refilled the LayerZero adapter between May 13 and May 26, restoring full backing.
Legal complications added a second layer. The Arbitrum Security Council had frozen 30,765 ETH from the attacker on April 21. In May, judgment creditors in an unrelated federal matter tried to seize it through a Manhattan court restraining notice. Aave LLC filed an emergency motion. That legal question was still open as of May 31.
The post-mortem Aave published this week covers the full incident timeline, the response actions, the five-tranche recovery, and the risk infrastructure improvements now underway. A new Technical Asset Listing Framework went to governance on May 28. A Bridge Assessment Framework is coming. The bug bounty was raised fivefold.
For anyone using DeFi lending or holding liquid restaking tokens, this incident is the clearest case study available on what bridge configuration risk actually costs in practice and what a coordinated DeFi recovery effort looks like when it has to move fast.
Read the full breakdown, including charts, the five-tranche timeline, and the legal update, at CryptoNewsLive.org.
Comments
Post a Comment