Skip to main content
AVOID.NET
← Fake Trezor Support Social Engineering — $282M Heistreviewed 2026-11-04 · 7 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Fake Trezor Support Social Engineering — $282M Heist 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.

disputed

1 claim

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #5[disputed][awaiting moderator]in the timeline
    “2026-02-16”
    reviewerLetter campaign surfaced Feb 16, 2026Cited BleepingComputer article is dated Feb 14, 2026, two days before the timeline date.
    Proposed correction (not yet applied)
    2026-02-14

unverifiable

2 claims

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

  1. #4[unverifiable][awaiting moderator]in section: Suspect Status and Attribution
    “Security firm ZeroShadow traced and attributed approximately $2 million of funds”
    reviewerZeroShadow traced and attributed about $2 million of fundsNo $2M figure found in fetched sources.
  2. #7[unverifiable][awaiting moderator]in section: Historical Context: Record-Breaking Theft
    “Malone Lam (20, of Singapore) and Jeandiel Serrano (21, of Los Angeles) were charged by the U.S. Department of Justice in September 2024”
    reviewerRecord previously $243M Genesis creditor Aug 2024; two charged Sept 2024Not fetched within time; consistent with my background knowledge but not independently checked here.

partially supported

1 claim

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

  1. #6[partially supported][awaiting moderator]in the summary
    “Stolen funds were laundered through ThorChain, multiple instant exchanges, and converted predominantly into Monero”
    reviewerStolen funds were laundered only via ThorChain, instant exchanges and Monero (Tornado Cash not mentioned); also page says no ETH mixingAccurate but incomplete; some funds reportedly went through Tornado Cash.

confirmed

3 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Incident Overview
    “At approximately 23:00 UTC on January 10, 2026, an unknown individual lost approximately 1,459 Bitcoin (valued at roughly $139 million) and 2.05 million Litecoin (valued at roughly $153 million), totalling approximately $282 million.”
    reviewerTheft occurred about 23:00 UTC on Jan 10, 2026: 1,459 BTC and 2.05M LTC, about $282M, flagged by ZachXBTCoinDesk matches date, time, amounts and ZachXBT flagging.
  2. #2[confirmed][no action needed]in section: Money Laundering: ThorChain, Instant Exchanges, and Monero Conversion
    “The attacker then converted large portions of the stolen funds into Monero (XMR) through multiple instant exchange platforms.”
    reviewerLaundering via ThorChain to ETH/XRP/LTC and conversion to Monero via instant exchangesSupported. CoinDesk says XMR rose about 70% over four days.
  3. #3[confirmed][no action needed]in section: Money Laundering: ThorChain, Instant Exchanges, and Monero Conversion
    “was able to freeze approximately $700,000 worth of assets within approximately 20 minutes of the theft before conversion to privacy coins was complete”
    reviewerZeroShadow froze about $700,000 within about 20 minutesFinanceFeeds supports. Note the cited CoinDesk article does not mention it.
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.