Incident Overview
On April 18-19, 2026, Kelp DAO suffered a $292M exploit when an attacker forged a LayerZero message to mint unbacked rsETH (18% of total supply), deposited it as collateral across Aave, Compound, and Euler, then borrowed $236M in WETH. The attacker now holds massive debt positions across multiple lending protocols, creating what analysts call a "collateral contagion event" affecting the entire DeFi ecosystem.
The attacker forged a LayerZero cross-chain message to mint rsETH tokens without any backing. This created 18% of the entire rsETH supply from nothing. They immediately took these worthless tokens to major lending protocols and deposited them as collateral. Aave, Compound, and Euler all accepted the rsETH at face value, treating this bridge-dependent asset like native ETH.
The attacker borrowed over $236M in WETH against the fake collateral across Ethereum and Arbitrum. They became the #8 largest WETH borrower on Aave Ethereum ($123M debt) and #4 largest on Aave Arbitrum ($22M debt). Now they hold 106,466.7 ETH worth about $250M while the lending protocols are stuck with massive bad debt they cannot recover. The unbacked rsETH collateral is essentially worthless, but the borrowed WETH is very real and already extracted.
This created systemic risk across DeFi lending markets. Multiple major protocols are now exposed to this bad debt simultaneously. The exploit demonstrates how a single forged cross-chain message can cascade through the entire ecosystem when lending markets treat bridged assets as equivalent to native tokens.
Incident Report
Protocol Information
What the Attacker Needed to Succeed
Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.
What Auditors Should Check
If you're auditing a protocol with similar architecture to Kelp DAO, these are the critical security checks that could have prevented this incident (April 2026).
- Verify all logic paths related to Access Control are guarded by proper access controls and input validation - see the Access Control Attacks attack class for patterns
- Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs
Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.
Free TrialRelated Attack Classes
The technique used in this hack maps to these vulnerability classes in our security curriculum:
Sources & References
Learn to Prevent the Next Kelp DAO
The Kelp DAO hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.