Kelp DAO Hack Rocks DeFi as Attacker Drains $292 Million in rsETH
The decentralized finance world is reeling from what has officially become the largest crypto exploit of 2026. An attacker successfully drained 116,500 rsETH tokens from Kelp DAO’s LayerZero-powered bridge on Saturday, making off with approximately $292 million. The Kelp DAO hack represents nearly 18 percent of the entire circulating supply of rsETH, sending shockwaves through the DeFi ecosystem and triggering emergency responses from major protocols including Aave, SparkLend, Fluid, and Upshift.
This devastating breach has left wrapped versions of rsETH stranded across more than 20 different blockchains, raising serious concerns about the legitimacy and backing of tokens held by users on layer 2 networks. The incident underscores the persistent vulnerabilities in cross-chain infrastructure and serves as a stark reminder of the risks facing the rapidly expanding DeFi landscape.
What Happened During the Kelp DAO Hack
The attack unfolded with alarming speed and precision at 17:35 UTC on Saturday. An unknown attacker managed to exploit Kelp DAO’s bridge, which was built on LayerZero’s cross-chain messaging infrastructure. By tricking the system into believing a legitimate instruction had arrived from another network, the attacker successfully triggered the bridge to release 116,500 rsETH to their controlled wallet address.
For those unfamiliar with the technology involved, here’s what makes this attack particularly concerning:
- LayerZero functions as a cross-chain messaging layer that enables different blockchains to send verified instructions to each other
- Kelp DAO operates as a liquid restaking protocol that routes user-deposited ETH through EigenLayer to generate additional yield
- rsETH serves as a tradeable receipt token for users who deposit ETH into the Kelp restaking system
- The compromised bridge held the entire rsETH reserve backing wrapped versions across multiple networks
The attack didn’t end with the initial drain. At 18:26 UTC and again at 18:28 UTC, two follow-up attempts were made, each carrying identical LayerZero packets designed to extract another 40,000 rsETH worth roughly $100 million. Fortunately, these subsequent attempts were reverted, preventing even greater losses.
Kelp DAO’s Emergency Response
Kelp DAO’s security team acted quickly once the breach was detected, though the damage had already been done. The protocol’s emergency pauser multisig froze the core contracts at 18:21 UTC, just 46 minutes after the initial successful drain. This rapid response likely prevented additional theft, though it came too late to recover the initial stolen funds.
Despite the quick technical response, Kelp DAO’s public communication was notably delayed. The protocol didn’t acknowledge the incident publicly until 20:10 UTC, nearly three hours after the drain occurred. In their first X post addressing the situation, Kelp confirmed they were investigating alongside LayerZero, Unichain, their auditors, and external security specialists.
As of the time of reporting, Kelp DAO has not publicly disclosed how the attacker managed to bypass the bridge’s validation logic. This lack of transparency has only intensified concerns among users and other protocols that may have exposure to similar vulnerabilities.
The Ripple Effect Across DeFi Protocols
The consequences of the Kelp DAO hack extended far beyond the immediate theft. Because rsETH had been deployed across more than 20 networks through LayerZero’s OFT standard, the loss of the reserve backing sent panic waves through virtually every major DeFi lending and trading platform that supported the token.
Aave moved swiftly to contain potential damage, freezing rsETH markets on both V3 and V4 within hours of the exploit. Founder Stani Kulechov took to social media to reassure users that the exploit was external to Aave and that the protocol’s own contracts remained secure. Despite these assurances, the AAVE token still fell approximately 10 percent as markets priced in the potential for bad debt.
Other major protocols that took emergency action include:
- SparkLend froze its rsETH markets to prevent cascading losses
- Fluid similarly suspended rsETH-related operations
- Lido Finance paused deposits into its earnETH product due to rsETH exposure
- Ethena temporarily halted its LayerZero OFT bridges from Ethereum mainnet as a precautionary measure
Lido Finance was quick to clarify that its core products, including stETH and wstETH, remained completely unaffected by the incident. The company emphasized that the core Lido staking protocol had no involvement in the attack and that only the earnETH product carried exposure to rsETH.
Ethena, the stablecoin issuer, also moved quickly to reassure its community. The company confirmed it had no rsETH exposure and remained more than 101 percent overcollateralized. Their bridge pause was expected to last approximately six hours while the root cause of the Kelp DAO exploit was investigated.
Why the Layer 2 Exposure Is So Concerning
One of the most troubling aspects of this incident involves the wrapped versions of rsETH deployed across numerous layer 2 blockchains. Networks including Base, Arbitrum, Linea, Blast, Mantle, and Scroll all host rsETH tokens that were supposed to be backed by the reserves held in the now-drained bridge.
With that reserve gone, holders on non-Ethereum deployments now face a genuinely existential question about their tokens. Do they have anything of actual value underneath them? This uncertainty creates a potentially devastating feedback loop where several things happen simultaneously:
- Panic sets in among holders on layer 2 networks
- Mass redemption attempts pressure the unaffected Ethereum supply
- Kelp may be forced to unwind restaking positions to honor withdrawals
- The pressure could accelerate de-pegging of rsETH from its intended value
- Cascading liquidations could occur across multiple DeFi protocols
Whether rsETH maintains its peg through the weekend depends largely on how much of the cross-chain float attempts to redeem into ETH on Ethereum and whether Kelp can recover any portion of the stolen funds before the attacker successfully launders them through mixing services like Tornado Cash.
The Technical Vulnerability Explained
While Kelp DAO has not yet disclosed the exact technical details of how the exploit was executed, what is known suggests a fundamental flaw in the cross-chain messaging validation. The attacker essentially convinced LayerZero’s messaging layer that a legitimate instruction had been sent from another network, when in reality, no such authorized instruction existed.
Cross-chain bridges have historically been among the most vulnerable components in the DeFi infrastructure. Their complexity, the trust assumptions they require, and the value they typically hold make them attractive targets for sophisticated attackers. This incident adds to a growing list of bridge exploits that have plagued the crypto industry over the past several years.
The fact that the attack vector involved spoofing cross-chain messages raises broader questions about the security of LayerZero’s infrastructure, though it’s important to note that the validation failure appears to be specific to how Kelp’s bridge implemented the system rather than a flaw in LayerZero itself. Still, the incident will likely prompt a thorough review of similar implementations across the industry.
A Brutal Year for DeFi Security
The Kelp DAO hack doesn’t exist in isolation. It comes during what has been an unusually hostile period for decentralized finance protocols throughout 2026. The previous record holder for the largest DeFi exploit of the year was the Drift Protocol attack, which occurred on April 1 and resulted in losses of approximately $285 million.
That earlier attack on Drift, a Solana-based perpetuals protocol, was later linked to North Korea-affiliated threat actors. The pattern of state-sponsored attacks on DeFi infrastructure has become increasingly concerning, with sophisticated actors bringing significant resources to bear against these platforms.
Between the Drift hack and the Kelp DAO exploit, at least a dozen smaller protocols have also been successfully exploited. The list of victims includes:
- CoW Swap, a decentralized exchange known for its MEV-protection features
- Zerion, a popular crypto portfolio management platform
- Rhea Finance, an emerging DeFi protocol
- Silo Finance, a money market protocol with isolated asset pools
This steady drumbeat of exploits suggests that DeFi security challenges are not isolated incidents but rather reflect systemic vulnerabilities across the ecosystem. The Kelp DAO incident, at $292 million, has now overtaken Drift as the largest DeFi exploit of 2026, though the year is still young and the trend is deeply concerning.
The Recovery Challenge
Recovering stolen cryptocurrency has historically proven extremely difficult, especially when attackers use sophisticated laundering techniques. The attacker behind the Kelp DAO hack is likely already working to move the stolen funds through various obfuscation methods.
Tornado Cash, a privacy-focused cryptocurrency mixer, is frequently used by attackers to obscure the trail of stolen funds. Once assets have been processed through such services, tracing and recovering them becomes exponentially more difficult. Time is genuinely of the essence in these situations.
The Kelp team and their partners are presumably working with blockchain forensics firms to track the stolen funds in real-time. However, the reality of cryptocurrency attacks is that recovery rates are typically quite low. Most exploit victims end up absorbing the losses, either through their own treasury or by distributing the pain among token holders through reduced redemption values.
What This Means for Users and the Broader Ecosystem
For rsETH holders and Kelp DAO users, the immediate path forward is uncertain. Those holding rsETH on Ethereum mainnet may find themselves in a relatively better position than holders on layer 2 networks, though even they face questions about the protocol’s ability to meet all redemption requests given the significant portion of circulating supply that has been stolen.
Users should be cautious about making impulsive decisions in the immediate aftermath of the hack. While the situation is genuinely serious, panic selling or attempting emergency redemptions during a crisis period often results in worse outcomes than waiting for clarity to emerge. Monitoring official Kelp DAO channels and reputable crypto news sources for verified updates is essential.
The broader DeFi community will undoubtedly spend considerable time analyzing this incident to extract lessons that can prevent similar attacks in the future. Key areas that will likely receive renewed scrutiny include:
- Cross-chain messaging validation mechanisms
- Bridge security architectures and trust assumptions
- Emergency pause capabilities and response times
- Reserve transparency and proof-of-reserves systems
- Insurance and recovery mechanisms for protocol users
The Future of Cross-Chain Infrastructure
The Kelp DAO hack will likely accelerate existing debates about the fundamental design of cross-chain infrastructure. Critics have long argued that cross-chain bridges introduce dangerous trust assumptions that undermine the security benefits of underlying blockchains. Incidents like this one add fuel to these arguments.
Alternative approaches to cross-chain functionality, including more decentralized and trust-minimized designs, may receive increased attention and development resources following this attack. However, transitioning existing ecosystems to new architectures is a massive undertaking that won’t happen overnight.
In the meantime, users interacting with cross-chain protocols will need to weigh the convenience and yield opportunities against the genuine risks these systems introduce. The Kelp DAO incident serves as a sobering reminder that even well-established protocols with professional audits and significant backing can fall victim to sophisticated attacks.
Looking Ahead After the Kelp DAO Hack
As the dust settles on the Kelp DAO hack, several things become clear about the current state of decentralized finance. The ecosystem has matured significantly in terms of total value locked and mainstream adoption, but security continues to lag behind growth. Each major exploit represents not just financial losses but also damaged trust that takes years to rebuild.
For Kelp DAO specifically, the path forward will be challenging. Even if the protocol survives this incident operationally, rebuilding user confidence and restoring rsETH’s peg will require significant effort and potentially innovative solutions. How the team handles transparency, communication, and any potential recovery or compensation plans will largely determine their long-term viability.
The broader DeFi community is watching closely, not just to see how Kelp responds but to extract lessons for their own protocols. This incident will undoubtedly influence security practices, design decisions, and user behavior across the ecosystem for months and years to come.
For now, the $292 million Kelp DAO hack stands as a stark reminder that despite all the innovation and progress in decentralized finance, security remains the industry’s most persistent and dangerous challenge. Until cross-chain infrastructure can be made truly secure, events like this one will continue to shake the foundations of DeFi.
