Fact-check findings
What an automated fact-checker found when it re-read World Mobile Token (WMTx) — SingularityNET Bridge Key Compromise against the sources the page cites. Only the most recent review is shown.
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 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #6[disputed][awaiting moderator]in section: Detection Gap and Remediation Delays
“as of September 21, 2026 — more than 48 hours after the initial exploit — the compromised conversion-authorizer key had not been rotated”
reviewerCompromised key unrotated more than 48 hours after exploitThe exploit began Sept 19 ~19:21 UTC, so Sept 21 is at most ~48 hours (less than 48 on the morning of Sept 21). The 'more than 48 hours' framing is arithmetically unsupported for Sept 21 and absent from the source. The correction is arithmetic only; the exact tracking-update time is unknown, so the edit_kind may be better as a softer wording.Proposed correction (not yet applied)as of September 21, 2026 — roughly 24 to 36 hours after the initial exploit — the compromised conversion-authorizer key had not been rotated - #7[disputed][awaiting moderator]in the timeline
“Technical analysis reports that the compromised signing key and stolen NuNet minter role remained unrevoked more than 48 hours post-exploit.”
reviewerSame 48 hours claim in timelineSame error as sections[4].Proposed correction (not yet applied)Technical analysis reports that the compromised signing key and stolen NuNet minter role remained unrevoked as of the latest tracking update.
unverifiable
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #3[unverifiable][awaiting moderator]in section: WMTx-Specific Impact: Unauthorized Minting and Token Distribution
“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”
reviewerBagster reported 503 mint transactions totaling ~500.6M tokens, 346.6M (69%) in attacker wallets, ~41M to pools/bots, ~94M to retailPage already flags the discrepancy as unverified. Many page claims (timings, Watkins statements, exchange reopenings, Sept 25 plan) cite only this paywalled Bagster post and could not be checked. - #5[unverifiable][awaiting moderator]in section: Bridge Design Flaws
“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.”
reviewerBridge operated as a 'committee of one'; AWS compromiseDid not fetch the Ricosworks1 GitHub release; page hedges with 'reportedly'. AWS intrusion narrative rests on paywalled Bagster only and is unverified. - #9[unverifiable][awaiting moderator]in the timeline
“Kraken and Coinbase reopen WMTx deposits on the Base chain contract following exchange coordination.”
reviewerKraken and Coinbase reopened WMTx on Base; Sept 25 recovery plan; Watkins 95% recovery; Swiss/BVI policeThe CoinMarketCap archive cited is dated 2025-11-22, which predates the incident; it cannot support a Sept 2026 event. The rest of the response narrative could not be verified; search found no deprecated-contract or Base migration reporting. - #10[unverifiable][awaiting moderator]in section: Exchange Responses
“Reporting by CryptoTimes described this as the ninth major bridge exploit in 2026, pushing the year's cumulative bridge-related losses past $345 million.”
reviewerCluster totals and 'ninth major bridge exploit in 2026', $345M cumulativeSource blocked; not scored.
partially supported
3 claimsThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in section: WMTx-Specific Impact: Unauthorized Minting and Token Distribution
“PeckShield valued the attacker's remaining WMTx holdings at approximately $627,350 (33.538 million tokens)”
reviewerPeckShield valued attacker's remaining WMTx at approx $627,350False precision; the fetched source says about $627,000. Separately, Bitquery estimated realized attacker holdings far lower (~$2.25M total) per search results, so the $16.77M figure is one estimate among several. - #8[partially supported][awaiting moderator]in the timeline
“Attacker uses the compromised SingularityNET bridge signing key to mint 53.838 million unauthorized WMTx and 260 million unauthorized AGIX on Ethereum.”
reviewerExploit date Sept 19; WMTx minting and AGIX minting dated Sept 20 on timelineCryptoTimes was 403 blocked. Mint timing is imprecise; the summary says the attack was Sept 19-20. - #11[partially supported][awaiting moderator]in section: Exchange Responses
“PeckShield placed the total attacker-controlled value at approximately $16.77 million as of September 21, 2026.”
reviewerAttacker holds $16.77M cluster totalFigure confirmed; Bitquery gives a much lower realized estimate (~$2.25M) which the page does not mention.
confirmed
3 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: WMTx-Specific Impact: Unauthorized Minting and Token Distribution
“Security firm PeckShield reported on September 20–21, 2026 that 53.838 million WMTx were minted on Ethereum without authorization”
reviewerPeckShield reported 53.838 million WMTx minted on Ethereum without authorizationKuCoin flash and search results (Forklog, PANews headlines) corroborate the figure. - #4[confirmed][no action needed]in section: The Attack: SingularityNET Bridge Key Compromise
“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.”
reviewerThe conversion authorizer was not rotated; no per-conversion limit; recipient not bound in digestMetaverse Post confirms. - #12[confirmed][no action needed]in the summary
“World Mobile Chain is a victim of the exploit, not its perpetrator”
reviewerWorld Mobile Chain is a victim; Cardano network not affectedConsistent with reporting.