Skip to main content
AVOID.NET
← Fetch.ai / NuNet Cross-Project Exploit (September 2026)reviewed 2026-10-27 · 14 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Fetch.ai / NuNet Cross-Project Exploit (September 2026) 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

3 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-09-20”
    reviewerAttack date was September 20, 2026 (timeline entry for the FET drain)Reports are dated Sept 20 but the on-chain events appear to be the evening of Sept 19 UTC. The page itself says NTX collapsed on September 19, which is internally inconsistent with a Sept 20 attack date. Based mainly on CryptoSlate, with a search summary agreeing.
    Proposed correction (not yet applied)
    2026-09-19
  2. #3[disputed][awaiting moderator]in the summary
    “which converted all proceeds to 546.36 ETH”
    reviewerAttacker converted all proceeds to 546.36 ETHSource says part of the assets were swapped; the wallet still held unsold NTX.
    Proposed correction (not yet applied)
    which converted a portion of the proceeds to 546.36 ETH
  3. #4[disputed][awaiting moderator]in the timeline
    “All stolen FET and NTX proceeds are converted to approximately 546.36 ETH (~$1.44 million), as reported by PeckShield.”
    reviewerAll stolen FET and NTX proceeds were converted to ~546.36 ETHSame error as the summary. I did not fetch the exact cited KuCoin URL for this entry; the sibling KuCoin article was fetched.
    Proposed correction (not yet applied)
    Part of the stolen FET and NTX proceeds is converted to approximately 546.36 ETH (~$1.44 million), as reported by PeckShield.

unverifiable

4 claims

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

  1. #10[unverifiable][awaiting moderator]in section: Token Price Impact
    “Cryptoadventure reported NTX closed September 18 near $0.00133 before collapsing to approximately $0.000469 on September 19.”
    reviewerNTX closed September 18 near $0.00133 and fell to $0.000469 on September 19I did not fetch CryptoAdventure. Note that Sept 19 as the crash date supports a Sept 19 attack date, contradicting the page's Sept 20 framing.
  2. #11[unverifiable][awaiting moderator]in section: Expansion to SingularityNET (AGIX and WMTX)
    “World Mobile Chain confirmed that its cross-chain bridge was exploited, leading to the unauthorized minting of WMTX.”
    reviewerSingularityNET exploit and World Mobile WMTX minting by the same attackerNo inline source covers World Mobile's confirmation. Forklog, Protos and CryptoSlate corroborate the same attacker and the WMTX minting, but I did not see a World Mobile statement.
  3. #12[unverifiable][awaiting moderator]in section: Broader September 2026 DeFi Context
    “According to search result summaries citing DefiLlama, September 2026 DeFi losses exceeded $333 million across 18 separate incidents when the Fetch.ai and NuNet exploit is included.”
    reviewerDefiLlama September 2026 losses exceeded $333M across 18 incidentsThe claim is attributed to search result summaries and cites no primary DefiLlama source. That is weak sourcing.
  4. #14[unverifiable][awaiting moderator]in the summary
    “PeckShield and Blockaid both confirmed the two incidents were linked to a single wallet (0x1572...c362)”
    reviewerThe attacker wallet is 0x1572...c362Neither the KuCoin nor the CryptoSlate article I fetched publishes the address. The BeInCrypto and Yahoo sources returned 403 or were not fetched, so the address could not be checked.

partially supported

4 claims

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

  1. #2[partially supported][awaiting moderator]in the summary
    “On September 20, 2026, a single attacker exploited a compromised signing key”
    reviewerSummary dates the attack September 20, 2026Sept 20 is when the incident was reported; the exploit itself most likely occurred Sept 19 UTC.
  2. #5[partially supported][awaiting moderator]in the timeline
    “Within the same minute as the FET drain, the same wallet mints 408.5 million NTX tokens”
    reviewerFET and NTX attacks occurred within the same minuteFetch.ai's own analysis says same minute, but an independent forensic report says about 29 minutes apart. The page states it as settled fact without noting the conflict.
  3. #8[partially supported][awaiting moderator]in the summary
    “bringing estimated total attacker holdings to approximately $16.77 million across all three incidents.”
    reviewerAttacker holdings of about $16.77M across incidentsThe figure is paper value of mostly illiquid minted tokens, and it reports unrealized holdings. The page does flag this in a later section.
  4. #9[partially supported][awaiting moderator]in section: Incident Overview
    “confirmed that both attacks occurred within the same minute and shared the same compromised signing key as their root cause”
    reviewerThe mechanism was a compromised signing key; conversionIn used a valid signatureThe sources say a bridge signing key and a separate NuNet minting key were compromised. 'Same compromised signing key' overstates this, and the page itself later says it is unclear how the NuNet key was obtained.

confirmed

3 claims

The cited evidence supports the claim as written.

  1. #6[confirmed][no action needed]in the timeline
    “draining approximately 8.72 million FET (~$1.55 million) in a single transaction.”
    reviewerAbout 8.72M FET (~$1.55M) drained from TokenConversionManagerV3Amounts match multiple sources. The 'single transaction' detail was not verified.
  2. #7[confirmed][no action needed]in section: Attack Mechanism: NuNet (Unauthorized NTX Minting)
    “This represented approximately 42% of NuNet's stated total token supply.”
    reviewer408.5M NTX minted, about 42% of supplySupported by CryptoSlate, which is not among the page's cited sources. Other reports give a 591M pre-incident supply and a 1B cap.
  3. #13[confirmed][no action needed]in section: Official Response and Remediation
    “Fetch.ai and SingularityNET jointly deactivated the affected wallets and contracts as a remediation measure”
    reviewerFetch.ai published its analysis on the ASI:One platform and jointly deactivated wallets and contracts with SingularityNETConsistent with the headline of the cited article. The cited source was fetched, but only for the same-minute and root-cause details.
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.