The decentralized finance ecosystem is still reeling from one of the most surgically executed attacks in its history. On April 18, 2026, an attacker exploited Kelp DAO’s LayerZero-powered cross-chain bridge to mint 116,500 unbacked rsETH tokens — worth approximately $292 million — before emergency measures could halt the drain. Two days later, as the dust settles and on-chain forensics paint a clearer picture, the exploit stands as a stark reminder that DeFi’s security is only as strong as its weakest verification layer.
The Exploit Mechanics
The attack targeted Kelp DAO’s rsETH adapter, the cross-chain component that allows users to deposit liquid staking tokens like stETH or cbETH and receive rsETH in return. According to blockchain security analysts, the attacker compromised the RPC nodes used by LayerZero’s Decentralized Verifier Network (DVN). The critical vulnerability was a 1-of-1 DVN verification configuration — meaning a single compromised verifier was sufficient to approve fraudulent cross-chain messages.
The attack chain was multi-layered. First, the threat actor tainted internal RPCs while simultaneously launching a distributed denial-of-service attack against external verification infrastructure. This forced the system to fall back to the compromised nodes, which then accepted forged cross-chain messages. The result was the minting of 116,500 rsETH with zero backing — roughly 18% of the token’s circulating supply.
The attacker funded gas fees through Tornado Cash, the cryptocurrency mixer frequently used to obscure transaction origins. The funds were quickly swapped back to Ethereum and Arbitrum, with the attacker depositing nearly 90,000 rsETH into Aave as collateral to borrow approximately $190 million in ETH and other assets. Security firm Cyvers confirmed the attack and attributed the funding trail to North Korea’s Lazarus Group.
Affected Systems
The blast radius extended far beyond Kelp DAO itself. At least nine DeFi protocols were directly affected by the exploit. Aave, the world’s largest DeFi lending protocol, froze rsETH markets on both Aave v3 and Aave v4 after discovering the attacker had used the unbacked tokens as collateral. Aave’s total value locked plummeted by $10 billion as lenders rushed to withdraw available funds in what became a cascading liquidity crisis.
Other major DeFi tokens felt the shockwaves. stETH and wstETH dropped nearly 4%, while Aave’s native AAVE token fell 10% within 24 hours. The contagion spread across more than 20 Layer-2 networks where rsETH had been integrated as collateral. Bitcoin, trading at approximately $75,872, held relatively steady, but the broader DeFi ecosystem experienced a crisis of confidence.
Kelp DAO’s own exposure was enormous. The protocol had amassed over $2 billion in total value locked before the exploit, with rsETH having crossed $1 billion in TVL and integrated across Aave, Arbitrum, Base, Linea, and Mantle. The interconnected nature of these integrations amplified the damage exponentially.
The Mitigation Strategy
Kelp DAO’s emergency pauser multisig activated 46 minutes after the initial exploit at 18:21 UTC on April 18, pausing core rsETH contracts. Two subsequent drain attempts at 18:26 and 18:28 UTC — each targeting an additional 40,000 rsETH — were successfully reverted. The speed of the initial response, while commendable, underscores a fundamental problem: 46 minutes is an eternity in blockchain time.
A recovery initiative dubbed “DeFi United” was launched in the aftermath, with Lido Finance, EtherFi, and Aave founder Stani Kulechov coordinating efforts to cover the collateral shortfall. Aave’s governance forum activated emergency procedures to isolate the impaired positions and protect remaining depositors.
On-chain investigators confirmed that wallets linked to the hack have begun moving funds through THORChain and mixing services, suggesting the laundering process is already underway. The scale and sophistication of the operation aligns with the operational patterns of state-sponsored threat groups.
Lessons Learned
The Kelp DAO exploit exposes a systemic weakness in cross-chain infrastructure: single-point-of-failure verification. A 1-of-1 DVN configuration for a protocol managing over $2 billion in assets represents a catastrophic misjudgment of risk. Multi-signature verification with geographic and operational diversity should be the absolute minimum for any bridge handling significant value.
Secondly, the speed of exploitation versus response remains fundamentally asymmetric. The attacker completed the entire minting-and-collateralization sequence in under an hour, while the emergency pause required multisig coordination across time zones. Automated circuit breakers with on-chain thresholds could reduce this gap dramatically.
Third, the cascading effect on Aave demonstrates the interconnected risk in DeFi. A vulnerability in one protocol’s bridge infrastructure can threaten the solvency of an entirely separate lending platform. Cross-protocol stress testing and collateral haircut mechanisms deserve far more attention than they currently receive.
User Action Required
If you hold rsETH or have exposure to any protocol that accepted rsETH as collateral, you should immediately verify your positions. Check Aave’s official channels for updates on the rsETH market freeze and any recovery distributions. Avoid interacting with any rsETH contracts until Kelp DAO publishes a full post-mortem and remediation plan. Monitor on-chain tracking services for updates on the stolen funds, and exercise extreme caution with any cross-chain bridge that relies on single-verifier configurations. The era of trusting bridges by default is over — verify the verification layer itself.
Disclaimer: This article is for informational purposes only and does not constitute financial advice. Always conduct your own research before making investment decisions.
attacker deposited 90K rsETH into Aave as collateral to borrow $190M more. using stolen assets as collateral to steal more is next level deFi inception
Petra Novotna depositing stolen rsETH into Aave as collateral is wild. the attacker understood defi composability better than the team that got hacked
depositing stolen rsETH into Aave as collateral to borrow $190M more is exploit composability. the attacker used DeFi legos against itself better than any dev team
Real-time monitoring tools are getting better at catching exploits early
Isabella Conti real-time monitoring caught the attack after the funds were already deposited into aave as collateral. monitoring is necessary but reactive, not preventive
The cost of a security breach always exceeds the cost of prevention
Social engineering attacks are becoming more sophisticated
Formal verification should be mandatory for high-value protocols
Tomasz Kowal formal verification is table stakes for anything handling $292M. but the real failure was 1-of-1 DVN config. single point of failure on a bridge that size is criminal negligence
1-of-1 DVN for a protocol handling $292M is like putting a padlock on a bank vault. adding a second verifier costs nothing and prevents exactly this
dvn_audit_ 1-of-1 DVN verification for a protocol handling hundreds of millions. the cost of adding a second verifier would have been negligible compared to the $292M loss
bridge_inspector 1-of-1 DVN for $292M is criminal negligence. a 3-of-5 config costs almost nothing and prevents exactly this attack vector