TL;DR:
On Saturday, April 18, a hacker attacked the bridge infrastructure of KelpDAO and manipulated the system to release 116,500 rsETH, equivalent to around $292 million and approximately 18% of the token’s circulating supply. Those tokens, issued without real backing, were immediately deposited into Aave to borrow genuine assets such as ETH and wETH. Fake tokens in, real money out.
Aave froze the rsETH markets on its V3 and V4 versions within hours. Its founder, Stani Kulechov, confirmed that the protocol’s contracts had not been compromised and that the exploit was external. The freeze halted the direct damage but triggered a chain reaction that no one clearly anticipated.
As news of the exploit spread, whales and institutional funds began withdrawing billions of dollars from Aave’s liquidity pools. According to analyst Duo Nine, figures such as Justin Sun and exchange MEXC pulled billions from the protocol within hours. The ETH pool was the first to reach 100% utilization, meaning no assets remained available for withdrawals. The wave quickly spread to the USDT and USDC pools, which also hit their cap. In total, over $6 billion left the protocol in less than 24 hours.
With funds locked and no direct withdrawal available, trapped depositors turned to the only exit at hand: borrowing against their own deposits. According to data from Chaos Labs, in the first 24 hours following the attack, nearly $300 million in new loans were generated using USDT as collateral.

“Basically you take a loan in GHO, DAI or USDe against your locked USDT or USDC,” Duo Nine explained. Aave allows borrowing up to 75% of the value of deposited collateral according to each asset’s risk parameters. That means accepting 75 cents on the dollar, at best, just to recover some liquidity.
Monetsupply.eth, head of strategy at the Spark protocol, noted that this dynamic worsened the problem: by draining other markets such as USDC and USDe, the desperate borrowing pushed those pools to their own utilization limits. The crisis spread from market to market, even as Aave’s core code remained intact and functioning as intended.