Skip to main content
AVOID.NET
← Trinity Walletreviewed 2026-11-03 · 8 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Trinity Wallet 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 20 corrections pending · 0 applied

unverifiable

3 claims

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

  1. #5[unverifiable][awaiting moderator]in section: Losses and Victim Impact
    “Affected users who had opened Trinity Wallet between December 17, 2019 and February 17, 2020 were considered at risk.”
    reviewerAffected at-risk window of Dec 17, 2019 to Feb 17, 2020Dates not found in the cited Part 1 post. Part 2 (migration plan) was not checked and may contain them.
    citedblog.iota.org/trinity-attack-incident-pa…ps-8c7ccc4d81e8/
  2. #6[unverifiable][awaiting moderator]in section: Deprecation and Current Status
    “Prior to its deprecation, Trinity had recorded over 160,000 downloads and processed more than $1.8 billion in IOTA transactions across its lifetime.”
    reviewerTrinity recorded over 160,000 downloads and processed more than $1.8 billion in transactionsThe GitHub page has no such figures, and none were found in search. Unsupported by cited sources.
    citedgithub.com/iotaledger/trinity-wallet/blog.iota.org/the-next-steps-for-trinity-f9af3fc64736/
  3. #7[unverifiable][awaiting moderator]in section: ZachXBT Flag and Broader Community Concern
    “Trinity Wallet has been flagged by on-chain investigator ZachXBT as a notable incident in the history of crypto security failures.”
    reviewerZachXBT flagged Trinity WalletNo evidence found of any ZachXBT flag. The only cited source is a Medium article about supply chain attacks, which is unlikely to mention ZachXBT. The whole section's premise is unsupported.
    citedmedium.com/cryptronics/what-recent-suppl…ity-36f63876b539

partially supported

3 claims

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

  1. #3[partially supported][awaiting moderator]in section: Supply Chain Attack — MoonPay SDK Compromise (February 2020)
    “The IOTA Foundation's post-incident report named MoonPay 19 times”
    reviewerThe post-incident report named MoonPay 19 timesThe quote and substance are supported, but the specific count of 19 was not reproduced (17 found in Part 1). Low-value detail; consider removing the count.
    citedblog.iota.org/trinity-attack-incident-pa…ps-8c7ccc4d81e8/
  2. #4[partially supported][awaiting moderator]in section: Attack Timeline and Technical Mechanics
    “The IOTA Foundation reported the incident to the Berlin Police Cyber Division, the German Center for Cybercrime, Maltese authorities, and the U.S. Federal Bureau of Investigation.”
    reviewerFoundation reported the incident to Berlin Police Cyber Division, German Center for Cybercrime, Maltese authorities, and FBIBroadly supported; the source also names UK police, which the page omits.
    citedblog.iota.org/trinity-attack-incident-pa…ps-8c7ccc4d81e8/
  3. #8[partially supported][awaiting moderator]in section: Deprecation and Current Status
    “Trinity Wallet was officially deprecated on April 28, 2021 in conjunction with the IOTA Chrysalis protocol upgrade.”
    reviewerTrinity deprecated April 28, 2021 with Chrysalis; repository archivedDeprecation with Chrysalis and Firefly replacement are supported by IOTA's blog; the exact day is not stated by the cited GitHub page. README wording is 'Trinity is now deprecated. Please use Firefly.' on the page fetched.
    citedgithub.com/iotaledger/trinity-wallet/

confirmed

2 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Attack Timeline and Technical Mechanics
    “The active attack on Trinity users began January 25, 2020, when the attacker began delivering malicious code via the CDN.”
    reviewerCore attack dates (Nov 27 2019, Dec 22 2019, Jan 25 2020, Feb 11, Feb 12, Feb 15 2020) match the IOTA Foundation postDates in the timeline sequence match the primary source.
    citedblog.iota.org/trinity-attack-incident-pa…ps-8c7ccc4d81e8/
  2. #2[confirmed][no action needed]in section: Losses and Victim Impact
    “The IOTA Foundation confirmed that 50 independent user seeds were compromised, representing the total known victim population.”
    reviewer50 seeds and 8.55 Ti stolen; 28 Gi packages to stay under KYC thresholdsMatches primary source.
    citedblog.iota.org/trinity-attack-incident-pa…ps-8c7ccc4d81e8/
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.