Skip to main content
AVOID.NET
← SingularityNET (AGIX/WMTx Bridge Key Compromise)reviewed 2026-11-17 · 8 claims checked

Fact-check findings

What an automated fact-checker found when it re-read SingularityNET (AGIX/WMTx Bridge Key Compromise) 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.

partially supported 2confirmed 60 corrections pending · 0 applied

partially supported

2 claims

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

  1. #6[partially supported][awaiting moderator]in the timeline
    “2026-09”
    reviewerAttack began 2026-09-19 (timeline date given only as month)Correct but imprecise; the sources support a day-level date. Optional precision fix.
  2. #7[partially supported][awaiting moderator]in the timeline
    “2026-09”
    reviewerPeckShield reported continued attack on Sept 20 (timeline date given only as month)Correct but imprecise; optional precision fix.

confirmed

6 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Incident overview and FET drain
    “According to CryptoSlate (published 21 September 2026, updated 30 September 2026), 8,721,530 FET (about $1.55 million at the time) was drained from the Ethereum-side conversion contract on September 19.”
    reviewer8,721,530 FET (about $1.55 million) drained from the Ethereum-side conversion contract on Sept 19; 1M cap not enforced on conversionIn; Athena report not independently verifiedMatches the CryptoSlate article.
  2. #2[confirmed][no action needed]in section: NTX, AGIX and WMTx minting
    “CryptoSlate reports that a NuNet minter key created 408,532,878 NTX (about 42% of NuNet's documented supply), 29 minutes after the FET withdrawal”
    reviewerNuNet minter key created 408,532,878 NTX (~42% of supply) 29 minutes after the FET withdrawal; tx hash linkedMatches.
  3. #3[confirmed][no action needed]in section: NTX, AGIX and WMTx minting
    “ForkLog attributes to PeckShield the minting of 260 million AGIX and 53.838 million WMTx on Ethereum via the SingularityNET bridge”
    reviewerPeckShield: 260M AGIX and 53.838M WMTx minted; attacker holdings ~$16.77M; Bitquery: ~896M AGIX, 500.5M WMTx, 492.4M CGV, 408.5M NTX, ~2.3B units, ~$2.25M realizedFigures match ForkLog; page notes the discrepancy between analysts.
  4. #4[confirmed][no action needed]in section: Statements by affected parties and exchanges
    “CryptoSlate includes no direct SingularityNET statement, and ForkLog quotes none”
    reviewerFetch.ai, World Mobile and Bitvavo responses; no primary SingularityNET statementMatches both sources.
  5. #5[confirmed][no action needed]in section: Key management concerns and open questions
    “Bitquery observed ETH withdrawn from 16 wallets before issuance began, four of them allegedly linked to SingularityNET or NuNet employees”
    reviewer16 wallets had ETH withdrawn before issuance, four linked to SingularityNET or NuNet employees; credentials not rotated ~5 hours after the attackMatches.
  6. #8[confirmed][no action needed]in the timeline
    “CryptoSlate article updated.”
    reviewerCryptoSlate published Sept 21 and updated Sept 30, 2026Matches.
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.