Skip to main content
AVOID.NET

Fact-check findings

What an automated fact-checker found when it re-read KelpDAO vs. LayerZero — Civil Lawsuit (September 2026) against the sources the page cites. Only the most recent review is shown.

Read this first

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.

unverifiable 3partially supported 3confirmed 30 corrections pending · 0 applied

unverifiable

3 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #6[unverifiable][awaiting moderator]in the timeline
    “Attackers (attributed with preliminary confidence to North Korea's TraderTraitor/Lazarus Group) compromise LayerZero RPC nodes used by the Kelp bridge verifier via social engineering of a developer, according to LayerZero's post-mortem.”
    reviewerA March 2026 RPC node compromise via social engineering of a developerThe cited Unchained article supports neither the 2026-03-01 date nor the developer social-engineering detail. The LayerZero post-mortem itself was not fetched.
  2. #7[unverifiable][awaiting moderator]in the timeline
    “Aave reports restoration of rsETH backing, following DeFi ecosystem recovery efforts addressing the approximately $177 million in bad debt created when stolen rsETH was used as collateral.”
    reviewerAave reported restoration of rsETH backing on 2026-06-01 and bad debt was about $177 millionThe cited source was blocked, so I searched alternatives. I found no confirmation of the $177M figure or of a June 1 restoration. The source is a September lawsuit article, which makes a June 1 event odd. The section 4 text repeats the $177 million figure.
  3. #9[unverifiable][awaiting moderator]in the summary
    “represents the first major civil litigation in Canada seeking to hold a DeFi messaging-layer infrastructure provider directly liable for an exploit loss”
    reviewerFirst major civil litigation in Canada holding a DeFi messaging-layer provider liableA superlative 'first' claim that no reporting I found supports. It is unattributed on the page.

partially supported

3 claims

The cited evidence supports part of the claim but not all of it.

  1. #1[partially supported][awaiting moderator]in the summary
    “On September 24, 2026, Evercrest Technologies Inc. (the operator of KelpDAO) filed a civil claim in the Supreme Court of British Columbia against LayerZero Labs Ltd. and its co-founder and CEO Bryan Pellegrino”
    reviewerEvercrest filed on September 24, 2026 against LayerZero Labs Ltd. and Pellegrino (defendant list complete)Court, plaintiff and Pellegrino confirmed. Sources differ slightly on the filing day (notice dated Sept 24 per Unchained; 'Wednesday' per Decrypt). Decrypt also lists LayerZero Labs Canada Inc. as a defendant, which the page omits.
  2. #2[partially supported][awaiting moderator]in section: Civil Lawsuit: Evercrest Technologies v. LayerZero Labs Ltd. and Bryan Pellegrino
    “(case number 267169)”
    reviewerCase number is 267169A search surfaced one report tying file number 267169 to the Vancouver Law Courts. CoinDesk, Unchained and Decrypt give no number. Single-source.
  3. #8[partially supported][awaiting moderator]in section: Parallel Proceedings: U.S. Frozen Funds Litigation
    “As of the filing of this investigation, the New York proceedings remain active and no final disposition of the frozen funds has been reported.”
    reviewerU.S. frozen-funds litigation remains active and no disposition has been reportedOverall framing is plausible, but the page omits a later order permitting a DAO vote to move the funds to Aave. Sourced from a snippet and a summary with no visible date, so the correction is hedged and the order date is not given. The May 1 restraining order and the roughly $71M / 30,766 ETH figures are consistent with the reporting I saw.

confirmed

3 claims

The cited evidence supports the claim as written.

  1. #3[confirmed][no action needed]in section: Civil Lawsuit: Evercrest Technologies v. LayerZero Labs Ltd. and Bryan Pellegrino
    “No specific damages figure is pleaded, but the complaint alleges the exploit and LayerZero's public statements inflicted 'tens of millions of dollars of damages' on Evercrest.”
    reviewerThe complaint pleads negligence, negligent misrepresentation and defamation, with no specific damages figure, alleging 'tens of millions of dollars of damages'Matches Unchained. Decrypt lists itemised loss heads, which the page does not mention.
  2. #4[confirmed][no action needed]in section: Civil Lawsuit: Evercrest Technologies v. LayerZero Labs Ltd. and Bryan Pellegrino
    “Pellegrino responded publicly that the claim is 'meritless' and stated he would 'defend myself accordingly' in Vancouver.”
    reviewerPellegrino called the claim meritless and said he would defend himself in VancouverSupported.
  3. #5[confirmed][no action needed]in section: Background: The April 18, 2026 rsETH Bridge Exploit
    “The bridge released 116,500 rsETH to an attacker-controlled address at 17:35 UTC; KelpDAO's emergency multisig paused core contracts at 18:21 UTC, approximately 46 minutes later.”
    reviewerExploit timing: drain at 17:35 UTC, pause 46 minutes later, follow-ups blocked at 18:26 and 18:28The 18:21 figure is the 17:35 time plus 46 minutes, an arithmetic derivation. The rest is stated in the source. The 'two follow-up attempts targeting approximately 40,000 rsETH' wording is also fine, though the source gives about 40,000 per attempt.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.