$293M KelpDAO Hack Exposes Cross-Chain DeFi Weaknesses, Lazarus Suspected

The KelpDAO hack that surfaced this week is not a smart contract failure story. It is something worse. Attackers drained roughly 116,500 rsETH, valued at about $293 million, by quietly corrupting the data plumbing that cross-chain DeFi assumes it can trust. The funds were then washed through Tornado Cash. Investigators now point to a familiar villain.

## $293M KelpDAO Hack Exposes Cross-Chain DeFi Weaknesses, Lazarus Suspected **What to Know** - Attackers drained roughly **116,500 rsETH**, worth about **$293 million**, from KelpDAO and laundered the funds through Tornado Cash. - LayerZero attributed the breach to **North Korea's Lazarus Group**, specifically the TraderTraitor subgroup. - **Aave** froze rsETH collateral activity to stop the contagion from spreading into Compound and Euler lending markets. - The exploit did not break a smart contract. It poisoned the **RPC nodes** feeding the Decentralized Verifier Network. The [KelpDAO hack](https://www.bleepingcomputer.com/news/security/kelpdao-suffers-290-million-heist-tied-to-lazarus-hackers/) that surfaced this week is not a smart contract failure story. It is something worse. Attackers drained roughly **116,500 rsETH**, valued at about **$293 million**, by quietly corrupting the data plumbing that cross-chain DeFi assumes it can trust. The funds were then washed through Tornado Cash. Investigators now point to a familiar villain. ## A Liquid Restaking Protocol Caught in the Crossfire KelpDAO is a liquid restaking protocol on Ethereum. Users deposit ETH and receive rsETH in return, a yield-bearing derivative that can move freely across decentralized apps and chains. That portability is the product. It is also, as this incident shows, the attack surface. The stolen rsETH did not stay parked. Because the token plugs into lending markets across the DeFi stack, the blast radius spread fast. Aave, Compound, and Euler all carried exposure. Aave moved first, freezing rsETH-collateralized positions to stop bad debt from cascading into healthy markets. The other protocols scrambled to evaluate their own risk. This is the trade-off nobody likes to talk about. Composability is a feature when everything works. When one piece breaks, it is a transmission line for catastrophic loss. > "Preliminary indicators suggest attribution to a highly sophisticated state actor, likely DPRK's Lazarus Group, more specifically TraderTraitor." ## How Did Attackers Pull Off the KelpDAO Heist? Short answer: they did not break the code. They broke the messengers. KelpDAO uses a Decentralized Verifier Network to confirm cross-chain messages routed through interoperability infrastructure from [LayerZero](https://layerzero.network/blog/kelpdao-incident-statement). DVNs lean on Remote Procedure Call nodes, the off-chain workers that read blockchain state and feed it back into the validation layer. Compromise enough RPCs, and you control what the verifiers "see." That is exactly what happened. The attackers seized control of select RPC nodes and started piping falsified blockchain data into the verification pipeline. To make sure honest nodes could not contradict the lies, they hammered the legitimate RPCs with distributed denial-of-service attacks. Trusted data sources went dark. The system fell back on the poisoned ones. From there it was paperwork. The verifier network signed off on cross-chain messages authorizing rsETH transfers that never occurred on the source chain. Tokens moved. Funds vanished into Tornado Cash. By the time the dust cleared, **$293 million** was gone. No bug bounty would have caught this. The smart contracts behaved exactly as designed. The problem was the assumption that the data feeding them was real. ## Why Lazarus Group Is the Prime Suspect The fingerprints look familiar. The [Lazarus Group](https://www.cisa.gov/news-events/cybersecurity-advisories/aa22-108a) and its TraderTraitor offshoot have been hammering crypto infrastructure for years. The FBI, CISA, and Treasury issued a joint advisory back in 2022 warning that North Korean state hackers were systematically targeting blockchain firms, exchanges, and DeFi protocols. The playbook has only gotten sharper since. What sets the KelpDAO breach apart is the patience. Compromising RPC infrastructure, coordinating DDoS waves, and timing the falsified messages takes preparation that goes well beyond a smash-and-grab exploit. This was reconnaissance, persistence, and execution at the level of a nation-state intrusion campaign. The crypto industry does not always like to admit it, but DPRK operators are arguably the most successful threat actors targeting Web3 today. The pattern matters. Lazarus does not chase coins for the thrill. The funds reportedly help finance North Korea's weapons programs. Every successful DeFi heist becomes a geopolitical line item. ## What This Means for Cross-Chain DeFi The uncomfortable read: cross-chain bridges and verifier networks have always been the soft underbelly of decentralized finance, and this incident proves the industry has not fixed the problem. It has just abstracted it. Validators and oracles sit at the center of every cross-chain transaction. They are also the easiest things to attack, because they live partly off-chain, in environments that look more like traditional web infrastructure than blockchain consensus. RPC nodes are servers. Servers can be compromised. Servers can be DDoS'd. When the security model assumes those servers are honest and available, the model has a hole big enough to drive **$293 million** through. Protocol teams now face a hard set of choices. Increase the number of independent verifiers. Diversify RPC providers across geographies and jurisdictions. Add anomaly detection that flags suspicious cross-chain message patterns before tokens move. Build circuit breakers that pause withdrawals when validator quorum looks degraded. None of these are free, and all of them slow things down. The market has historically punished slow. ## What Should Security Teams Do Right Now? The answer for any team running cross-chain operations is to assume compromise and verify everything. That means treating RPC nodes as adversarial unless proven otherwise, running redundant verifier sets that span unrelated infrastructure providers, and stress-testing what happens when half the validators go offline simultaneously. The KelpDAO blueprint will be copied. The teams that survive the next round are the ones building zero-trust assumptions into their bridge architecture today, not after the funds are already gone. This incident will fuel another round of insurance premium hikes for DeFi protocols and another wave of regulatory hand-wringing about the risks of permissionless finance. Both are predictable. Neither will fix the underlying issue. The deeper lesson is structural. As long as cross-chain DeFi keeps stacking trust assumptions on top of off-chain infrastructure, the attack surface keeps growing. Lazarus knows it. The next attacker knows it too. The question is whether the protocols catch up before another nine-figure exit drains a different liquid restaking pool. KelpDAO will rebuild. Aave will likely thaw rsETH markets once the post-mortem is in. The cycle will continue. And somewhere in Pyongyang, a unit of state-backed engineers is already mapping the next target. ## FAQ **What happened in the KelpDAO hack?** Attackers drained approximately **116,500 rsETH**, worth about **$293 million**, from KelpDAO by compromising the RPC nodes that feed its Decentralized Verifier Network. They injected falsified cross-chain messages, authorized fraudulent token transfers, and laundered the proceeds through Tornado Cash. The smart contracts themselves were never broken. **Who is behind the KelpDAO exploit?** LayerZero attributed the breach to a sophisticated state actor, most likely North Korea's Lazarus Group and specifically its TraderTraitor subgroup. US agencies including the FBI, CISA, and Treasury have publicly tied this group to a long-running campaign against cryptocurrency and blockchain firms dating back to at least 2022. **Why did the KelpDAO hack affect Aave, Compound, and Euler?** rsETH is widely accepted as collateral across major DeFi lending protocols. When the token's backing came into question, the contagion risk spread instantly. Aave froze rsETH-related activity to prevent cascading liquidations and protect the broader pool. It is a textbook case of DeFi composability turning into systemic risk. **How can DeFi protocols defend against cross-chain attacks like this?** Protocols should diversify RPC providers, run redundant verifier sets across independent infrastructure, monitor for abnormal cross-chain message patterns, and implement circuit breakers that pause activity when validator quorum degrades. Treating off-chain infrastructure as a trusted layer is no longer a defensible security posture.