Skip to main content
AVOID.NET
← TMX TRIBEreviewed 2026-11-03 · 9 claims checked

Fact-check findings

What an automated fact-checker found when it re-read TMX TRIBE 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

2 claims

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. #1[disputed][awaiting moderator]in the timeline
    “2026-01-06”
    reviewerThe team's on-chain bounty offer (keep 20%, return 80%) was sent on 2026-01-06Rekt dates the bounty message to January 5, not January 6. The 20%/80% terms and the wallet address match.
    Proposed correction (not yet applied)
    2026-01-05
  2. #2[disputed][awaiting moderator]in the timeline
    “Rekt News publishes full incident documentation.”
    reviewerRekt News published its full incident documentation on 2026-01-10The Rekt article is dated 8 January 2026. The event is placed on 2026-01-10 in the timeline.
    Proposed correction (not yet applied)
    Rekt News publishes full incident documentation on 2026-01-08.

unverifiable

3 claims

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

  1. #6[unverifiable][awaiting moderator]in the summary
    “ZachXBT has flagged the entity.”
    reviewerZachXBT has flagged TMX TRIBENo source links ZachXBT to TMX TRIBE. The page itself admits the flag was not located. The only cited source is his Wikipedia biography.
  2. #8[unverifiable][awaiting moderator]in section: Token Sale and Marketing Practices
    “language that some analysts have flagged as indicative of speculative or misleading marketing.”
    reviewerMarketing language 'some analysts have flagged' as misleadingNo analyst commentary is cited and none was found. This is a vague attribution.
  3. #9[unverifiable][awaiting moderator]in section: Platform Overview
    “As of the most recent data, the live TMX price was approximately $7.57 USD with a 24-hour trading volume of roughly $59,000.”
    reviewerLive TMX price about $7.57 and 24h volume about $59,000A live market figure with no date; it cannot be verified as of a stated time and is likely stale.

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: January 2026 Smart Contract Exploit ($1.4 Million)
    “This cycle was repeated systematically across 502 transactions over 36 hours.”
    reviewerAttacker executed 502 transactions over 36 hoursThe 502 figure matches Rekt. The duration is inconsistent in the source itself. The page does not mention the Jan 3 funding.
  2. #4[partially supported][awaiting moderator]in section: January 2026 Smart Contract Exploit ($1.4 Million)
    “Drained assets included USDT, wrapped SOL, and WETH.”
    reviewerDrained assets included USDT, wrapped SOL and WETH; about $1.2M bridged via AcrossThe $1.2M Across bridge and Tornado Cash laundering are supported. Wrapped SOL was not seen in the source, and WBTC was bridged but is not listed on the page.
  3. #7[partially supported][awaiting moderator]in section: Team Conduct During and After the Exploit
    “The absence of any public acknowledgment of a $1.4 million loss from user funds is consistent with behavior documented in exit scam or gross negligence scenarios, though the precise characterization remains alleged.”
    reviewerAbsence of statement is consistent with exit scam behaviourThe silence is supported. The exit-scam characterization is the page's own inference, and the page hedges it.

confirmed

1 claim

The cited evidence supports the claim as written.

  1. #5[confirmed][no action needed]in section: January 2026 Smart Contract Exploit ($1.4 Million)
    “On January 5-7, 2026, TMX TRIBE suffered a critical security incident resulting in the loss of approximately $1.4 million in user funds.”
    reviewerAttack, primary and secondary addresses, 1.4M loss, mint-and-stake loop, no pause, bounty wallet, unverified and unaudited contracts, GMX fork, no public statementThe core incident facts match Rekt and the CertiK coverage found in search.
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.