Kelp hack drains $294M from DeFi

TLDR

Kelp DAOs rsETH bridge was exploited, letting attackers mint fake tokens and drain around $292294 million, triggering a liquidity shock across major DeFi lending protocols.

1. Attackers abused Kelps LayerZero-based bridge and a single-verifier setup to forge cross-chain messages and mint about 116,500 unbacked rsETH, worth roughly $292 million.
2. The fake rsETH was used as collateral on Aave and other lenders, creating around $195236 million in bad debt and driving multi-billion dollar outflows from DeFi.
3. The incident highlights bridge and configuration risk, non-isolated lending risk, and why users should be cautious with bridged and liquid restaking collateral until new safeguards are in place.

Deep Dive

1. How The Exploit Worked

Kelp DAO issues rsETH, a liquid restaking token users receive when they restake ETH and then use across DeFi. Its rsETH bridge relied on LayerZero messaging with a single verifier configuration.

Investigations report that attackers compromised infrastructure feeding LayerZeros verifier and then forged cross-chain messages, letting them mint 116,500 rsETH without backing, about 18 percent of supply and roughly $292 million in value. This 1 of 1 verifier setup is identified as the key weakness in analyses by outlets like CoinDesk and CCN.

Kelp paused rsETH contracts within roughly an hour, but by then the unbacked tokens had been moved and used elsewhere, so the core loss was locked in.

2. Knock On Effects For Aave And DeFi

Once the fake rsETH existed, the attacker deposited it as collateral on Aave V3 and other lenders like Compound and Euler, borrowing large amounts of WETH and other assets against what looked like valid collateral.

Analysts estimate Aave alone ended up with about $196236 million in bad debt, while ETH and stablecoin markets on Aave hit near 100 percent utilization, freezing withdrawals and forcing the protocol to halt rsETH and related markets across several chains. A detailed breakdown of the resulting liquidity crunch and blocked withdrawals is provided in this CCN explainer.

Across DeFi, total value locked dropped roughly 67 percent in a day, as users rushed to pull funds from protocols that touched rsETH or shared similar bridge risk.

3. Lessons For Users And Builders

This was not a classic smart contract bug in Aave or Ethereum but a failure in bridge and verifier configuration. A single misconfigured bridge became a system wide risk once its token was widely accepted as collateral.

For lending protocols, the episode shows how non-isolated lending and aggressive onboarding of complex assets can turn a niche integration into protocol level bad debt. Risk teams are now debating stricter caps, isolated markets for bridged and restaking tokens, and mandatory multi-verifier bridge setups.

LayerZero has stated it will no longer support single-verifier configurations, and several security analyses now treat the Kelp case as a reference example of infrastructure level attack paths, with some attributing it probabilistically to North Koreas Lazarus Group as described in post incident reports.

Conclusion

The Kelp DAO hack shows how one poorly secured bridge can mint fake collateral, drain real assets, and rapidly stress even battle tested lenders like Aave. Until bridge designs, verifier setups, and asset listing standards catch up, the main defense for users and protocols is stricter collateral selection and tighter limits on complex cross-chain assets.