A single spoofed message in the LayerZero bridge allowed the attacker to drain $292M in rsETH.
The attacker used unbacked rsETH as collateral across lending protocols like Aave, borrowing real assets and creating massive bad debt.
Aave absorbed the biggest impact, with WETH pools hitting full utilization, withdrawals failing, and emergency freezes triggered.
The largest decentralized finance exploit of 2026 unfolded with surgical precision on Saturday afternoon. At 17:35 UTC, a single call to a cross-chain messaging contract set off a cascade of failures that would drain nearly $300 million from one protocol, strand collateral across two dozen blockchains, and push the industry’s dominant lending platform, Aave, to the edge of a liquidity crisis.
The attacker manipulated LayerZero’s cross-chain messaging layer, the verification system that confirms legitimate instructions between networks, into believing a valid transfer request had arrived from another chain. The spoofed message triggered the unauthorized transfer of 116,500 rsETH, Kelp DAO’s liquid restaking token, worth approximately $292 million.
Earlier today we identified suspicious cross-chain activity involving rsETH. We have paused rsETH contracts across mainnet and several L2s while we investigate.
The theft was not opportunistic. Investigation revealed the operation was set in motion well in advance, with the attacker funding wallets through Tornado Cash roughly ten hours before the breach, thereby enhancing transactional anonymity.
The execution was almost clinical. By the time Kelp’s emergency ‘pauseAll’ function was triggered, 46 minutes after the first successful drain, the protocol had already lost the bulk of its funds. Two follow-up attempts by the attacker failed. Transactions at 18:26 and 18:28 UTC attempted to drain another 40,000 rsETH, worth about $100 million. Both were rejected due to the protocol’s paused state. Without that intervention, total losses could have climbed near $391 million.
A breach that started outside lending markets
The incident originated with Kelp DAO’s rsETH, a liquid restaking token designed to move across chains using LayerZero. According to preliminary findings, attackers were able to manipulate the verification layer responsible for confirming cross-chain messages. By compromising parts of the underlying RPC infrastructure and forcing the system into fallback conditions, they succeeded in introducing forged data that appeared legitimate on-chain.
The result was the creation of approximately 116,500 rsETH tokens without any real backing. From a technical standpoint, the exploit did not rely on breaking a smart contract. Instead, it targeted the assumptions that allow different blockchains to trust one another.
Once the tokens were minted, the attacker moved quickly. The unbacked rsETH was deposited into lending platforms and used as collateral to borrow real assets, effectively converting synthetic value into liquid capital.
Collateral shock triggers liquidity exodus and market panic
Crypto analyst Darkfost described the situation as a collateral-driven failure rather than a protocol exploit, noting that the deterioration of a single asset can produce cascading effects across lending systems. That dynamic became visible almost immediately as users began withdrawing funds at scale.
After going through a series of recent challenges, including the departure of key contributors such as BGD Labs and Chaos Labs, Aave finds itself once again under pressure.
❌ A major incident has affected the ecosystem through an exploit involving rsETH used… pic.twitter.com/Jx9fNUFHzZ
Within a single day, total value locked on Aave dropped sharply, with estimates suggesting a contraction of roughly $7 billion. The movement was not limited to withdrawals. Exchange flows surged as well, with AAVE tokens moving to centralized platforms at levels far above their typical range. Data shared by Darkfost indicates that inflows spiked significantly, particularly toward Binance, reflecting a broader shift in market sentiment.
The price reaction followed. AAVE declined by around 15% over the same period, underscoring the speed at which confidence deteriorated once uncertainty spread.
As the attacker’s activity spread through lending markets, the pressure quickly concentrated on Aave, where rsETH had already been integrated as collateral. The protocol itself remained intact, but its exposure to the compromised asset created a new form of risk that traditional safeguards were not designed to handle.
In its response, Aave moved quickly to contain the fallout while distancing its core infrastructure from the root cause of the incident. The protocol clarified that its smart contracts were not exploited, and that the disruption stems from the compromised rsETH asset linked to KelpDAO’s bridge.
To prevent further risk, Aave froze all rsETH-related activity across its latest versions and restricted WETH liquidity in affected markets. While maintaining that rsETH on Ethereum remains fully backed, the team acknowledged ongoing uncertainty and said it is actively reviewing transactions that took place after the exploit.
Update on rsETH incident:
According to our analysis, rsETH on Ethereum mainnet is fully backed.
Out of an abundance of caution, rsETH remains frozen across Aave V3 and V4 and exposure to the incident is capped.
WETH reserves also remain frozen across affected markets including…
Aave also signaled that, if necessary, it may take steps to absorb or offset any bad debt resulting from the event as the situation continues to evolve.
Liquidity stress replaces technical failure
Although the incident was triggered by an exploit, the most immediate problem facing Aave users was not a loss of funds, but a shortage of liquidity. As withdrawals accelerated and borrowing demand remained elevated, key markets approached full utilization. In practical terms, this meant that most deposited assets had already been lent out, leaving little available for users attempting to exit.
Under such conditions, withdrawal requests can stall or fail, not because the protocol is insolvent, but because liquidity is temporarily unavailable. For users, however, the distinction is largely academic. In fast-moving markets, the inability to access funds can carry consequences similar to outright losses.
Register and unlock all content immediately
Create a free account to get full access to all our content.
LayerZero points to configuration choices
In a detailed post-incident statement, LayerZero emphasized that its core protocol had not been exploited. Instead, the company attributed the breach to a highly sophisticated attack to the Lazarus Group targeting the RPC infrastructure used by its Decentralized Verifier Network.
The attack reportedly involved compromising specific nodes and forcing the system to rely on manipulated data sources, enabling the confirmation of transactions that never occurred.
LayerZero further indicated that the affected setup relied on a single verifier configuration, a design choice that removed redundancy from the system. Without multiple independent validators, there was no mechanism to reject forged messages once the primary verifier was compromised. The company noted that its recommended best practices involve multi-verifier configurations precisely to avoid such single points of failure.
The implication is that the exploit may have been enabled not only by technical sophistication, but also by decisions made during deployment.
Security trade-offs under renewed scrutiny
The role of configuration choices has drawn attention from across the industry. Ripple’s ex-CTO David Schwartz, widely known as JoelKatz, observed that many cross-chain systems are built with strong security features that are often underutilized in practice. He suggested that teams are frequently encouraged to prioritize ease of integration and scalability, even when doing so requires bypassing more robust protections.
I evaluated a lot of DeFi bridging systems for use by RLUSD. I was almost exclusively focused on the security and risk aspect. One thing I noticed is that most schemes were very well designed and had really strong mechanisms available to protect against exactly the type of attack…
This perspective aligns with a broader concern emerging from the incident. While DeFi infrastructure may offer advanced security mechanisms, those mechanisms are not always mandatory. As a result, the level of protection ultimately depends on how individual applications choose to configure their systems.
A pattern of escalating attacks
The Kelp DAO exploit is part of a wider trend that has seen attacks on DeFi infrastructure grow both in scale and frequency. Data compiled by X user Our Crypto Talk suggests that more than $1 billion has already been lost to hacks in 2026, with multiple high-profile incidents occurring in recent months.
April alone has recorded several major breaches, including both Kelp DAO and Drift Protocol, each involving losses in the hundreds of millions. Earlier in the year, a series of smaller but still significant exploits affected bridges, wallets, and lending systems.
This pattern points to a shift in attacker focus. Rather than targeting isolated smart contracts, increasingly sophisticated operations are aimed at the infrastructure layers that connect protocols and enable composability.
Contagion across interconnected systems
What distinguishes this incident is not just the initial exploit, but the speed at which it propagated. DeFi protocols are designed to interoperate, allowing assets to move freely between platforms. While this composability enhances efficiency, it also creates pathways for risk to spread.
Once rsETH lost its backing, its use as collateral in lending markets transmitted the impact far beyond its point of origin. A bridge failure evolved into a lending crisis, and the resulting liquidity stress triggered broader market reactions.
This chain reaction highlights a structural vulnerability within the ecosystem. When assets are deeply integrated across multiple platforms, the failure of a single component can have system-wide consequences.
What comes next for Aave and DeFi
In the immediate term, Aave’s priority remains stabilizing liquidity conditions and managing the fallout from bad debt created during the exploit. While the protocol’s core systems remain intact, the incident has exposed limitations in how risk is assessed when collateral depends on external infrastructure.
For the broader DeFi ecosystem, the questions are more fundamental. The incident has raised concerns about how cross-chain systems are secured, how collateral is evaluated, and how much reliance can be placed on interconnected protocols.
Whether these questions lead to meaningful changes remains uncertain. Past incidents have prompted short-term adjustments, but long-term structural reforms have often been slower to materialize.
What is clear, however, is that this event represents more than an isolated breach. It serves as a reminder that in decentralized finance, risk is rarely contained. When one layer fails, the effects can extend far beyond its boundaries, testing not just individual protocols, but the resilience of the system as a whole.
Create a free account to keep reading
Register or log in to unlock the full content immediately.
Onkar is a seasoned digital finance (DeFi) content creator with half a decade of experience in the blockchain and cryptocurrency industry. He has contributed to leading crypto media platforms, and collaborated with numerous DeFi projects worldwide. He blends his passion for technology and storytelling to deliver insightful content that bridges the gap between complex blockchain concepts and mainstream understanding.
