LayerZero, a leading cross-chain interoperability protocol, has issued a significant reversal in its stance regarding the recent $292 million exploit targeting Kelp DAO’s rsETH token bridge. After weeks of framing the incident as a developer configuration failure on the part of Kelp, LayerZero now acknowledges that it 'made a mistake' by allowing its own verifier network—a decentralized oracle system—to secure high-value assets under a notoriously vulnerable setup. The admission marks a pivotal moment for the protocol, which has long prided itself on its security architecture and its role in enabling seamless asset transfers across disparate blockchains.
The Exploit: A $292 Million Heist
On an undisclosed date in early May 2026, attackers—widely attributed to North Korea’s Lazarus Group—exploited the rsETH bridge between Ethereum and multiple layer-2 networks. The bridge, built on LayerZero’s cross-chain messaging framework, was designed to transfer Kelp DAO’s liquid staking derivative rsETH. The attackers drained approximately $292 million worth of assets, including Ethereum and various ERC-20 tokens, in what became one of the largest DeFi hacks of the year. Initial investigations pointed to a misconfiguration in the bridge’s security settings, which allowed an unauthorized party to trigger a withdrawal of funds under false pretenses.
At first, LayerZero management placed the blame squarely on Kelp DAO’s developers, arguing that the configuration of the bridge’s verifier settings—specifically the choice to rely on a single verifier rather than a multi-signature or threshold setup—was entirely the DAO’s responsibility. In a series of tweets and blog posts, LayerZero CEO Bryan Pellegrino emphasized that 'the protocol itself was not compromised' and that 'developers must take ownership of their own security parameters.' The message was clear: LayerZero provided the infrastructure, but clients were responsible for their own implementation.
A Reversal of Position
However, in a stunning reversal on May 9, 2026, LayerZero released a public statement admitting fault. 'We made a mistake,' the company declared. 'We own the decision to allow our own verifier network to secure high-value transfers in a setup we knew was vulnerable.' The statement went on to clarify that while the protocol core remained intact, LayerZero had explicitly approved a configuration that relied on its own decentralized verifier network—known as LayerZero Verifier—without requiring additional security layers such as a separate multi-sig or an independent oracle. This configuration, which the company acknowledged was 'insufficiently robust for transfers above a certain threshold,' was directly responsible for the exploit vector.
Security analysts note that LayerZero’s architecture allows developers to choose which verifiers to use for cross-chain messages. By default, LayerZero provides its own verifier network, but users can also plug in third-party verifiers like Chainlink or custom multi-sig setups. In the case of Kelp’s rsETH bridge, the developers opted to use only LayerZero’s verifier—a decision that LayerZero now concedes was imprudent given the asset value at stake.
Technical Breakdown: The Attack Vector
According to post-mortem reports issued by several blockchain security firms, the exploit exploited a vulnerability in the RPC (Remote Procedure Call) infrastructure used by LayerZero’s verifier network. Specifically, the attackers compromised a subset of the verifier’s relayer nodes, which are responsible for forwarding messages between chains. By gaining control of these nodes, the attackers were able to forge a message that convinced the destination chain that a legitimate withdrawal had been authorized, when in fact no such authorization existed.
LayerZero has emphasized that its protocol-level cryptographic mechanisms—such as the use of threshold signatures and a decentralized set of oracle operators—remained secure. The breach occurred at the application layer, where the verifier selection process allowed a single point of failure to dictate the outcome. 'If Kelp had used a multi-verifier setup, the attack would have been impossible,' a LayerZero spokesperson said in a follow-up interview. 'But we failed to enforce or even strongly recommend such a configuration for high-value bridges.' Critics argue that LayerZero’s initial blame-shifting was a disservice to the industry, as it obscured the real lessons about shared responsibility in cross-chain security.
Fallout: Client Exodus and Market Impact
The admission has done little to stem the tide of client departures. Kelp DAO, the immediate victim, announced within hours of LayerZero’s statement that it would migrate its rsETH bridge to Chainlink’s Cross-Chain Interoperability Protocol (CCIP). 'We need a solution where security is not left to the discretion of a single provider,' said a Kelp representative. 'Chainlink’s decentralized oracle network and its battle-tested infrastructure give us the confidence we require.'
More damaging for LayerZero was the decision by Solv Protocol, a leading tokenized bitcoin platform managing over $700 million in total value locked, to move its entire cross-chain infrastructure away from LayerZero. Solv’s announcement cited 'irreparable damage to trust' and a need for 'radical transparency in security practices.' The migration will take several months and involve extensive audits, but Solv’s leadership made clear that LayerZero’s handling of the Kelp incident was a decisive factor.
Several other smaller protocols have also paused their integrations with LayerZero pending a security review. The total value secured by LayerZero’s bridges has dropped by an estimated 40% in the week following the admission, according to data from DefiLlama. Analysts predict that LayerZero could lose its dominant position in the cross-chain messaging market if it fails to implement stricter security defaults.
Background: LayerZero’s Rise and Promises
LayerZero, founded in 2021, quickly became a darling of the DeFi ecosystem for its innovative 'ultra-light node' approach to cross-chain messaging. Unlike earlier interoperability solutions that relied on heavy on-chain verification or trusted third parties, LayerZero allowed developers to choose their own verifiers and maintain control over security parameters. This flexibility attracted a wide range of projects, from decentralized exchanges like Uniswap (which uses LayerZero for its cross-chain swaps) to lending protocols and token bridges. At its peak, LayerZero facilitated over $15 billion in monthly cross-chain volume.
The protocol’s architecture consists of three main components: the endpoint (smart contracts on each chain), the oracle (which reports block headers), and the relayer (which transmits message payloads). By default, LayerZero operates its own oracle and relayer network, but developers can replace either component with custom implementations or third-party providers. This modularity was hailed as a breakthrough, but it also introduced complexity: developers had to understand the trade-offs of different verifier configurations.
Security experts have long warned that the default configuration—using LayerZero’s own verifier—could create a single point of failure if the provider itself were compromised or if its infrastructure had vulnerabilities. The Kelp exploit proved those warnings prescient. 'LayerZero’s promise was that you could customize security to your needs,' said a blockchain security auditor who spoke on condition of anonymity. 'But in practice, many developers just took the default because it was easiest. That default should have been far more secure.'
Industry Reactions and Broader Implications
The incident has reignited debate about the division of responsibility between infrastructure providers and application developers. While LayerZero has now accepted blame, the industry remains divided. Some argue that LayerZero should have insisted on a multi-verifier setup for bridges handling more than, say, $10 million in assets. Others contend that Kelp DAO, as the application’s developer, should have performed its own due diligence and not relied solely on LayerZero’s recommendations.
Chainlink, the largest decentralized oracle network, has capitalized on the mishap. Its CCIP product, which mandates the use of multiple independent oracles and a separate risk management network, is gaining traction. Chainlink’s CEO, Sergey Nazarov, tweeted, 'Trust is built on verifiable guarantees, not on post-hoc apologies.' The company has announced partnerships with three additional DeFi protocols that previously used LayerZero.
Regulators are also taking note. The hack, attributed to North Korean state-sponsored actors, has drawn the attention of the U.S. Treasury Department and the Office of Foreign Assets Control (OFAC), which may consider sanctions against LayerZero if it is deemed to have facilitated illicit finance through negligence. While no formal action has been taken, the possibility looms large over the protocol’s future.
In response, LayerZero has announced a security overhaul: it will require all bridged transfers above a threshold (likely $5 million) to use at least two independent verifiers from separate providers. Additionally, it is implementing a mandatory security audit certification program for any project using its infrastructure to bridge assets over $1 million. These measures, while welcomed by some, are seen by others as too late. 'The cat is out of the bag,' wrote a prominent DeFi analyst on X. 'LayerZero’s reputation has been permanently damaged.'
Meanwhile, Kelp DAO is working to recover lost funds through negotiations with LayerZero and law enforcement. The exact recovery prospects remain unclear, although LayerZero has pledged $20 million from its treasury to partially reimburse affected users. Kelp has also launched a bug bounty program offering up to $10 million for information leading to the identification of the attackers.
Technical Deep Dive: How Cross-Chain Bridges Can Fail
Cross-chain bridges have historically been one of the most vulnerable components in DeFi. According to data from REKT, a platform that tracks blockchain exploits, bridges have accounted for over $2.5 billion in losses since 2020, representing roughly 40% of all hack-related losses. The 2022 Wormhole hack ($326 million), the 2022 Nomad bridge collapse ($190 million), and the 2023 Mixin Network exploit ($200 million) all involved cross-chain bridges. The common thread in many of these incidents was a failure in the verification mechanism—whether it was a compromised validator set, a flawed smart contract, or, as in this case, a misconfigured oracle/relayer setup.
LayerZero’s design, while innovative, introduced a new attack surface: the RPC infrastructure underlying its verifier network. The verifier network operates by running relayer nodes that listen to events on source chains and then deliver messages to destination chains. These relayers are themselves distributed and operated by independent parties, but the specific set of relayers used for a given message is determined by the sender’s configuration. In the Kelp bridge, the configuration specified a single relayer from LayerZero’s internal pool. When that relayer’s RPC endpoint was compromised—through a phishing attack or a vulnerability in the relayer software—the attackers could inject a fraudulent message.
LayerZero has since patched the vulnerability by implementing a 'verifier diversity requirement' at the protocol level, but the damage to its ecosystem persists. The incident underscores a fundamental tension in DeFi between flexibility and security. Too much flexibility allows developers to shoot themselves in the foot; too little stifles innovation. LayerZero’s mistake was in assuming that developers would naturally choose the safest configuration, without enforcing safeguards for high-value assets.
The broader lesson for the industry is that infrastructure providers must take a more proactive role in preventing user errors. This is analogous to how cloud providers like AWS offer 'security by default' settings that automatically encrypt data and restrict access. LayerZero is now moving in that direction, but for many clients, the trust has been broken.
In the coming months, LayerZero will likely face increased competition from Chainlink CCIP, Wormhole (which has also implemented stricter security defaults), and new entrants like Axelar. The cross-chain interoperability market is expected to grow to $5 billion in total value secured by 2027, according to projections from Messari. LayerZero’s ability to maintain its market share will depend on how quickly it can restore confidence.
One possible path forward is for LayerZero to open-source its verifier network code and submit it to multiple independent audits on an ongoing basis. Another is to create a formal insurance fund specifically for losses arising from configuration errors, backed by a portion of its protocol fees. Such measures could signal a genuine commitment to security, but they will take time to implement.
For now, the crypto industry watches nervously. The Kelp exploit is a stark reminder that even the most sophisticated protocols can fail when human oversight is lacking. LayerZero’s admission of mistake is a step in the right direction, but it remains to be seen whether it can rebuild the 'L0' that once stood for 'Layer Zero' trust.
Source: Coindesk News