Kelp DAO Loses $292 Million in DeFi Protocol Hack

Kelp DAO DeFi hack $292 million exploit visualization

Kelp DAO, a liquid restaking protocol built on Ethereum, suffered one of the largest DeFi exploits of 2026 when an attacker drained approximately $292 million from its smart contracts. The incident marks a significant blow to the growing restaking sector and raises renewed questions about smart contract security in decentralized finance.

What Happened in the Kelp DAO Exploit?

The attacker exploited a vulnerability in Kelp DAO's reward distribution mechanism, manipulating the protocol's accounting logic to withdraw far more funds than they had deposited. On-chain analysis revealed a flash loan attack that amplified the exploit, allowing the hacker to drain multiple pools within a single transaction block. Security firm PeckShield confirmed the attack within hours of its occurrence.

Impact on the Restaking Ecosystem

The hack sent shockwaves through the broader restaking ecosystem. Competing protocols including EigenLayer and Renzo saw temporary liquidity outflows as users moved funds to safer alternatives. The rsETH token issued by Kelp DAO depegged significantly from ETH following the news, dropping by over 40% before partial recovery. The incident highlights the compounding risks inherent in restaking, where assets are staked multiple times across protocols.

Kelp DAO's Response and Recovery Plans

The Kelp DAO team swiftly paused all protocol functions and began working with security auditors to identify the full scope of the exploit. The team published a post-mortem within 24 hours and announced a compensation plan for affected users. Law enforcement has been engaged, and blockchain forensics firms are actively tracing the stolen funds across multiple wallets and bridges.

The Bottom Line

The Kelp DAO hack underscores that even well-audited DeFi protocols remain vulnerable to sophisticated exploits. As restaking protocols accumulate larger pools of assets, they increasingly become high-value targets. Users and developers alike must weigh the yield opportunities against the heightened security risks that come with complex protocol interactions.

Related Articles

Sources