LayerZero (ZRO), the cross-chain messaging protocol, has publicly acknowledged a critical security misstep that allowed the North Korean hacking group Lazarus to exploit its infrastructure during a past incident. In a candid post on its official X account, the project apologized for poor communication and admitted that operating a sub-component of its Decentralized Verification Network (DVN) in a single-validator mode was a serious mistake.
What happened during the attack
The incident in question involved the exploitation of a sub-RPC within LayerZero’s DVN. According to the project’s statement, the Lazarus Group managed to corrupt data through this compromised sub-RPC. Simultaneously, an external RPC provider was hit with a distributed denial-of-service (DDoS) attack, compounding the operational disruption. LayerZero emphasized that the core protocol itself remained unaffected and that no user funds were directly lost from the LayerZero network. However, the event was tied to the broader Kelp DAO rsETH exploit, where attackers used the bridge to move illicit funds.
Single validator mode: the root cause
LayerZero’s post-mortem identified the single-validator setup as the fundamental weakness. In a decentralized verification network, a single validator creates a single point of failure. If that validator is compromised or goes offline, the entire verification process can be corrupted or halted. The project acknowledged that this configuration was a serious design flaw and that it failed to communicate the severity of the situation to the community in a timely manner.
The path forward: multi-validator and infrastructure overhaul
In response, LayerZero has announced a comprehensive security upgrade. The protocol will immediately discontinue the single-validator setup and transition its default configuration to a multi-validator system requiring at least a 3:3 threshold — meaning three out of three validators must agree for a transaction to be verified. This change eliminates the single point of failure and aligns the network with industry best practices for decentralized security.
Full security infrastructure upgrade
Beyond the validator change, LayerZero plans a complete overhaul of its security infrastructure. This includes developing new client software, introducing a multi-signature (multisig) system for critical administrative actions, and deploying an integrated console management platform. These measures are designed to provide better monitoring, faster incident response, and greater overall resilience against sophisticated threat actors like Lazarus.
Why this matters
This incident serves as a cautionary tale for the broader DeFi and cross-chain ecosystem. As bridges and messaging protocols become critical infrastructure for moving value between blockchains, their security configurations must be held to the highest standards. A single-validator setup, while potentially simpler to operate, introduces a vulnerability that state-sponsored hacking groups are actively hunting for. LayerZero’s admission and corrective actions are a step toward rebuilding trust, but the episode highlights the ongoing arms race between protocol developers and increasingly sophisticated attackers.
Conclusion
LayerZero’s acknowledgment of its past security failure and its commitment to a multi-validator future is a necessary, if belated, response to a serious incident. The transition to a 3:3 validator system, combined with a broader infrastructure upgrade, represents a meaningful improvement. For users and developers relying on cross-chain infrastructure, this episode reinforces the importance of demanding transparency and robust security configurations from the protocols they depend on.
FAQs
Q1: Was the LayerZero protocol itself hacked?
No. LayerZero stated that its core protocol was unaffected. The attack targeted a sub-RPC of its Decentralized Verification Network (DVN) and an external RPC provider.
Q2: Did users lose funds in this incident?
LayerZero has not reported any direct loss of user funds from its own network. The incident was connected to the Kelp DAO rsETH exploit, where the bridge was used as part of the attack chain.
Q3: What is a 3:3 multi-validator system?
A 3:3 system requires all three validators in a set to confirm a transaction before it is verified. This eliminates the single point of failure present in a single-validator setup and provides stronger security guarantees.