Fact-check findings
What an automated fact-checker found when it re-read KelpDAO Bridge Exploit (April 2026) against the sources the page cites. Only the most recent review is shown.
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed
1 claimThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #26[disputed][awaiting moderator]in section: Broader Industry Impact and Security Implications
“Crypto.news reported that DeFi protocols had lost $1.3 billion to hacks in 2026 by mid-year, with the KelpDAO incident accounting for the majority of that total.”
reviewerCrypto.news reported DeFi lost $1.3 billion to hacks in 2026 by mid-year, with KelpDAO accounting for the majority.The cited source directly contradicts the page's characterization — KelpDAO alone is roughly a fifth of the total, not a majority, by the cited article's own figures.Proposed correction (not yet applied)Crypto.news reported that DeFi protocols had lost $1.3 billion to hacks in 2026 by mid-year, with the KelpDAO and Drift Protocol incidents — both linked to Lazarus Group — together accounting for roughly 44% of that total.
unverifiable
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #4[unverifiable][awaiting moderator]in section: Incident Overview
“making it the largest single DeFi exploit recorded in 2026, according to reporting by Bloomberg, CoinDesk, and Chainalysis.”
reviewerBloomberg, CoinDesk, and Chainalysis reported this as the largest single DeFi exploit of 2026.CoinDesk's and Chainalysis's framing of this as the year's biggest DeFi exploit is well corroborated. I could not locate a specific Bloomberg article making this claim in multiple searches, so that part of the attribution is unverifiable rather than confirmed or false.
link rot
2 claimsA cited source no longer resolves or no longer says what the page attributes to it.
- #27[link rot][awaiting moderator]in the cited sources
“https://www.kucoin.com/news/flash/defi-united-raises-160m-to-cover-aave-bad-debt-from-kelpdao-exploit”
reviewerSource URL for the KuCoin 'DeFi United raises $160M' article is live and supports cited claims.The live URL is dead. An archived snapshot already exists in this same record's archive_url field and resolves; the live URL should be replaced with it.Proposed correction (not yet applied)http://web.archive.org/web/20260727173437/https://www.kucoin.com/news/flash/defi-united-raises-160m-to-cover-aave-bad-debt-from-kelpdao-exploit - #28[link rot][awaiting moderator]in section: Recovery Effort: DeFi United Coalition
“https://www.kucoin.com/news/flash/defi-united-raises-160m-to-cover-aave-bad-debt-from-kelpdao-exploit”
reviewerSource URL for the KuCoin article cited in the Recovery Effort section is live.Same dead link as the sources_used entry; same fix applies — this is the duplicate citation inside the Recovery Effort section's sources list.Proposed correction (not yet applied)http://web.archive.org/web/20260727173437/https://www.kucoin.com/news/flash/defi-united-raises-160m-to-cover-aave-bad-debt-from-kelpdao-exploit
partially supported
6 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: Incident Overview
“The drain was completed within approximately 46–80 minutes before detection and emergency intervention halted further outflows.”
reviewerThe drain took approximately 46-80 minutes before detection and halt.Every source found (CoinDesk, Chainalysis, Hypernative, The Block) converges on a 46-minute window to the emergency pause. No source supports an 80-minute upper bound; the range appears padded beyond what is documented. - #8[partially supported][awaiting moderator]in section: Attribution: North Korea's TraderTraitor Unit
“LayerZero Labs, Mandiant, CrowdStrike, Elliptic, and Chainalysis jointly attributed the attack with high confidence to TraderTraitor (also tracked as UNC4899), a DPRK-aligned threat actor assessed to be part of North Korea's Reconnaissance General Bureau and a subgroup of the broader Lazarus Group.”
reviewerLayerZero Labs, Mandiant, CrowdStrike, Elliptic, and Chainalysis jointly attributed the attack to TraderTraitor/UNC4899.Mandiant, CrowdStrike, Chainalysis, and LayerZero attribution is confirmed via LayerZero's own incident report, but no source consulted — cited or independently searched — credits Elliptic with attributing this specific incident to TraderTraitor/UNC4899. - #9[partially supported][awaiting moderator]in section: Attribution: North Korea's TraderTraitor Unit
“TraderTraitor was previously linked to the Axie Infinity Ronin Bridge exploit (2022) and the WazirX compromise (2024).”
reviewerTraderTraitor was previously linked to the 2022 Ronin Bridge exploit and the 2024 WazirX compromise.The Ronin Bridge/TraderTraitor link (2022) is well documented (FBI attribution). The WazirX (2024) link to the specific TraderTraitor sub-group, as opposed to Lazarus Group broadly, was not corroborated in sources found. - #11[partially supported][awaiting moderator]in section: On-Chain Fund Movements and DeFi Contagion
“the attacker deposited approximately 89,567 rsETH into Aave V3 as collateral and immediately borrowed approximately $190–$236 million in WETH across multiple Aave deployments before markets could reprice the unbacked tokens or freeze the relevant pools.”
reviewerThe attacker deposited ~89,567 rsETH into Aave V3 and borrowed ~$190-236 million in WETH.The $190 million lower bound and the general mechanism are supported; the $236 million upper bound, the WETH-specific framing, and the 89,567 rsETH collateral figure are not matched precisely by the cited source, and a different figure (107,000 rsETH) appears in other reporting. - #13[partially supported][awaiting moderator]in section: On-Chain Fund Movements and DeFi Contagion
“Reporting from CoinDesk and The Block documented that the resulting DeFi contagion triggered more than $10 billion in aggregate deposit withdrawals from Aave and related protocols as users rushed to exit exposure.”
reviewerDeFi contagion triggered more than $10 billion in aggregate deposit withdrawals from Aave and related protocols.A >$10 billion figure is defensible from other reporting (DeFiLlama TVL decline), but it is not what the specifically cited CoinDesk article says (~$6 billion in net withdrawals); figures across outlets range from $6.2B to $15B depending on metric and date. - #14[partially supported][awaiting moderator]in the timeline
“Aave V3 freezes all rsETH and wrsETH reserves across deployments, sets LTV to zero. DeFi contagion triggers reported $8–10 billion in deposit outflows from Aave. Bloomberg reports incident as largest crypto hack of 2026.”
reviewerAave V3 froze reserves on 2026-04-19; contagion triggered $8-10B in deposit outflows; Bloomberg called it largest 2026 hack.Same underlying overstatement of the Aave outflow figure as the one in sections[3]; freeze/LTV-zero actions are independently confirmed, but the $8-10B figure and the Bloomberg attribution are not supported by the cited source.
confirmed
18 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Incident Overview
“At approximately 17:35 UTC on April 18, 2026, an attacker submitted a forged LayerZero cross-chain message claiming that 116,500 rsETH had been burned on the source chain (Unichain). No such burn transaction existed.”
reviewerAt approximately 17:35 UTC on April 18, 2026, an attacker submitted a forged LayerZero message claiming 116,500 rsETH had been burned on Unichain, which was false.Time, amount, and forged-burn mechanism are corroborated by both cited sources and independent reporting (The Block, Hypernative). - #2[confirmed][no action needed]in section: Incident Overview
“KelpDAO's bridge escrow on Ethereum accepted the forged attestation and released 116,500 rsETH — approximately 18% of the token's circulating supply and 74.3% of the total bridge escrow balance — to the attacker's address.”
reviewer116,500 rsETH released was ~18% of circulating supply and 74.3% of total bridge escrow balance.Both figures independently confirmed by their respective cited sources. - #5[confirmed][no action needed]in section: Attack Method and Technical Details
“First, beginning on or around March 6, 2026, a LayerZero Labs developer was socially engineered into cloning a malicious GitHub repository, which installed malware on their macOS system.”
reviewerThe attack unfolded in stages beginning with social engineering of a LayerZero developer on/around March 6, 2026, leading to RPC/DVN compromise.Directly confirmed by LayerZero's own incident-report blog, which I was able to fetch and read in full. - #6[confirmed][no action needed]in section: Attack Method and Technical Details
“Hypernative's analysis confirmed that the total drained amount exceeded the entire Unichain rsETH supply at the time by a factor of approximately 2,300.”
reviewerHypernative found the drained amount exceeded Unichain's entire rsETH supply by a factor of ~2,300.Confirmed verbatim against the cited source. - #7[confirmed][no action needed]in the summary
“Security firms Mandiant, CrowdStrike, and Chainalysis, as well as LayerZero Labs, attributed the attack with high confidence to TraderTraitor (UNC4899), a North Korean state-linked threat actor operating under the Lazarus Group umbrella.”
reviewerMandiant, CrowdStrike, Chainalysis, and LayerZero Labs attributed the attack with high confidence to TraderTraitor (UNC4899).Confirmed via LayerZero's primary incident report, which names Mandiant and CrowdStrike explicitly alongside its own and Chainalysis's attribution. - #10[confirmed][no action needed]in section: Attribution: North Korea's TraderTraitor Unit
“pre-funding of the attacker wallet via Tornado Cash approximately eight hours before execution, and on-chain fund movement patterns consistent with prior Lazarus Group operations.”
reviewerThe attacker's wallet was pre-funded via Tornado Cash approximately eight hours before execution.Confirmed. - #12[confirmed][no action needed]in section: On-Chain Fund Movements and DeFi Contagion
“This created an estimated $123–$230 million in bad debt for Aave V3, with WETH pools across five chains reaching 100% utilization.”
reviewerThe exploit created an estimated $123-230 million in bad debt for Aave V3, with WETH pools across five chains reaching 100% utilization.Range matches the cited source. - #15[confirmed][no action needed]in section: Responsibility Dispute: KelpDAO vs. LayerZero
“LayerZero's initial post-exploit statement blamed KelpDAO, asserting the protocol had ignored repeated recommendations to adopt a multi-verifier setup, and that Kelp had specifically downgraded from a 2-of-2 DVN configuration to a 1-of-1 configuration prior to the attack.”
reviewerLayerZero initially blamed KelpDAO for downgrading from a 2-of-2 to a 1-of-1 DVN configuration.Confirmed via independent reporting of LayerZero's stated position. - #16[confirmed][no action needed]in section: Responsibility Dispute: KelpDAO vs. LayerZero
“In a detailed memo published on or around May 5, 2026, KelpDAO asserted that LayerZero personnel had directly approved the single-verifier configuration across approximately eight integration meetings spanning roughly two and a half years, and that LayerZero's own V2 OApp Quickstart documentation listed single-DVN setups without flagging them as insecure for high-value deployments.”
reviewerKelpDAO's May 5, 2026 memo said LayerZero approved the setup across ~8 meetings over ~2.5 years and that the Quickstart docs listed single-DVN setups.Confirmed verbatim against the cited CoinDesk article. - #17[confirmed][no action needed]in section: Responsibility Dispute: KelpDAO vs. LayerZero
“Independent security researcher Artem K (a Yearn Finance developer) reviewed LayerZero's deployment code and stated that the V2 OApp Quickstart shipped with single-source verification defaults across multiple networks, supporting KelpDAO's characterization.”
reviewerSecurity researcher Artem K, a Yearn Finance developer, found LayerZero's V2 OApp Quickstart shipped with single-source verification defaults.Not found in the sources specifically cited for this section, but independently corroborated: Artem K (known as @banteg on X, a Yearn Finance core developer) is widely reported to have reviewed LayerZero's public deployment code and found the V2 OApp Quickstart defaulted to single-source verification across several chains. The underlying fact checks out even though the page's listed sources don't carry it. - #18[confirmed][no action needed]in section: Responsibility Dispute: KelpDAO vs. LayerZero
“Chainlink manager Zach Rynes publicly accused LayerZero of deflecting responsibility for its compromised infrastructure.”
reviewerChainlink community manager Zach Rynes accused LayerZero of deflecting responsibility.Confirmed; his title is 'community manager' which the page shortens to 'manager' — an immaterial simplification. - #19[confirmed][no action needed]in section: Responsibility Dispute: KelpDAO vs. LayerZero
“Approximately 47% of 2,665 active LayerZero OApp contracts used a 1-of-1 DVN setup within 90 days of the incident, representing roughly $4.5 billion in ecosystem exposure, according to data cited by Unchained Crypto.”
reviewerAbout 47% of 2,665 active LayerZero OApp contracts used a 1-of-1 DVN setup, representing ~$4.5 billion in ecosystem exposure.Confirmed; figure matches multiple independent reports of the same Dune dataset. - #20[confirmed][no action needed]in section: Responsibility Dispute: KelpDAO vs. LayerZero
“The company stated: 'We made a mistake by allowing our DVN to act as a 1/1 DVN for high-value transactions. We didn't police what our DVN was securing, which created a risk we simply didn't see. We own that.'”
reviewerLayerZero publicly stated it made a mistake allowing its DVN to act as a 1/1 DVN, quoting a specific apology.Exact quote verified against LayerZero's primary 'an overdue apology' blog post. - #21[confirmed][no action needed]in section: Responsibility Dispute: KelpDAO vs. LayerZero
“LayerZero subsequently announced that its DVN would no longer service 1-of-1 configurations and that all defaults were being migrated to a minimum of 3-of-3 and up to 5-of-5 where possible.”
reviewerLayerZero announced it will no longer service 1-of-1 configurations and is migrating defaults to a minimum of 3-of-3 and up to 5-of-5.Confirmed verbatim. - #22[confirmed][no action needed]in section: Recovery Effort: DeFi United Coalition
“Participating organizations included Aave DAO, Mantle, Lido DAO, EtherFi, and LayerZero. The coalition aimed to raise sufficient ETH to restore rsETH's backing ratio and cover Aave's bad debt, with reported contributions including 25,000 ETH from the Aave DAO, a 30,000 ETH loan from Mantle, and personal contributions from individuals including Aave founder Stani Kulechov.”
reviewerDeFi United coalition included Aave DAO, Mantle, Lido DAO, EtherFi, and LayerZero, with 25,000 ETH from Aave DAO, a 30,000 ETH loan from Mantle, and personal contributions including Stani Kulechov.All named participants and contribution figures check out across independent reporting, though the specific 25,000/30,000 ETH figures come from other outlets rather than the single cited CoinDesk article. - #23[confirmed][no action needed]in section: Recovery Effort: DeFi United Coalition
“Reporting from KuCoin and The Block indicated that DeFi United raised over $160 million to $300 million in ETH across tranches.”
reviewerDeFi United raised over $160 million to $300 million in ETH across tranches, per KuCoin and The Block.Range is corroborated, though the KuCoin URL itself is now dead (see separate link_rot finding). - #24[confirmed][no action needed]in section: Recovery Effort: DeFi United Coalition
“The final tranche of 20,373.7 rsETH was transferred to the LayerZero lockbox contract, completing the recovery approximately five weeks after the exploit.”
reviewerrsETH was fully restored on May 25, 2026, with a final 20,373.7 rsETH tranche completing recovery ~5 weeks after the exploit.Confirmed, with a negligible rounding difference (20,373.7 vs. 20,373.72). - #25[confirmed][no action needed]in section: KelpDAO's Infrastructure Response: Migration to Chainlink CCIP
“The migration to Chainlink CCIP was reported by Unchained Crypto and Bitcoin.com News on or around May 5, 2026.”
reviewerKelpDAO's migration to Chainlink CCIP was reported by Unchained Crypto and Bitcoin.com News on or around May 5, 2026.Dates are approximate but consistent with both cited outlets.