What Happened in the Kelp DAO Exploit?
An attacker drained 116,500 rsETH from Kelp DAO’s LayerZero-powered cross-chain bridge on Saturday, with the stolen funds valued at approximately $292 million. Onchain data shows the exploit was executed through a call to LayerZero’s EndpointV2 contract, triggering Kelp’s bridge to release funds to an attacker-controlled address.
The attacker wallet had been funded roughly 10 hours earlier via Tornado Cash, a pattern commonly observed in DeFi exploits to obscure transaction origins. Blockchain investigator ZachXBT noted, “KelpDAO appears to have had $280M+ stolen one hour ago on Ethereum and Arbitrum,” adding that “the attack addresses were funded via Tornado Cash.”
The scale of the breach is material relative to the token’s supply. The stolen amount represents roughly 18% of rsETH’s circulating supply, which is deployed across more than 20 networks, amplifying the potential impact across ecosystems.
How Did Kelp and the Ecosystem Respond?
Kelp DAO activated its emergency controls approximately 46 minutes after the initial exploit. The protocol’s pauser multisig froze core contracts, halting further activity across components including deposits, withdrawals, oracle functions, and the rsETH token itself.
“Earlier today we identified suspicious cross-chain activity involving rsETH,” Kelp said in its first public statement. “We have paused rsETH contracts across mainnet and several L2s while we investigate.”
Two additional attack attempts shortly after the initial drain failed, indicating the pause mechanism prevented further losses. Both transactions attempted to extract an additional 40,000 rsETH, which would have pushed total losses toward $391 million.
The exploit appears to center on Kelp’s LayerZero Omnichain Fungible Token bridge, a key component enabling rsETH transfers across chains. Kelp said it is working with LayerZero, Unichain, and security partners to determine the root cause.
Investor Takeaway
What Are the Implications for Aave and DeFi Lending?
The impact quickly extended beyond Kelp DAO. Aave froze rsETH markets on both its V3 and V4 deployments, seeking to contain potential contagion from undercollateralized positions tied to the exploited asset.
“We are reviewing information about rsETH borrows on Aave that occurred after the exploit and will share more details as soon as possible,” Aave said. “If the protocol accumulates bad debt from this incident, we’ll explore paths to offset the deficit.”
The incident triggered a market reaction, with AAVE declining around 10% as concerns emerged over potential bad debt exposure. While Aave clarified that its own smart contracts were not compromised, the event highlights how external asset failures can propagate risk into lending protocols.
Such spillover effects are a recurring feature in DeFi, where composability links protocols through shared collateral and liquidity pools.
Investor Takeaway
Is This Part of a Broader Pattern?
The exploit marks the second security incident involving rsETH within 12 months. In April 2025, Kelp DAO paused operations after a bug in its fee contract led to excess token minting, though no user funds were lost at the time.
The recurrence of issues around the same asset raises questions about the robustness of its underlying architecture, particularly as it scales across multiple chains and integrates with other DeFi protocols.
The situation remains under investigation, with further details expected as Kelp DAO and its partners complete their analysis.
