The crypto community was plunged into anxious anticipation for several hours: rumors of a $2.4 million hack of LayerZero protocol wallets spread instantly across the network. However, as a thorough investigation revealed, this turned out to be a false alarm. In reality, we witnessed not a hacker attack, but a standard internal asset consolidation operation.
The first alarm was raised by the security service PeckShield. Experts detected suspicious movement of funds from LayerZero protocol Executor wallets across several networks: BNB Chain, Base, Arbitrum, Avalanche, Optimism, Mantle, Plasma, and Ethereum. According to their analysis, the attacker allegedly transferred the stolen assets to the Ethereum network, where the majority was exchanged for 956 ETH (approximately $1.79 million) and $322,000 in USDC.
Other observers, including WuBlockchain and analyst Zacharia Sharif, also estimated the alleged damage in the range of $2.1 to $2.4 million. The market reacted instantly: headlines about the hack flooded feeds, and some protocols temporarily suspended operations.
Why the panic was unfounded
The key point in this story is the speed of the refutation. The LayerZero team promptly issued a statement, emphasizing that the funds were withdrawn from internal wallets as part of standard asset operations. "Nothing is at risk," the protocol stated. Co-founder Bryan Pellegrino also expressed bewilderment over the resulting uproar, noting that it was merely a "routine asset consolidation."
Independent analysts, such as Crypto Patel, confirmed this version, pointing out that the transfers were part of a routine internal rebalancing. The Verdict service emphasized that the false alarm caused the market to panic for about four hours, even though there was actually no threat.
My analysis: This incident is a vivid example of how, in the crypto industry where security is paramount, even a minor movement of funds can trigger widespread panic. The lesson here is simple: before raising the alarm and making loud statements, it is necessary to thoroughly verify the data. Otherwise, we risk succumbing to emotions and damaging the reputation of projects that are actually operating normally.