Attackers drained roughly $292 million from KelpDAO’s bridge this month, then used the launched tokens as collateral on lending protocols that have been by no means initially hacked. The result’s a textbook instance of how one failure can unfold by way of DeFi — and why that issues as extra tokenised belongings transfer into wider markets.
On April 18, 2026 attackers exploited KelpDAO’s cross-chain bridge and drained roughly $292 million in rsETH, a liquid restaking token. The assault is being described as the most important DeFi exploit of the 12 months up to now — simply the newest in a collection of incidents to have earned April its place as the worst month of the 12 months thus far for the sector, with losses estimated at over $600 million.
The theft itself, nonetheless, was solely the beginning. Inside hours, the stolen tokens have been getting used as collateral throughout a few of DeFi’s largest lending protocols — protocols that had nothing to do with the unique assault and are actually left holding collateral that not represents what the market as soon as assumed.
That is what makes the Kelp episode way more than simply one other bridge exploit. It’s, in truth, a textbook instance of how shortly harm can transfer by way of DeFi as soon as an asset that also appears legitimate on-chain enters the broader system. It additionally exhibits simply how tough it may be to evaluate the true soundness of a token when the proof of that soundness sits on one other protocol.
For establishments more and more exploring DeFi, tokenisation and on-chain settlement, the structural warning is evident: the weakest level might not sit out there you may see, however within the infrastructure hidden beneath the floor.
KelpDAO’s Single Level of Failure
KelpDAO, a restaking protocol, points rsETH, a liquid restaking token representing ETH staked by way of EigenLayer. To maneuver rsETH between chains, it used LayerZero’s messaging infrastructure. The exploited route relied on a 1-of-1 Decentralised Verifier Community (DVN) setup, which means a single verifier was accountable for approving cross-chain messages earlier than tokens have been launched on Ethereum.
Reasonably than attacking Kelp’s core restaking contracts, the attackers focused the infrastructure feeding knowledge into that verifier. They compromised two RPC nodes utilized by the DVN and changed their software program with variations that reported false transaction knowledge. They then launched a distributed denial-of-service (DDoS) assault towards the remaining clear nodes, forcing the verifier into failover in order that it was studying solely the poisoned sources.
That, in impact, triggered the verifier to simply accept a cast message claiming rsETH had been burned on the supply chain and could possibly be launched on Ethereum. Kelp’s bridge contract then launched 116,500 rsETH — roughly 18% of circulating provide — to an attacker-controlled deal with, regardless of there being no corresponding backing. Inside hours, they have been being moved into different elements of DeFi.
Kelp and LayerZero are nonetheless publicly disputing accountability. LayerZero says it warned KelpDAO to undertake a multi-verifier setup. KelpDAO says the 1-of-1 verifier configuration matched LayerZero’s personal default documentation and quickstart information. LayerZero has since stated it’s going to not signal messages for any software utilizing a single-verifier configuration.
That debate issues for governance and for the narrower query of who ought to bear the losses.
It doesn’t, nonetheless, change the truth that the unbacked rsETH nonetheless appeared legitimate on-chain and was in a position to be moved, deposited and accepted by different protocols. rsETH’s credibility trusted infrastructure that extraordinary market checks didn’t seize.
The token had liquidity, a worth and integration throughout main protocols. What it didn’t have was sufficient redundancy within the layer that decided whether or not the ETH it represented was truly there.
That’s the place the exploit stopped being a Kelp downside and have become a headache for the broader market.
The place the Harm Landed
As soon as the tokens had been launched, the attacker didn’t merely dump them into the market. They used them as collateral.
Aave, DeFi’s largest lending protocol, seems to have been probably the most uncovered. The attacker proceeded to make use of the unbacked rsETH there to borrow roughly $190 million in wrapped ether (WETH), triggering a pointy withdrawal of liquidity as soon as the dimensions of the issue turned clear.
The important thing distinction is that Aave itself was by no means hacked. Its contracts truly labored precisely as designed. Even so, it was left holding collateral that not represented what it appeared.
An incident report from Aave Labs and LlamaRisk estimates dangerous debt on Aave will run to between $123.7 million and $230.1 million, relying on how the shortfall is finally allotted. If losses are unfold throughout all rsETH holders, the harm will likely be smaller however shared extra extensively. If they’re as an alternative remoted to Layer 2 networks, the losses there will likely be concentrated and extreme.
Nevertheless the fallout is managed, one of many key classes is that after dangerous collateral enters the broader market, the ultimate end result is not nearly code.
How Kelp Grew to become Everybody Else’s Downside
DeFi’s composability is normally offered as one in all its essential strengths — the concept that one protocol’s output turns into one other’s enter, permitting belongings to maneuver throughout venues and capital to be reused extra effectively.
Kelp exhibits the flip facet of that design.
rsETH was not an obscure token sitting on the edges of the market. It was built-in throughout a number of protocols, accepted by threat frameworks, priced by oracles and utilized by depositors in numerous leveraged methods. As soon as the bridge launched unbacked rsETH, each venue that handled it as a legitimate illustration of staked ETH inherited publicity to one thing that not existed.
In some ways, composability labored precisely as designed, simply within the mistaken course. Sound inputs make the system extra environment friendly however when an enter breaks the harm inevitably flows throughout the identical connections.
Lending is within the highlight this time as a result of the exploit focused lending protocols, and lending is the place damaged assumptions a few token create the quickest and most measurable losses.
The underlying failure is greater than lending, although. It started earlier, on the level the place the token stopped representing what the market thought it did.
Why It Issues Past DeFi
The fast losses of the KelpDAO exploit sit with DeFi-native contributors. The failure mode Kelp uncovered, nonetheless, will not be unique to DeFi lending.
Any tokenised asset carries an implicit declare: that the token represents the asset behind it. That declare solely holds if the infrastructure linking the token to its backing stays sound. In rsETH’s case, that hyperlink broke, regardless that the token nonetheless appeared legitimate on-chain.
The enchantment of tokenised markets lies exactly in issues like programmable collateral, quicker settlement and round the clock liquidity. However in addition they require extra worth to maneuver throughout shared rails and thru infrastructure layers that many markets nonetheless deal with as secondary.
This can matter more and more past DeFi-native markets, and there are already recommendations that the fallout might sluggish institutional tokenisation efforts as safety dangers are reassessed. That isn’t shocking — in spite of everything, tokenised bonds, deposits and different real-world belongings are transferring into environments the place contributors, particularly establishments, must belief that the token truly stands for what it says it does.
The method of injury management is already spreading past Aave. Arbitrum, one other of the Layer 2 networks affected by the fallout, moved this week to freeze roughly 30,766 ETH linked to the assault by way of motion by its Safety Council. That will assist scale back remaining losses, however it’s additionally a reminder that after failures like this unfold, the result is not formed by code alone, but in addition by governance and emergency intervention — choices that stay extremely contentious in methods that declare to be decentralised.
Whereas the KelpDAO exploit doesn’t present that tokenised belongings are inherently unsound, it does present that the credibility of any token finally rests on infrastructure that always sits under the extent most markets actively assess.
As soon as that infrastructure fails, the harm doesn’t keep native. It spreads by way of composable markets, lands in venues that have been by no means immediately attacked and is then formed by typically questionable governance choices.
As extra worth strikes on-chain, the hidden layers beneath the belongings themselves are going to turn out to be a lot more durable to disregard.
