A single misconfigured cross-chain verifier cost Kelp DAO $292 million on April 18, making it the largest DeFi exploit of 2026 and pushing total April losses past $600 million. The attacker — preliminarily attributed to North Korea's Lazarus Group by LayerZero — forged a cross-chain message throu...
"rsETH has been frozen on Aave V3 and V4. The asset does not have any borrowing power as a measure due to KelpDAO bridge exploit that happened outside of Aave." — Stani Kulechov, Founder, Aave
A single misconfigured cross-chain verifier cost Kelp DAO $292 million on April 18, making it the largest DeFi exploit of 2026 and pushing total April losses past $600 million. The attacker — preliminarily attributed to North Korea's Lazarus Group by LayerZero — forged a cross-chain message through LayerZero's EndpointV2, tricking Kelp's bridge into releasing 116,500 rsETH (roughly 18% of circulating supply) to an attacker-controlled address.
The contagion was immediate. Aave's total value locked dropped $6.6 billion in 24 hours — from $26.4 billion to under $20 billion — as depositors fled. The AAVE token fell 18%. At least nine protocols froze rsETH markets. The incident follows the $285 million Drift Protocol exploit on April 1, also attributed to Lazarus, meaning the same state-backed unit drained $577 million from DeFi in 18 days through two structurally different attack vectors.
At 17:35 UTC on Saturday, April 18, an attacker called the lzReceive function on LayerZero's EndpointV2 contract with a forged cross-chain message. The message instructed Kelp's rsETH OFT (Omnichain Fungible Token) bridge to release 116,500 rsETH — approximately $292 million at prevailing prices — to a wallet the attacker controlled.
The root cause was a configuration choice, not a code vulnerability. Kelp's rsETH OFT operated with a 1-of-1 DVN (Decentralized Verifier Network) threshold: a single verifier whose attestation was sufficient to authorize token releases on Ethereum. The attacker compromised two RPC nodes used by the verifier and launched a DDoS attack to force failover to the compromised nodes, tricking the DVN into approving a fraudulent cross-chain transaction.
Two follow-up drain attempts at 18:26 UTC and 18:28 UTC — each targeting an additional 40,000 rsETH (roughly $100 million) — reverted. Kelp's emergency pauser multisig froze core contracts at 18:21 UTC, 46 minutes after the initial drain. A properly configured multi-DVN setup would have required consensus across multiple independent verifiers, rendering the attack ineffective even if one DVN was compromised.
The 116,500 rsETH represented approximately 18% of the token's 630,000-unit circulating supply. According to CoinDesk, wrapped ether remains stranded across 20 chains as recovery efforts continue.
The exploit's impact extended far beyond Kelp. Within hours, at least nine protocols took emergency action:
The withdrawal pattern is significant. Outflows were not limited to rsETH-exposed protocols. According to on-chain data compiled by DeFi analysts, lending platforms on Solana and other chains with zero rsETH exposure also saw elevated withdrawals, suggesting a confidence-driven liquidity drain rather than a rational risk-off response confined to affected assets.
Aave bore the heaviest impact. Net inflows turned negative by roughly $6.2 billion, with the WETH market pinned at 100% utilization as borrowers scrambled and depositors withdrew.
After draining 116,500 rsETH from Kelp's bridge, the attacker deposited the stolen tokens on Aave V3 as collateral and borrowed wrapped ether against them. The Aave-specific borrow totaled approximately $196 million.
Twenty-four hours after the exploit, Aave carried an estimated $177 million to $236 million in bad debt, concentrated in the rsETH–WETH pair on Ethereum mainnet. According to The Defiant, Aave's Umbrella backstop reserve may not fully cover the deficit, raising the prospect that stkAAVE holders could absorb losses through the protocol's slashing mechanism.
The AAVE token dropped 17.7% on April 19, with deposits fleeing the protocol at a pace not seen since the 2022 bear market. Aave founder Stani Kulechov emphasized that the exploit was external — Aave's contracts were not compromised — and that the rsETH freeze prevents further exposure while the team reviews post-exploit borrows.
The incident raises structural questions about permissionless collateral listing. Aave accepted rsETH as collateral without direct control over the security configuration of Kelp's bridge infrastructure. The risk materialized not from Aave's own code but from the weakest link in the composability chain.
The Kelp exploit followed the $285 million Drift Protocol hack on April 1 — an attack also attributed to North Korean state-backed actors. The Drift exploit combined three vectors: fake token creation, oracle manipulation, and a compromised admin key.
Attackers created a token called "CarbonVote Token" (CVT), minted roughly 750 million units, seeded a small (~$500) liquidity pool on Raydium, and used wash trading to build a price history near $1. Over time, oracles picked up the artificial price, treating the token as legitimate. A compromised admin key enabled the final extraction: approximately $285 million drained in 12 minutes.
TRM Labs stated with medium-high confidence that the operation was carried out by the same threat actors responsible for the October 2024 Radiant Capital hack, attributed by Mandiant to UNC4736 — a North Korean state-affiliated group also tracked as AppleJeus or Citrine Sleet. Most stolen funds were bridged to Ethereum within hours via Circle's CCTP.
Drift and Kelp are the headline events, but they sit within a broader pattern. At least 12 additional DeFi protocols and crypto businesses have been attacked since April 1, according to Cointelegraph and blockchain.news:
| Date | Protocol | Loss | Vector | |------|----------|------|--------| | Apr 1 | Drift Protocol | $285M | Social engineering + oracle manipulation | | Apr 3 | Silo Finance | $392K | Oracle misconfiguration | | Apr 9 | Aethir | $423K | Access control vulnerability | | Apr 13 | Dango | $410K | Smart contract defect | | Apr 14 | CoW Swap | $1.2M | Domain hijacking | | Apr 18 | Kelp DAO | $292M | Cross-chain bridge (DVN compromise) | | Apr (various) | Rhea Finance | $7.6M | Margin trading exploit via fraudulent tokens | | Apr (various) | Zerion, Hyperbridge, BSC TMM, MONA, Grinex | Various | Multiple vectors |
Total DeFi losses in the first three weeks of April 2026 now exceed $600 million. For context, total DeFi exploit losses for all of 2025 were approximately $1.5 billion, according to Chainalysis. April 2026 alone has already reached 40% of the prior year's annual total.
The preliminary attribution of both the Drift and Kelp exploits to North Korea's Lazarus Group represents a concerning escalation. Two structurally different attack methodologies — social engineering combined with oracle manipulation (Drift) versus infrastructure compromise of cross-chain verification (Kelp) — suggest operational versatility and sustained targeting of DeFi infrastructure.
According to Elliptic, the combined $577 million drained in 18 days exceeds any comparable period of state-sponsored crypto theft. The Lazarus Group has been linked to over $6 billion in cumulative crypto theft since 2017, but the pace and scale of April 2026 operations represent an acceleration.
The use of DDoS to force RPC node failover (Kelp) and the months-long social engineering campaign to compromise an admin key (Drift) indicate that these are not opportunistic exploits. They are planned operations with infrastructure investments, intelligence gathering, and multi-week preparation timelines.
LayerZero Labs responded on April 20, attributing the Kelp exploit to Kelp's security configuration choices rather than a protocol-level vulnerability. According to CoinDesk, LayerZero stated:
The response frames the incident as an application-layer configuration failure rather than a protocol-layer bug. This distinction matters for LayerZero's broader ecosystem — over 50 OFT deployments rely on the same underlying infrastructure — but it also highlights the tension between protocol flexibility and minimum security standards. A system that permits insecure configurations will eventually see those configurations exploited.
The Kelp–Aave contagion chain exposes three structural issues in DeFi lending:
1. Collateral risk is downstream risk. Aave's contracts were not compromised. Aave's code performed as designed. Yet Aave absorbed $177M–$236M in bad debt and lost $6.6 billion in TVL because it accepted collateral whose security depended on a third party's bridge configuration. In traditional finance, collateral eligibility requires independent due diligence on the collateral's underlying infrastructure. DeFi's permissionless collateral listing process lacks equivalent safeguards.
2. Composability amplifies contagion speed. The time between the Kelp exploit (17:35 UTC) and the attacker depositing stolen rsETH on Aave to borrow WETH was measured in minutes, not hours. Composability — DeFi's core value proposition — also means that a breach in one protocol propagates to connected protocols at the speed of a blockchain transaction.
3. Confidence contagion exceeds rational contagion. Withdrawals from Solana lending protocols with zero rsETH exposure suggest that the trust deficit extends beyond direct financial risk. When depositors cannot independently verify which protocols have indirect exposure to compromised assets, the rational response is to withdraw from all protocols. This dynamic mirrors traditional bank runs.
The April 2026 DeFi hack spree — anchored by the Drift ($285M) and Kelp ($292M) exploits — represents the most concentrated period of losses the sector has experienced since the cross-chain bridge attacks of 2022. The common thread is not a single vulnerability type but a pattern of configuration-level and operational-security failures exploited by a state-backed adversary with the resources to conduct multi-week, multi-vector operations.
For DeFi lending protocols, the Kelp–Aave contagion chain demonstrates that smart contract security alone is insufficient. The security of accepted collateral depends on the entire stack beneath it — including bridge infrastructure, verifier configurations, and the operational security of third-party protocols. Until DeFi develops standardized minimum security requirements for collateral eligibility — analogous to the collateral haircut and eligibility frameworks used in traditional securities lending — similar contagion events are structurally likely to recur.
LayerZero's decision to bar 1-of-1 DVN configurations is a reactive measure addressing the proximate cause. The deeper question — whether cross-chain bridge security should be a protocol-enforced minimum or an application-layer option — remains unresolved.