← TMX TRIBE5 decisions on this page
Audit log
Every state-changing event for TMX TRIBE: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.
- #1publishby system:backfill2026-05-27 19:45:41ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 422,568,322
- sig
2pMSjBgLbffv…buWRkHLcexplorer ↗- hash
fEqfy8ihKH4T…mnaPSZbjsha256 → base58
verifying row…full verify ↗canonical bytes (5563 B) ▸
{"actor":"system:backfill","investigation_id":"c1e4e929-48a2-4614-8908-a90fa95f9fd6","kind":"publish","page_slug":"tmx-tribe","published_at":"2026-05-27T19:45:41.333Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"TMX TRIBE","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://x.com/TMXTribe/status/1920163256846479553","type":"other","url":""},{"credibility":3,"name":"https://www.globenewswire.com/news-release/2025/05/26/3088231/0/en/TRIBE-DEX-Brings-Real-DeFi-Utility-to-Life-with-TMX-TGE-Only-485-ETH-Available-After-871K-Raised.html","type":"other","url":""},{"credibility":3,"name":"https://www.weex.com/learn/articles/what-is-tribe-perpetual-tmx-coin-a-comprehensive-guide-983","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/currencies/tmx/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://rekt.news/tmztribe-rekt","type":"other","url":""},{"credibility":3,"name":"https://nulltx.com/certik-flags-1-4m-exploit-linked-to-tmx-tribe-on-arbitrum/","type":"other","url":""},{"credibility":3,"name":"https://bitcoinethereumnews.com/finance/certik-flags-1-4m-exploit-linked-to-tmx-tribe-on-arbitrum/","type":"other","url":""},{"credibility":3,"name":"https://x.com/QuillAudits_AI/status/2008459614711386457","type":"other","url":""},{"credibility":3,"name":"https://smartcontractshacking.com/hacks/tmx-tribe-hack-2026","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://rekt.news/tmztribe-rekt","type":"other","url":""},{"credibility":3,"name":"https://nulltx.com/certik-flags-1-4m-exploit-linked-to-tmx-tribe-on-arbitrum/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://rekt.news/tmztribe-rekt","type":"other","url":""},{"credibility":3,"name":"https://nulltx.com/certik-flags-1-4m-exploit-linked-to-tmx-tribe-on-arbitrum/","type":"other","url":""},{"credibility":3,"name":"https://bitcoinethereumnews.com/finance/certik-flags-1-4m-exploit-linked-to-tmx-tribe-on-arbitrum/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.globenewswire.com/news-release/2025/05/26/3088231/0/en/TRIBE-DEX-Brings-Real-DeFi-Utility-to-Life-with-TMX-TGE-Only-485-ETH-Available-After-871K-Raised.html","type":"other","url":""},{"credibility":3,"name":"https://www.globenewswire.com/news-release/2025/08/26/3139061/0/en/TMX-DEX-Announces-Token-Launch-Empowering-Global-Traders-with-100x-Opportunity.html","type":"other","url":""},{"credibility":3,"name":"https://finance.yahoo.com/news/tribe-dex-brings-real-defi-161200483.html","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://tribe-dex.com/","type":"other","url":""},{"credibility":3,"name":"https://x.com/TMXTribe","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://en.wikipedia.org/wiki/ZachXBT","type":"other","url":""}]}],"sources_used":[],"summary":"TMX TRIBE (also marketed as Tribe DEX) is a decentralized perpetual futures exchange operating on Arbitrum and Optimism that launched its TMX token in mid-2025. On January 5-7, 2026, an attacker exploited a critical logic flaw in unverified, unaudited smart contracts to drain approximately $1.4 million in user funds over 36 hours, with stolen assets subsequently bridged to Ethereum and laundered via Tornado Cash. The team deployed no emergency pause during the attack, issued no public statement for days afterward, and produced no post-mortem or user compensation plan, raising serious concerns about operational competence and transparency. ZachXBT has flagged the entity.","timeline":[{"date":"2025-05-26","event":"Tribe DEX announces public TGE for TMX token, with 485 ETH allocated after $871,000 raised in a private sale.","source":""},{"date":"2025-08-26","event":"TMX DEX announces token launch via GlobeNewswire, marketing '100x Opportunity' and referencing an unspecified 'Top 10 CEX' listing.","source":""},{"date":"2025-09-22","event":"TMX token listed on WEEX exchange as a spot trading pair (TMX/USDT).","source":""},{"date":"2026-01-05","event":"Attack begins on TMX TRIBE's Arbitrum contracts. Primary attacker address 0x763a67E4418278f84c04383071fC00165C112661 begins executing the mint-and-stake loop exploit against unverified LP contracts.","source":""},{"date":"2026-01-05","event":"CertiK Alert flags the exploit in progress. DefimonAlerts also detects anomalous activity.","source":""},{"date":"2026-01-06","event":"Exploitation continues for a second day. Team deploys contract upgrades on-chain but does not trigger an emergency pause. Approximately $1.2 million bridged to Ethereum via Across Protocol.","source":""},{"date":"2026-01-06","event":"TMX TRIBE team sends on-chain bounty message to exploiter from wallet 0x33392e39325013e81874ca7b76326858ec179543, offering 20% retention in exchange for 80% return. Exploiter does not respond.","source":""},{"date":"2026-01-07","event":"Exploitation concludes. Total loss approximately $1.4 million. Stolen funds deposited into Tornado Cash.","source":""},{"date":"2026-01-10","event":"As of at least four days post-exploit, TMX TRIBE has issued no public statement, post-mortem, or compensation plan. Rekt News publishes full incident documentation.","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision 196175fa-2d21-4f92-80f4-f6ec20b0a743 - #2rescoreby systemsystem2026-10-10 18:42:34ZScore: 18 → 40 (+22)Rescored under Scoring v2, the published formula (avoid.net/scoring): 18 → 40. Problems weighed by who is responsible: the subject's own conduct −16, incidents the subject suffered −3.2, concerns that are not fraud −3.2, problems around the subject, caused by others −2.4.anchoranchored
- chain
- ●mainnet-betaslot 455,362,196
- sig
aRhMtSR2bpxZ…3hGyTJfSexplorer ↗- hash
EbJhe5iCf5mB…aBHsUqH5sha256 → base58
verifying row…full verify ↗canonical bytes (636 B) ▸
{"actor":"system","decided_at":"2026-10-10T18:42:33.941Z","decision":"rescore","investigation_id":"c1e4e929-48a2-4614-8908-a90fa95f9fd6","new_score":40,"page_slug":"tmx-tribe","prev_score":18,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 18 → 40. Problems weighed by who is responsible: the subject's own conduct −16, incidents the subject suffered −3.2, concerns that are not fraud −3.2, problems around the subject, caused by others −2.4.","score_delta":22,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision a021a99f-511e-49c4-acb5-6aa8b8ea0f0b - #3reviewby reviewerreviewer2026-11-03 23:45:09ZScore: 40 → 40 (no score change)The core exploit narrative is supported by the Rekt News article: a $1.4M loss, the mint-and-stake loop, two attacker addresses, about $1.2M bridged and sent to Tornado Cash, no pause, a 20/80 bounty offer, unverified contracts, no audit and no statement. Two timeline dates are off (bounty message Jan 5, not Jan 6; Rekt article Jan 8, not Jan 10). The ZachXBT flag is unsupported, and the market figures are undated. The page omits the phishing link posted from the TMXTribe account. I did not fetch the pre-exploit sources.anchoranchored
- chain
- ●mainnet-betaslot 465,088,197
- sig
33AHVpT7shFV…ymz2XFMhexplorer ↗- hash
6ZMWdqirL6ue…bgyMj68Msha256 → base58
verifying row…full verify ↗canonical bytes (1375 B) ▸
{"actor":"reviewer","artifact_identity":"ec40707f52a124861b0131ed88d46242","decided_at":"2026-11-03T23:45:09.327Z","decision":"review","disputed_pct":0.5556,"findings_hash":"79Vipd6izhamYD9fhwvCBcPHAVBh7FkTETMuhkc5izGD","investigation_id":"c1e4e929-48a2-4614-8908-a90fa95f9fd6","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":40,"omissions":{"material":1,"total":2},"page_content_hash":"c1273e6869c626a90df3b75445412827417728848c9cc5af8f8614209bfacd84","page_slug":"tmx-tribe","prev_score":40,"reason":"The core exploit narrative is supported by the Rekt News article: a $1.4M loss, the mint-and-stake loop, two attacker addresses, about $1.2M bridged and sent to Tornado Cash, no pause, a 20/80 bounty offer, unverified contracts, no audit and no statement. Two timeline dates are off (bounty message Jan 5, not Jan 6; Rekt article Jan 8, not Jan 10). The ZachXBT flag is unsupported, and the market figures are undated. The page omits the phishing link posted from the TMXTribe account. I did not fetch the pre-exploit sources.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision ffa71270-3e5f-4eab-8e8a-f295b9050c96 - #4review reviseby judgejudge2026-11-03 23:45:09ZScore: 40 → 40 (no score change)Of 9 checked claims, 2 were disputed (claim_findings[0] bounty date is Jan 5 not Jan 6; claim_findings[1] Rekt article is dated Jan 8 not Jan 10) and 3 could not be verified (claim_findings[5] the ZachXBT flag, [7] the 'some analysts' attribution, [8] an undated live price), giving 55.6% disputed or unverifiable. The core exploit account (about $1.4M loss, attacker addresses, no pause, no audit) is confirmed by Rekt News and CertiK coverage (claim_findings[4]), so the penalty sits in the lower half of the significant band. The ZachXBT claim in the summary has no supporting source, and the page omits the phishing link posted from the project's own account.anchoranchored
- chain
- ●mainnet-betaslot 465,088,203
- sig
Na7cmyB3NMQ3…c6opX4GUexplorer ↗- hash
ATwnTzUpw9t7…LQG6cEttsha256 → base58
verifying row…full verify ↗canonical bytes (1693 B) ▸
{"actor":"judge","artifact_identity":"ec40707f52a124861b0131ed88d46242","band_override":null,"decided_at":"2026-11-03T23:45:09.327Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5556,"investigation_id":"c1e4e929-48a2-4614-8908-a90fa95f9fd6","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":40,"page_slug":"tmx-tribe","prev_score":40,"reason":"Of 9 checked claims, 2 were disputed (claim_findings[0] bounty date is Jan 5 not Jan 6; claim_findings[1] Rekt article is dated Jan 8 not Jan 10) and 3 could not be verified (claim_findings[5] the ZachXBT flag, [7] the 'some analysts' attribution, [8] an undated live price), giving 55.6% disputed or unverifiable. The core exploit account (about $1.4M loss, attacker addresses, no pause, no audit) is confirmed by Rekt News and CertiK coverage (claim_findings[4]), so the penalty sits in the lower half of the significant band. The ZachXBT claim in the summary has no supporting source, and the page omits the phishing link posted from the project's own account.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission (claim_findings do not cover it): the TMXTribe X account posted a link to a site flagged as phishing on 2026-01-07 and the page does not mention it. This confirms the significant band rather than lowering it; the percentage band is already significant."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision cd501630-e86c-4f26-b9bc-6e304d71c7ae - #5rescoreby systemsystem2026-11-03 23:45:10ZScore: 40 → 49 (+9)Recalculated after the fact-check of 2026-11-03. Rescored under Scoring v2, the published formula (avoid.net/scoring): 40 → 49. Problems weighed by who is responsible: the subject's own conduct −8, incidents the subject suffered −3.2, concerns that are not fraud −3.2, problems around the subject, caused by others −1.6; 2 section(s) set aside until a failed fact-check is resolved.anchoranchored
- chain
- ●mainnet-betaslot 465,088,208
- sig
2aNRvuyZbZr8…4DXyaWvGexplorer ↗- hash
3AnV9UXQJwCW…VxMv3958sha256 → base58
verifying row…full verify ↗canonical bytes (745 B) ▸
{"actor":"system","decided_at":"2026-11-03T23:45:09.327Z","decision":"rescore","investigation_id":"c1e4e929-48a2-4614-8908-a90fa95f9fd6","new_score":49,"page_slug":"tmx-tribe","prev_score":40,"reason":"Recalculated after the fact-check of 2026-11-03. Rescored under Scoring v2, the published formula (avoid.net/scoring): 40 → 49. Problems weighed by who is responsible: the subject's own conduct −8, incidents the subject suffered −3.2, concerns that are not fraud −3.2, problems around the subject, caused by others −1.6; 2 section(s) set aside until a failed fact-check is resolved.","score_delta":9,"score_model":"v2","sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 8f67ed81-7885-4335-bb24-350e135c9662
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine —
python -m src.verify_decision <event_id>.