Arbitrum’s Security Council Seizes $71M in Stolen ETH After KelpDAO Bridge Hack
Arbitrum’s Security Council Seizes $71M in Stolen ETH After KelpDAO Bridge Hack
Arbitrum’s Security Council just immobilized $71 million in stolen ETH. One emergency vote. Nine signatures. And a question that won’t go away: can a “decentralized” network really freeze your funds?
How 116,500 rsETH Materialized Out of Thin Air
On Saturday, April 18, 2026, at precisely 17:35 UTC, someone did something extraordinary: they minted 116,500 rsETH tokens on Ethereum mainnet with zero legitimate backing behind them. Worth roughly $292 million at the time, this wasn’t a flash loan attack or a smart contract reentrancy bug. The contracts ran exactly as written. The verification layer was the weapon.
KelpDAO is a liquid restaking protocol built on EigenLayer. Users deposit ETH, which earns compounding yield across EigenLayer’s Actively Validated Services, and receive rsETH — a tradeable liquid restaking token representing their position. To enable rsETH to move across the multi-chain ecosystem, KelpDAO deployed a LayerZero-based bridge architecture using the OFT (Omnichain Fungible Token) standard. As of the exploit, that bridge held the backing reserve for rsETH deployed across more than 20 networks — Arbitrum, Base, Linea, Blast, Mantle, Scroll, and more. The protocol had roughly $1.07 billion in total value locked, making it the second-largest participant in EigenLayer’s ecosystem. This was the reserve that was drained.
LayerZero EndpointV2: 0x1a44076050125825900e736c501f859c50fE728c
KelpDAO rsETH OFT Adapter: 0x85d456B2DfF1fd8245387C0BfB64Dfb700e98Ef3
Attacker address: 0x8B1b6c9A6DB1304000412dd21Ae6A70a82d60D3b
// Forged origin packet → EID 30320 (Unichain)
→ 116,500 rsETH released from escrow
→ Single Transfer · One OFTReceived · One PacketDelivered
→ ~$292,000,000 exited the protocol
The Technical Root Cause: A 1-of-1 DVN
LayerZero’s security model is built on Decentralized Verifier Networks (DVNs) — independent entities that verify and attest to the authenticity of cross-chain messages. When a message travels from Chain A to Chain B, one or more DVNs must observe the packet on the source chain and deliver a signed attestation to the destination. The critical configuration choice is how many DVNs must agree.
KelpDAO’s rsETH bridge was configured with a 1-of-1 DVN setup — LayerZero Labs itself as the sole verifier. A single signature was all that stood between the bridge’s escrow and the open internet. The attackers, preliminarily attributed to North Korea’s Lazarus Group (TraderTraitor unit), exploited this exactly.
RPC Node Compromise Begins
Attackers compromise two of LayerZero’s downstream RPC nodes, swapping out op-geth binaries with malicious versions engineered to selectively lie to the DVN while reporting accurate data to all other querying IP addresses.
DDoS Triggers Failover
Attackers DDoS the uncompromised RPC nodes, forcing LayerZero’s DVN to failover to the poisoned endpoints. The malicious nodes confirm fraudulent cross-chain transactions that never occurred on the source chain.
The Drain — 116,500 rsETH Released
A forged LayerZero packet claiming origin from KelpDAO’s Unichain deployment passes the single compromised DVN. The OFT Adapter releases 116,500 rsETH from escrow to the attacker’s address. ~$292M exits in a single transaction.
KelpDAO Emergency Pause (46 Minutes Later)
Kelp’s emergency multisig freezes core contracts. Two subsequent follow-up attacks at 18:26 and 18:28 UTC — each attempting another 40,000 rsETH (~$100M) — both revert. The pause held.
DeFi Contagion Spreads
Attackers weaponize stolen rsETH as Aave v3 collateral, borrowing $196M in WETH. Aave WETH markets hit 100% utilization. Aave, SparkLend, and Fluid freeze rsETH markets. $6.6B in TVL collapses within 48 hours across affected protocols.
Arbitrum’s Security Council Acts: A Race Against the Bridge
As stolen funds began moving through the ecosystem, blockchain security firm PeckShield flagged a critical development: the exploiter had already initiated a native bridge withdrawal from Arbitrum back to Ethereum mainnet. The clock was ticking. If the 30,766 ETH that had been consolidated on Arbitrum One completed the withdrawal, it would enter Ethereum’s base layer — far harder to intercept.
The Arbitrum Security Council — a 12-member body elected by the Arbitrum DAO through semi-annual elections — convened an emergency session. According to council member Griff Green, the deliberation involved “countless hours of debates, technical, practical, ethical and political.” Nine of the twelve members voted to act. The council coordinated with law enforcement, who provided input on the exploiter’s identity. Security researchers later linked the operation to North Korea’s Lazarus Group.
“The Security Council identified and executed a technical approach to move funds to safety without affecting any other chain state or Arbitrum users.”
Using the 0x0000000000000000000000000000000000000DA0 precompile — a standard native ETH transfer mechanism — the council moved 30,766 ETH to a protocol-controlled intermediary address. The freeze was confirmed by Lookonchain approximately 20 minutes after execution. The funds were intercepted before the bridge withdrawal completed.
What Exactly Was Frozen
- 30,766 ETH moved to intermediary wallet FROZEN
- Destination: Protocol-controlled address 0x000…0DA0 ARBITRUM GOVERNANCE
- Access requires further governance vote PENDING
- Represents ~24% of the total $292M stolen PARTIAL RECOVERY
- Remaining ~$220M moved via other chains UNRECOVERED
- Lazarus Group suspected to be routing remainder LAUNDERING
For observers watching the situation unfold in real time, the move carried a weight that went beyond the mechanics of a single freeze. Dylan Dewdney, Founder of Kuvi AI, was among those who felt the historical echo immediately.
“It’s a fascinating moment for crypto governance — reminds me actually of the same gravitas as TheDAO, in a way. On one hand, decentralization purists will hate it. On the other, a DAO effectively looked at a state-sponsored hacking group and said: not this time. Arbitrum just demonstrated that onchain systems can defend themselves in real time. In a strange way, they out-coordinated one of the most sophisticated adversaries in the world. Legitimately onchain gangster moves.”
LayerZero vs. KelpDAO: Who Owns a $292M Default?
Even as funds were being frozen, a parallel battle erupted between the two parties at the center of the exploit. LayerZero moved first with a post-mortem attributing responsibility squarely to KelpDAO’s configuration choices. Kelp fired back with documentation. The dispute cuts to the heart of modular DeFi architecture.
LayerZero’s Position
LayerZero stated that KelpDAO “chose to utilize a 1/1 DVN configuration” despite the protocol’s consistent recommendation of multi-DVN redundancy. The firm argued that a properly hardened setup would have required consensus across multiple independent verifiers, making the attack ineffective even with a single node compromised. LayerZero announced it would stop signing messages for any application using a single-validator setup going forward, forcing a broad migration across its ecosystem.
KelpDAO’s Counter
Kelp pushed back hard. The team argued the 1-of-1 DVN was not a rogue customization
but LayerZero’s own documented default. The protocol’s
V2 OApp Quickstart — including the sample layerzero.config.ts — wires
every pathway with one required DVN and no optional DVNs. Kelp added that approximately
40% of protocols currently on LayerZero use the same configuration,
and that in the direct communications channel with LayerZero open since July 2024,
there was no specific recommendation to change the rsETH DVN setup.
“The KelpDAO exploit (~$290M) is NOT a LayerZero protocol bug. It’s a configuration issue and a case study every project with a cross-chain token needs to look at today. The smart contracts weren’t broken. The verification layer was.”
“There is no security floor. A configuration can be a 1/1 DVN and the DVN you chose can be a single node ran by a single entity. This is a design flaw.”
Independent analysis from Blockaid confirmed: “The KelpDAO exploit will be studied as the definitive case study in bridge DVN configuration risk. It did not require a zero-day. It exploited a weak governance policy and limited controls.” Chainalysis put it more bluntly: the attack proves that detecting malicious code isn’t enough — protocols must detect when a system enters an impossible state.
The Contagion Map: From rsETH to Aave to the Whole Ecosystem
The KelpDAO exploit did not stay contained. Within 46 minutes of the drain, the attackers began weaponizing the stolen rsETH across DeFi’s interconnected lending infrastructure. The mechanics were straightforward and devastating.
Attackers deposited the minted rsETH on Aave v3 as collateral and borrowed $196 million in WETH against it. Aave’s WETH market hit 100% utilization, rendering deposits inaccessible and triggering a $5.4 billion liquidity withdrawal cascade. Total DeFi TVL collapsed by $6.6 billion within 48 hours. Aave, SparkLend, and Fluid all froze their rsETH markets. Lido disclosed approximately $21.6 million in rsETH exposure through its EarnETH product and signaled it may deploy a $3 million loss buffer.
Aave Risk Scenarios (Per Ecosystem Risk Assessment)
- Scenario A: Losses socialized across all rsETH holders across chains $123.7M bad debt · ~15% depeg
- Scenario B: Losses isolated to L2 markets (Arbitrum, Mantle) Up to $230.1M impact
- Aave treasury backstop available $181M treasury
- Umbrella model available in certain cases Active
April 2026 has become the worst month for crypto hacks since February 2025, with over $606 million lost in just 18 days. The KelpDAO incident came on the heels of the Drift Protocol breach ($285M, April 1) — also linked to Lazarus Group — suggesting a sustained, coordinated campaign targeting DeFi infrastructure rather than isolated opportunistic attacks.
The structural lesson is uncomfortable: liquid restaking tokens (LRTs) as collateral on money markets create systemic amplification. When an LRT loses peg or backing, lending protocols don’t just feel the impact of the token — they absorb the entire downstream leverage built atop it. This is the second time in 2026 that an LRT collateral accepted on Aave has produced a nine-figure incident downstream of a non-Aave failure.
The Decentralization Paradox: Safety Valve or Fatal Contradiction?
Arbitrum’s intervention was precise, effective, and — for many in the crypto community — deeply troubling. In a single emergency session, a 12-person council immobilized 30,766 ETH that an external party held in their address. The funds were moved without a DAO vote, without the standard governance delay, and without consulting the broader community before execution. The legality, the ethics, and the precedent are all contested.
“A 12-person committee — elected by ARB token holders, sure — just demonstrated it can immobilize any funds on the network given sufficient justification. For a technology built on the promise of permissionless transactions, that’s either a necessary safety valve or a fundamental contradiction.”
The Arbitrum Security Council is defined in the Constitution of the Arbitrum DAO as a 12-member body divided into two cohorts, with members elected in semi-annual elections by ARB token holders. The council is bound by the Constitution to use its emergency powers only when necessary for declared security emergencies, and must issue a transparency report when those powers are invoked. The frozen ETH can only move through further governance action — ARB holders will ultimately vote on its fate.
The Community Splits
For the Freeze
- $71M recovered, likely from state-sponsored thieves
- Zero impact on legitimate users or applications
- Law enforcement coordination adds legitimacy
- Funds remain under governance — not taken
- DPRK laundering would have made recovery impossible
- Security Council acted within its constitutional mandate
Against the Freeze
- Permissionless transactions is the core value proposition
- Council can theoretically freeze any funds on the network
- Sets precedent for future, potentially non-consensual freezes
- “Decentralized” becomes a marketing term, not a guarantee
- Who decides what justification is “sufficient”?
- Ethereum community has concerns about L2 centralization
“Decentralized has become a marketing term. Only Bitcoin is actually decentralized.”
“WLFI is accused of wrongfully freezing user assets, while ARB froze stolen funds linked to DPRK hackers. One is ethically accepted, the other is criticized — but both prove the same point. When it matters most, governance overrides decentralization.”
“They can make the chain claim that they did whatever they want to all of the funds on the chain. But they cannot compel anyone to listen to those claims. Everyone else can make different claims and choose which set of claims to honor.”
The Stage 2 Problem
The Arbitrum DAO’s own governance documentation asks the question directly: “Can the governance process be further decentralized? How and when can the Security Council’s power be further minimized, or eliminated entirely?” These don’t have easy answers. Arbitrum achieved Stage 1 decentralization with permissionless fraud proofs via the BoLD upgrade. But Stage 2 — which would limit the Security Council to adjudicating only demonstrable bugs — remains a future aspiration, not a current reality.
The irony is sharp: the same emergency power that just recovered $71M in stolen funds is precisely the mechanism that prevents Arbitrum from claiming Stage 2 decentralization. Security and trustlessness are in direct tension, and today’s events demonstrated that tension is not theoretical.
Open Questions & The Road Forward
As of April 21, 2026, the 30,766 ETH remain locked in the protocol-controlled
address at 0x000...0DA0. No timeline has been
set for final disposition. The ARB community will vote on what happens to the funds
— options range from returning them to affected KelpDAO users to holding them pending
law enforcement proceedings. KelpDAO’s rsETH contracts remain paused. Founders
Amitej G and Dheeraj B have not announced a recovery timeline.
Open Questions as of Publication
- How will ARB governance vote to allocate the frozen $71M? PENDING VOTE
- Will other chains with similar emergency powers freeze their portions? UNCERTAIN
- Who bears legal liability — KelpDAO, LayerZero, or both? DISPUTED
- Will Aave deploy its Umbrella backstop for rsETH bad debt? MONITORING
- Will LayerZero’s forced DVN migration affect other protocols? IN PROGRESS
- Can the remaining $220M be traced before laundering completes? UNLIKELY
The KelpDAO exploit has accelerated three structural conversations that DeFi has been deferring: bridge configuration standards (who sets them, who enforces them, and who is liable when defaults cause catastrophic losses); LRT collateral risk in money markets (the second $100M+ incident in 2026 with restaked ETH tokens as the vector); and Layer 2 emergency powers (the legitimate tension between user protection and permissionless guarantees).
Chainalysis’s recommendation cuts through the noise: protocols must build systems capable of detecting when they have entered an “impossible state” — where issued tokens exceed locked collateral. For a cross-chain bridge, that means real-time consistency monitoring across every deployed chain. For DeFi as a whole, it means acknowledging that the “code is law” principle has never been fully true — and deciding what replaces it.
“The Lazarus Group, if indeed responsible, has already moved the remaining $220 million through various chains. Arbitrum caught what it could. The rest is likely gone.”
