LayerZero Admits Fault in $292 Million Kelp DAO Exploit, Discloses Separate Internal Security Breach
Cross-chain messaging protocol reverses blame after three weeks, bans single-verifier bridge configuration, and reveals a multisig signer used production hardware to execute a personal trade.
LayerZero Labs issued a public apology on May 9, 2026 over its handling of the April 18, 2026 Kelp DAO bridge exploit, in which attackers drained 116,500 rsETH (a yield-bearing ETH derivative token that allows users to earn restaking rewards while maintaining liquidity), worth roughly $292 million, from the liquid restaking protocol.
The company acknowledged it allowed its verifier network to operate in a configuration that made a single compromised node sufficient to authorize fraudulent cross-chain transactions. The apology reversed a position LayerZero had held for nearly three weeks, during which it repeatedly blamed Kelp DAO for the security failure.
The exploit, which security firms Blockaid and Halborn have attributed with preliminary confidence to North Korea's Lazarus Group, remains the largest DeFi theft of 2026.
Attackers gained access to two internal LayerZero RPC nodes, then launched a distributed denial-of-service attack against a third external node that served as a fallback. With legitimate infrastructure rendered inaccessible, LayerZero's own Decentralized Verifier Network (DVN) was left relying entirely on attacker-controlled nodes. Notably, the two compromised internal nodes continued returning truthful data to other queriers throughout the attack, a detail that explains why detection proved so difficult.
Because Kelp DAO's bridge used a "1-of-1 DVN" configuration (meaning only one verifier's approval was needed to release funds), a single forged cross-chain message was enough to authorize the drain. The OFT adapter contract at address 0x85d456B2DfF1fd8245387C0BfB64Dfb700e98Ef3 released the rsETH as intended, trusting a verification layer that had already been corrupted. Stolen assets were then deposited into Aave V3 as collateral, with approximately $190 million in WETH and ETH borrowed against them. From there, 52,440 ETH was routed to a consolidation address while USDC was moved through ChangeNow and Binance. Attackers had separately used Tornado Cash before the exploit to fund operational wallets, a step that preceded and was distinct from the post-theft asset movements. A second attempted theft of approximately $95 million (around 40,000 rsETH) was blocked; the Arbitrum Security Council subsequently froze more than 30,000 ETH in response to the incident.
In its apology post, LayerZero wrote: "We made a mistake by allowing our DVN to act as a 1/1 DVN for high-value transactions. We didn't police what our DVN was securing, which created a risk we simply didn't see." That statement contradicts the company's initial April 19 post-mortem, which characterized Kelp DAO's single-verifier setup as a deliberate application-level choice.
Kelp DAO pushed back publicly on April 20, releasing Telegram screenshots in which a LayerZero team member wrote "No problem on using defaults either." The same message noted that a custom DVN setup had been raised as an alternative but would be left to Kelp's team. Kelp said the message did not object to the 1-of-1 configuration and was consistent with 2.5 years of integration discussions across eight check-ins in which no objection to the setup was ever raised.
By May 5, Kelp had also pointed out that LayerZero's own developer quickstart documentation wired every example pathway with one required DVN and no optional DVNs, effectively making 1-of-1 the template default. LayerZero responded the same day with a counterclaim that Kelp had initially deployed a multi-DVN configuration and then manually downgraded to a 1-of-1, asserting the change was an active application-level decision made by Kelp's team. LayerZero held that position until its May 9 reversal and apology.
The Kelp DAO incident was not an isolated misconfiguration. Security researchers found that between 40 and 47 percent of all active LayerZero OApp (Omnichain Application) contracts were using the same single-verifier setup at the time of the exploit, collectively exposing an estimated $4.5 billion in assets to a comparable attack. LayerZero has since banned the 1-of-1 configuration from its DVN entirely, setting new defaults of 5-of-5 verifier requirements where feasible and a minimum of 3-of-3 on chains with fewer available nodes.
The ZRO token fell between 18 and 24 percent in the 48 hours following the breach, trading down from roughly $2 to around $1.40 to $1.52. Total DeFi TVL (total value locked, a measure of assets deposited in protocols) dropped approximately $13 billion in the same window, falling from roughly $99.5 billion to approximately $86 billion, and Aave recorded $8.45 billion in deposit outflows as users responded to potential bad debt exposure estimated between $123 million and $230 million, depending on rsETH recovery pricing.
Alongside the DVN apology, LayerZero disclosed a separate internal security incident it had not previously made public. Approximately 3.5 years ago, a signer on the company's production multisig wallet (a system requiring multiple approvals before moving funds) used the same hardware device that secured user assets to execute a personal trade.
LayerZero said the action was "obviously not ok," that the signer was removed, and that wallets were rotated. The company also said it built a custom multisig system called OneSig and added localized anomaly detection on each signing device following the incident.
That confirmed disclosure is separate from a set of disputed allegations. CEO Bryan Pellegrino has denied claims that production keys were used for memecoin trading, attributing suspicious transactions to former multisig members who had already been removed and to OFT testing activity.
The fallout has accelerated a measurable shift away from LayerZero in the bridge market. Kelp DAO migrated its bridging infrastructure to Chainlink's CCIP (Cross-Chain Interoperability Protocol). Solv Protocol followed, moving roughly $700 million in tokenized Bitcoin products to CCIP. Insurance protocol Re moved more than $200 million in the same direction. Together, these migrations represent over $1 billion in assets rerouted within roughly three weeks of the exploit. For context, LayerZero secures approximately $50 billion in assets across more than 150 chains, meaning the migrations, while significant reputationally, represent a fraction of the total ecosystem.
For users in sub-Saharan Africa and South Asia, where decentralized bridges are often the primary route for moving assets across chains (centralized exchange access remains limited by regulation, banking gaps, and KYC barriers in many of these markets), the systemic risk exposed here is not abstract.
Sub-Saharan Africa received more than $205 billion in on-chain value in the twelve months to June 2025, according to the most recent available data, a 52 percent year-on-year increase, and as on-chain volumes continue to grow, the region's reliance on multi-chain infrastructure grows with them.
Aave, directly affected by the rsETH contagion, is among the most widely used lending platforms across both regions.
In jurisdictions where regulators are increasingly scrutinising crypto infrastructure for consumer protection risks, disclosures about production key misuse are precisely the kind of governance detail that shapes licensing conversations.
The broader question raised by LayerZero's apology is not whether the 1-of-1 flaw has been fixed, but what governance standards bridge operators should be held to before a $292 million loss forces the disclosure.