Skip to main content
AVOID.NET

Audit log

Every state-changing event for World Mobile Token (WMTx) — SingularityNET Bridge Key Compromise: 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.

  1. #1publishby system:backfill
    2026-09-29 23:06:20Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 451,784,596
    sig
    5s5JafMuCLSs…Rdr4D6tWexplorer ↗
    hash
    4CBet2mP3yYc…4LcD3TSZsha256 → base58
    verifying row…full verify ↗
    canonical bytes (22702 B) ▸
    {"actor":"system:backfill","investigation_id":"68c31745-7e93-46e5-90b3-8250d884cf08","kind":"publish","page_slug":"world-mobile-token-wmtx-singularitynet-bridge-key-compromise","published_at":"2026-09-29T23:06:20.282Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"World Mobile Token (WMTx) — SingularityNET Bridge Key Compromise","sections":[{"content":"World Mobile Token (originally WMT on Cardano, rebranded WMTx in September 2025 when it expanded to Base, Ethereum, and BNB Chain) is the native utility token of World Mobile Group, a telecommunications and blockchain infrastructure company founded by Micky Watkins and Antonio H. The token supports a decentralized wireless network. Like several AI-alliance projects — including SingularityNET (AGIX), Fetch.ai (FET), and NuNet (NTX) — WMTx used the SingularityNET Ethereum-Cardano bridge for cross-chain transfers. That shared dependency exposed WMTx holders to infrastructure risks outside World Mobile Chain's direct control.","heading":"Background: World Mobile Token and the SingularityNET Bridge","severity":"low","sources":[{"credibility":1,"name":"WMT Is Now WMTx — World Mobile Token Goes Multichain","type":"official","url":"https://worldmobile.io/blog/post/world-mobile-token-migrates-to-base-ethereum-and-bnb-chain"},{"credibility":2,"name":"Bridges, Explained: The Hack That Hit World Mobile, and Why They Keep Breaking","type":"news_article","url":"https://bagster.substack.com/p/bridges-explained-the-hack-that-hit"}]},{"content":"On the afternoon of September 19, 2026, an attacker reportedly began automated scanning of SingularityNET's systems, gained access to its Amazon Web Services account, and escalated privileges to administrator level, according to reporting by Bagster (Substack). The attacker then obtained the bridge's offline conversion-authorizer signing key — described in technical analysis as a nonce-zero key that exists solely to sign backend approvals — and used it to produce valid cryptographic signatures that the TokenConversionManagerV3 contract on Ethereum accepted as legitimate. On-chain analysis published by Ricosworks1 on GitHub identified the affected contract address as 0xab424A430CC09864fA1277A38193111705ADF3A3. The exploit was not a smart-contract code vulnerability; rather, it was an operational security failure in key custody or the signing service. The signed message also failed to bind the recipient address, and the contract enforced no per-conversion transaction limit on the conversionIn function, compounding the damage. Separately, a dormant NuNet minter key inactive since March 2023 was also reactivated during the same window.","heading":"The Attack: SingularityNET Bridge Key Compromise","severity":"critical","sources":[{"credibility":2,"name":"Bridges, Explained: The Hack That Hit World Mobile, and Why They Keep Breaking","type":"news_article","url":"https://bagster.substack.com/p/bridges-explained-the-hack-that-hit"},{"credibility":2,"name":"Key Compromise Behind Fetch.ai-Linked Bridge Attack Drives Losses to $16.77M","type":"news_article","url":"https://mpost.io/key-compromise-behind-fetch-ai-linked-bridge-attack-drives-losses-to-16-77m/"},{"credibility":2,"name":"[DEEP DIVE] SingularityNET Bridge Key Hack Drains $16.77M — Ricosworks1/blockchain-payment-flow-analysis","type":"research","url":"https://github.com/Ricosworks1/blockchain-payment-flow-analysis/releases/tag/deep-dive-singularitynet-bridge-hack-16m-key-compromise-sept-2026"},{"credibility":2,"name":"One Wallet Links $1.55 Million FetchAI Theft to Massive 408.5 Million NTX Mint — CryptoSlate","type":"news_article","url":"https://cryptoslate.com/one-wallet-links-1-55-million-fetchai-theft-to-massive-408-5-million-ntx-mint/"}]},{"content":"Security firm PeckShield reported on September 20–21, 2026 that 53.838 million WMTx were minted on Ethereum without authorization, a figure corroborated by KuCoin and multiple crypto-news outlets. The Bagster analysis, citing what it described as transaction-level data, reported a larger figure of 503 separate mint transactions totaling approximately 500.6 million tokens; however, the sources reviewed for this page could not independently verify that higher figure against on-chain records, and the discrepancy between 53.8 million (PeckShield) and 500.6 million (Bagster) is material and unresolved. Per the Bagster account, of the minted tokens roughly 346.6 million (69%) remained in the attacker's wallets, approximately 41 million were sold into automated liquidity pools or acquired by trading bots, and approximately 94 million reached retail buyers who had no knowledge of the tokens' fraudulent origin. PeckShield valued the attacker's remaining WMTx holdings at approximately $627,350 (33.538 million tokens) as part of a broader attacker cluster holding $16.77 million across multiple tokens. WMTx declined approximately 43% in the immediate aftermath of the unauthorized mint reaching market venues.","heading":"WMTx-Specific Impact: Unauthorized Minting and Token Distribution","severity":"critical","sources":[{"credibility":2,"name":"PeckShield: Hacker Illegally Mints AGIX and WMTx, Causing Over $16.77M in Losses — KuCoin","type":"on_chain","url":"https://www.kucoin.com/news/flash/peckshield-hacker-illegally-mints-agix-and-wmtx-causing-over-16-77m-loss"},{"credibility":2,"name":"SingularityNET Bridge Hack Widens: 260M AGIX, 53.8M WMTx Minted, $16.77M Held by Attacker — CryptoTimes","type":"news_article","url":"https://www.cryptotimes.io/2026/09/21/singularitynet-bridge-hack-widens-260m-agix-53-8m-wmtx-minted-16-77m-held-by-attacker/"},{"credibility":2,"name":"Hackers Exploit SingularityNET Vulnerability, Minting 260M AGIX and 53.83M WMTX — KuCoin","type":"news_article","url":"https://www.kucoin.com/news/flash/hackers-exploit-singularitynet-vulnerability-mint-260m-agix-and-53-83m-wmtx"},{"credibility":2,"name":"Bridges, Explained: The Hack That Hit World Mobile, and Why They Keep Breaking","type":"news_article","url":"https://bagster.substack.com/p/bridges-explained-the-hack-that-hit"},{"credibility":2,"name":"PeckShield: Same Attacker Breached SingularityNET, Illicitly Minting 260M AGIX and 53.838M WMTx — PANews","type":"news_article","url":"https://panews.io/articles/01a0be2e-f8c9-738c-a585-a4d7708cc32b"}]},{"content":"Technical analysis identified several compounding design weaknesses in the SingularityNET bridge that amplified the damage. First, the bridge reportedly operated as a 'committee of one,' accepting authorizations from a single signing account with no multi-signature threshold or secondary approval layer. Second, the contract enforced no per-conversion limit on the conversionIn function, unlike the outbound conversionOut function. Third, the signed message digest did not bind the recipient address, meaning any valid signature could direct funds to an arbitrary wallet. Fourth, the conversion ID format used in the exploit transactions was anomalous — raw bytes rather than the historical UUID pattern — which may have been detectable by an automated monitoring system. These structural gaps meant that once the signing key was compromised, an attacker could mint without bound and direct proceeds wherever they chose.","heading":"Bridge Design Flaws","severity":"high","sources":[{"credibility":2,"name":"[DEEP DIVE] SingularityNET Bridge Key Hack Drains $16.77M — Ricosworks1","type":"research","url":"https://github.com/Ricosworks1/blockchain-payment-flow-analysis/releases/tag/deep-dive-singularitynet-bridge-hack-16m-key-compromise-sept-2026"},{"credibility":2,"name":"Key Compromise Behind Fetch.ai-Linked Bridge Attack Drives Losses to $16.77M","type":"news_article","url":"https://mpost.io/key-compromise-behind-fetch-ai-linked-bridge-attack-drives-losses-to-16-77m/"}]},{"content":"On-chain data indicates the initial FET drain occurred at approximately 19:21–20:21 UTC on September 19, 2026. World Mobile Chain's public acknowledgment of the breach was posted at 05:07 UTC on September 20 — representing a gap of roughly 9 to 16 hours between first exploit activity and public confirmation. According to analysis published by Ricosworks1 and Metaverse Post, as of September 21, 2026 — more than 48 hours after the initial exploit — the compromised conversion-authorizer key had not been rotated and the stolen NuNet minter role had not been revoked, meaning both attack vectors reportedly remained technically viable. This delayed remediation is a concern that applies to SingularityNET's bridge infrastructure rather than to World Mobile Chain specifically; however, WMTx holders remained exposed during this window.","heading":"Detection Gap and Remediation Delays","severity":"high","sources":[{"credibility":2,"name":"[DEEP DIVE] SingularityNET Bridge Key Hack Drains $16.77M — Ricosworks1","type":"research","url":"https://github.com/Ricosworks1/blockchain-payment-flow-analysis/releases/tag/deep-dive-singularitynet-bridge-hack-16m-key-compromise-sept-2026"},{"credibility":2,"name":"Key Compromise Behind Fetch.ai-Linked Bridge Attack Drives Losses to $16.77M","type":"news_article","url":"https://mpost.io/key-compromise-behind-fetch-ai-linked-bridge-attack-drives-losses-to-16-77m/"},{"credibility":2,"name":"One Wallet Links $1.55 Million FetchAI Theft to Massive 408.5 Million NTX Mint — CryptoSlate","type":"news_article","url":"https://cryptoslate.com/one-wallet-links-1-55-million-fetchai-theft-to-massive-408-5-million-ntx-mint/"}]},{"content":"World Mobile Chain confirmed the exploit at 05:07 UTC on September 20, 2026 and at 06:31 UTC announced a pre-exploit snapshot initiative to record legitimate holder balances. The team contacted exchanges to freeze affected deposits and advised holders to refrain from interacting with Ethereum WMTx during the investigation. Founder Micky Watkins stated in a public Space on September 21 that Swiss and British Virgin Islands police had been notified, and expressed confidence that approximately 95% of the minted WMTx could be recovered. On September 25, 2026, World Mobile Chain formally announced the recovery plan: the Ethereum WMTx contract was permanently deprecated and holders were instructed not to trade, transfer, or transact with it. Eligible holders, identified through the pre-exploit snapshot and supplemental chain analysis, are receiving replacement WMTx tokens on a new Base chain contract. SingularityNET subsequently stripped the affected contracts of their minting capability and replaced the compromised signers, stating that the bridges would remain offline pending an independent security review.","heading":"World Mobile Chain Response and Token Migration","severity":"medium","sources":[{"credibility":2,"name":"Bridges, Explained: The Hack That Hit World Mobile, and Why They Keep Breaking","type":"news_article","url":"https://bagster.substack.com/p/bridges-explained-the-hack-that-hit"},{"credibility":2,"name":"SingularityNET Bridge Hack Widens: 260M AGIX, 53.8M WMTx Minted, $16.77M Held by Attacker — CryptoTimes","type":"news_article","url":"https://www.cryptotimes.io/2026/09/21/singularitynet-bridge-hack-widens-260m-agix-53-8m-wmtx-minted-16-77m-held-by-attacker/"}]},{"content":"Following the World Mobile Chain announcement, Kraken and Coinbase both halted WMTx deposits and withdrawals on the Ethereum contract. After the Base chain migration was underway, Kraken reopened deposits, withdrawals, and trading on the new Base chain contract, and Coinbase reopened deposits. The Ethereum-chain WMTx contract is considered permanently worthless by the project; holders of those tokens must participate in the migration process to receive replacement tokens. Holders are cautioned to use only official World Mobile Chain migration channels, as the team warned of fraudulent recovery messages circulating following the exploit.","heading":"Exchange Responses","severity":"medium","sources":[{"credibility":2,"name":"Bridges, Explained: The Hack That Hit World Mobile, and Why They Keep Breaking","type":"news_article","url":"https://bagster.substack.com/p/bridges-explained-the-hack-that-hit"},{"credibility":2,"name":"Latest World Mobile Token News — CoinMarketCap","type":"other","url":"https://coinmarketcap.com/cmc-ai/world-mobile-token/latest-updates/"}]},{"content":"The WMTx incident was part of a larger attack cluster that affected multiple projects sharing the SingularityNET bridge infrastructure. Across the cluster, the attacker drained 8,721,530 FET (approximately $1.55 million) from the TokenConversionManagerV3 contract, minted 408,532,878 NTX (approximately 42% of NuNet's total supply) using a minter key dormant since March 2023, minted 260 million AGIX (approximately $14.42 million at time of exploit), and minted 53.838 million WMTx. PeckShield placed the total attacker-controlled value at approximately $16.77 million as of September 21, 2026. Reporting by CryptoTimes described this as the ninth major bridge exploit in 2026, pushing the year's cumulative bridge-related losses past $345 million. The Bagster analysis noted the operation appeared 'coordinated and largely automated,' and speculated it may have involved AI-assisted tooling, though that characterization has not been independently verified.","heading":"Broader Context: SingularityNET Bridge Attack Cluster","severity":"high","sources":[{"credibility":2,"name":"SingularityNET Bridge Hack Widens: 260M AGIX, 53.8M WMTx Minted, $16.77M Held by Attacker — CryptoTimes","type":"news_article","url":"https://www.cryptotimes.io/2026/09/21/singularitynet-bridge-hack-widens-260m-agix-53-8m-wmtx-minted-16-77m-held-by-attacker/"},{"credibility":2,"name":"Key Compromise Behind Fetch.ai-Linked Bridge Attack Drives Losses to $16.77M","type":"news_article","url":"https://mpost.io/key-compromise-behind-fetch-ai-linked-bridge-attack-drives-losses-to-16-77m/"},{"credibility":2,"name":"Hackers Exploit SingularityNET Bridge Vulnerability, Illegally Mint $16.77M in AGIX and WMTx — KuCoin","type":"news_article","url":"https://www.kucoin.com/news/flash/hackers-exploit-singularitynet-bridge-vulnerability-illegally-mint-16-77m-in-agix-and-wmtx"},{"credibility":2,"name":"Crypto Hacks Drain $20M This Week — CryptoTimes","type":"news_article","url":"https://www.cryptotimes.io/2026/09/21/crypto-hacks-drain-20m-this-week-rseth-safe-nostra-fall/"}]},{"content":"Several material questions remain open as of the date of this investigation. First, the exact total of unauthorized WMTx tokens minted is disputed: PeckShield's widely cited figure is 53.838 million, while the Bagster analysis refers to 503 transactions totaling approximately 500.6 million. No independent on-chain verification of the larger figure has been located. Second, the recovery timeline for retail holders who received counterfeit tokens is not yet finalized, and the criteria for eligibility under the pre-exploit snapshot have not been independently audited. Third, the attacker's identity has not been publicly disclosed, and no arrests or asset freezes had been confirmed as of late September 2026. Fourth, it is unclear whether an independent security review of the SingularityNET bridge infrastructure had been completed or what conditions would be required before any bridge service resumes. Holders of the deprecated Ethereum WMTx contract should treat those tokens as having no value and follow only official World Mobile Chain migration guidance.","heading":"Open Questions and Unresolved Risks","severity":"high","sources":[{"credibility":2,"name":"Bridges, Explained: The Hack That Hit World Mobile, and Why They Keep Breaking","type":"news_article","url":"https://bagster.substack.com/p/bridges-explained-the-hack-that-hit"},{"credibility":2,"name":"[DEEP DIVE] SingularityNET Bridge Key Hack Drains $16.77M — Ricosworks1","type":"research","url":"https://github.com/Ricosworks1/blockchain-payment-flow-analysis/releases/tag/deep-dive-singularitynet-bridge-hack-16m-key-compromise-sept-2026"}]}],"sources_used":[{"credibility":2,"name":"SingularityNET Bridge Hack Widens: 260M AGIX, 53.8M WMTx Minted, $16.77M Held by Attacker — CryptoTimes","type":"news_article","url":"https://www.cryptotimes.io/2026/09/21/singularitynet-bridge-hack-widens-260m-agix-53-8m-wmtx-minted-16-77m-held-by-attacker/"},{"credibility":2,"name":"Bridges, Explained: The Hack That Hit World Mobile, and Why They Keep Breaking — Bagster (Substack)","type":"news_article","url":"https://bagster.substack.com/p/bridges-explained-the-hack-that-hit"},{"credibility":2,"name":"Key Compromise Behind Fetch.ai-Linked Bridge Attack Drives Losses to $16.77M — Metaverse Post","type":"news_article","url":"https://mpost.io/key-compromise-behind-fetch-ai-linked-bridge-attack-drives-losses-to-16-77m/"},{"credibility":2,"name":"[DEEP DIVE] SingularityNET Bridge Key Hack Drains $16.77M — Ricosworks1/blockchain-payment-flow-analysis (GitHub)","type":"research","url":"https://github.com/Ricosworks1/blockchain-payment-flow-analysis/releases/tag/deep-dive-singularitynet-bridge-hack-16m-key-compromise-sept-2026"},{"credibility":2,"name":"PeckShield: Hacker Illegally Mints AGIX and WMTx, Causing Over $16.77M in Losses — KuCoin","type":"on_chain","url":"https://www.kucoin.com/news/flash/peckshield-hacker-illegally-mints-agix-and-wmtx-causing-over-16-77m-loss"},{"credibility":2,"name":"Hackers Exploit SingularityNET Vulnerability, Minting 260M AGIX and 53.83M WMTX — KuCoin","type":"news_article","url":"https://www.kucoin.com/news/flash/hackers-exploit-singularitynet-vulnerability-mint-260m-agix-and-53-83m-wmtx"},{"credibility":2,"name":"Hackers Exploit SingularityNET Bridge Vulnerability, Illegally Mint $16.77M in AGIX and WMTx — KuCoin","type":"news_article","url":"https://www.kucoin.com/news/flash/hackers-exploit-singularitynet-bridge-vulnerability-illegally-mint-16-77m-in-agix-and-wmtx"},{"credibility":2,"name":"PeckShield: Same Attacker Breached SingularityNET, Illicitly Minting 260M AGIX and 53.838M WMTx — PANews","type":"news_article","url":"https://panews.io/articles/01a0be2e-f8c9-738c-a585-a4d7708cc32b"},{"credibility":2,"name":"One Wallet Links $1.55 Million FetchAI Theft to Massive 408.5 Million NTX Mint — CryptoSlate","type":"on_chain","url":"https://cryptoslate.com/one-wallet-links-1-55-million-fetchai-theft-to-massive-408-5-million-ntx-mint/"},{"credibility":2,"name":"One Attacker, Multiple Tokens: Inside the Fetch.ai Breach — Coindoo","type":"news_article","url":"https://coindoo.com/one-attacker-multiple-tokens-inside-the-fetch-ai-breach/"},{"credibility":2,"name":"Crypto Hacks Drain $20M This Week: rsETH Safe, Nostra Fall — CryptoTimes","type":"news_article","url":"https://www.cryptotimes.io/2026/09/21/crypto-hacks-drain-20m-this-week-rseth-safe-nostra-fall/"},{"credibility":1,"name":"WMT Is Now WMTx — World Mobile Token Goes Multichain — World Mobile (official)","type":"official","url":"https://worldmobile.io/blog/post/world-mobile-token-migrates-to-base-ethereum-and-bnb-chain"},{"credibility":2,"name":"Latest World Mobile Token News — CoinMarketCap","type":"other","url":"https://coinmarketcap.com/cmc-ai/world-mobile-token/latest-updates/"},{"credibility":2,"name":"September 19-20, 2026 SingularityNET bridge signing key event — KuCoin Insight","type":"news_article","url":"https://www.kucoin.com/news/insight/FET/6ab77e8c74fd460007c57d70"}],"summary":"World Mobile Token (WMTx) was among several projects victimized by a signing-key compromise of the SingularityNET Ethereum-Cardano bridge in September 2026, which enabled an attacker to mint approximately 53.8 million unauthorized WMTx tokens on Ethereum. World Mobile Chain is a victim of the exploit, not its perpetrator; the project responded by deprecating the old Ethereum contract and migrating eligible holders to a new Base chain deployment. The score reflects the material harm to token holders, the severity of the infrastructure failure, and unresolved questions about the full recovery timeline, while recognizing that the root cause lay in SingularityNET's bridge operations rather than in World Mobile Chain's own systems.","timeline":[{"date":"2025-09-30","event":"World Mobile Token expands from Cardano to Base, Ethereum, and BNB Chain as WMTx, rebranding from WMT.","source":"World Mobile official blog","source_url":"https://worldmobile.io/blog/post/world-mobile-token-migrates-to-base-ethereum-and-bnb-chain"},{"date":"2026-09-19","event":"Attacker reportedly scans SingularityNET systems, gains AWS access, escalates to administrator privileges, and obtains the bridge's offline nonce-zero signing key. Initial FET drain from TokenConversionManagerV3 occurs at approximately 19:21–20:21 UTC; 408.5 million NTX minted from a reactivated dormant minter key.","source":"Bagster (Substack); CryptoSlate on-chain analysis","source_url":"https://bagster.substack.com/p/bridges-explained-the-hack-that-hit"},{"date":"2026-09-20","event":"Attacker uses the compromised SingularityNET bridge signing key to mint 53.838 million unauthorized WMTx and 260 million unauthorized AGIX on Ethereum. World Mobile Chain publicly confirms the exploit at 05:07 UTC and announces a pre-exploit snapshot initiative at 06:31 UTC. PeckShield reports the attacker holds approximately $16.77 million across the attack cluster.","source":"CryptoTimes; KuCoin/PeckShield; World Mobile Chain","source_url":"https://www.cryptotimes.io/2026/09/21/singularitynet-bridge-hack-widens-260m-agix-53-8m-wmtx-minted-16-77m-held-by-attacker/"},{"date":"2026-09-21","event":"World Mobile Chain founder Micky Watkins states in a public Space that Swiss and British Virgin Islands police have been notified and expresses confidence that approximately 95% of minted WMTx can be recovered. Technical analysis reports that the compromised signing key and stolen NuNet minter role remained unrevoked more than 48 hours post-exploit.","source":"Bagster (Substack); Metaverse Post","source_url":"https://bagster.substack.com/p/bridges-explained-the-hack-that-hit"},{"date":"2026-09-24","event":"Kraken and Coinbase reopen WMTx deposits on the Base chain contract following exchange coordination.","source":"CoinMarketCap latest updates; Bagster","source_url":"https://coinmarketcap.com/cmc-ai/world-mobile-token/latest-updates/"},{"date":"2026-09-25","event":"World Mobile Chain formally announces recovery plan: Ethereum WMTx contract is permanently deprecated; eligible holders will receive replacement tokens on Base chain via pre-exploit snapshot. Holders instructed to cease all Ethereum WMTx transactions.","source":"Bagster (Substack); CoinMarketCap","source_url":"https://bagster.substack.com/p/bridges-explained-the-hack-that-hit"}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision cc0f1435-f077-41d3-ba54-5df4caa2b906
  2. #2reviewby reviewerreviewer
    2026-10-27 11:22:24Z
    Score: 38 → 38 (no score change)
    The core incident (bridge key compromise, 53.838M WMTx minted, $16.77M attacker cluster, no per-conversion limit and unbound recipient) is corroborated. Overprecise or unsupported details include the exact $627,350 figure and the 'more than 48 hours' unrotated-key claim. The response and migration narrative (Sept 25 plan, exchange reopenings, police notification) could not be verified because the main source is paywalled, and the timeline's CoinMarketCap source predates the event. The page already flags the 500.6M versus 53.8M discrepancy.
    anchoranchored
    chain
    ●mainnet-betaslot 462,051,986
    sig
    5G9yuUr8y9eB…1b9nkdXVexplorer ↗
    hash
    5UrnCn2abRM2…yJoZ35vnsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1481 B) ▸
    {"actor":"reviewer","artifact_identity":"f5aab6c08219f050ae800c4cbe5ecdf8","blocked_count":3,"decided_at":"2026-10-27T11:22:24.508Z","decision":"review","disputed_pct":0.3333,"findings_hash":"9uDQnL835UBDDcrS2TJEwFkYgSq5Ywcp4VQpLfCtzB54","investigation_id":"68c31745-7e93-46e5-90b3-8250d884cf08","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":38,"omissions":{"material":0,"total":1},"page_content_hash":"586343857d2740bbd9b1fe3d91a43a9b4c951c1108a1862a2e9551e2ff7868af","page_slug":"world-mobile-token-wmtx-singularitynet-bridge-key-compromise","prev_score":38,"reason":"The core incident (bridge key compromise, 53.838M WMTx minted, $16.77M attacker cluster, no per-conversion limit and unbound recipient) is corroborated. Overprecise or unsupported details include the exact $627,350 figure and the 'more than 48 hours' unrotated-key claim. The response and migration narrative (Sept 25 plan, exchange reopenings, police notification) could not be verified because the main source is paywalled, and the timeline's CoinMarketCap source predates the event. The page already flags the 500.6M versus 53.8M discrepancy.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":2,"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 37a7be52-8332-4cdf-95f4-f919272c4571
  3. #3review reviseby judgejudge
    2026-10-27 11:22:25Z
    Score: 38 → 26 (-12)
    Of 12 claim findings, 3 were excluded because the sources blocked the reviewer, leaving 9; 2 were disputed (claim_findings[5] and [6], the same 'more than 48 hours' error) and 1 could not be found in the sources (claim_findings[4], the 'committee of one' claim), giving about 33%, which falls in the significant-issues band. The core incident (53.838M WMTx minted, $16.77M attacker cluster, no per-conversion limit, unbound recipient) was confirmed, and the disputed items are one repeated arithmetic error, so the penalty sits at the lenient end of the band. The response and migration narrative rests on a paywalled post and an out-of-date CoinMarketCap archive (coverage gap, high priority), and the reviewer's confidence is moderate (0.5). The page should be corrected, not denied.
    anchoranchored
    chain
    ●mainnet-betaslot 462,051,991
    sig
    2Avu6BAanHe9…C1djjLPrexplorer ↗
    hash
    8BfL1kCQb27F…HBveKEYgsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1626 B) ▸
    {"actor":"judge","artifact_identity":"f5aab6c08219f050ae800c4cbe5ecdf8","band_override":null,"blocked_count":3,"decided_at":"2026-10-27T11:22:24.508Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"68c31745-7e93-46e5-90b3-8250d884cf08","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"world-mobile-token-wmtx-singularitynet-bridge-key-compromise","prev_score":38,"reason":"Of 12 claim findings, 3 were excluded because the sources blocked the reviewer, leaving 9; 2 were disputed (claim_findings[5] and [6], the same 'more than 48 hours' error) and 1 could not be found in the sources (claim_findings[4], the 'committee of one' claim), giving about 33%, which falls in the significant-issues band. The core incident (53.838M WMTx minted, $16.77M attacker cluster, no per-conversion limit, unbound recipient) was confirmed, and the disputed items are one repeated arithmetic error, so the penalty sits at the lenient end of the band. The response and migration narrative rests on a paywalled post and an out-of-date CoinMarketCap archive (coverage gap, high priority), and the reviewer's confidence is moderate (0.5). The page should be corrected, not denied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-12,"score_limit":{"applied":-12,"limited":true,"proposed":-15,"rule":"limited_no_second_opinion","second":null},"scored_claims":9,"sequence_num":3,"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 eae9216a-69f5-4eea-910c-45d938f61f7e
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>.