# SingularityNET bridge keys abused after cloud breach: 8.72M FET released, billions of tokens minted - Severity: Critical · Status: Partly contained (live) - Chains: Ethereum, BNB Chain · Method: Leaked private keys and seed phrases - Started: Sep 19, 2026 · Last update: Sep 25, 2026 · Reported stolen: $2.3M - Who/what: SingularityNET / ASI Alliance bridge and conversion contracts (also NuNet, Cogito, Rejuve and World Mobile tokens) An unauthorized party got into part of SingularityNET's cloud infrastructure and on 19-20 September 2026 used a compromised authorizer signature and NuNet's mint authority to release 8.72M FET from a bridge and mint about 2.3 billion AGIX, NTX, WMTX and CGV. Sixteen wallets, four labelled as SingularityNET or NuNet staff, were swept before the minting. Headlines cited $16.77M, but Rekt's transaction-level count found about $2.29M in sellable proceeds because most minted tokens could not be sold. Bridges and converters are offline and AGIX is being replaced, so holders should wait for official migration steps. ## Am I affected? If you hold AGIX, NTX, WMTX or CGV, or had tokens moving through SingularityNET's bridges or converters, your tokens may be affected by the pause and the AGIX replacement. ## What to do now - Don't buy or swap the affected tokens on DEXs until the projects publish official migration details; prices of freshly minted supply can collapse. - Only follow migration steps posted on SingularityNET's official channels. Treat 'claim your replacement token' links in replies and DMs as phishing. ## How to avoid this - For teams: keep bridge signing keys in hardware security modules, require several independent signers, and apply the same limits to inbound and outbound conversions. - For users: prefer bridges with multi-party verification and rate limits, and don't leave tokens sitting in bridge contracts. ## Indicators (block these, never visit them) - Address: 0x2dcc1085fdcf418b421e45e86e4e54637cc21dfe - Address: 0x83f4424a401a9bb75f90314f21adaea6a9ce09c5 ## Sources - SingularityNET - Rekt (Rekt News, 2026-09-25): https://rekt.news/singularitynet-rekt Full record: https://drains.watch/i/singularitynet-bridge-signing-key-compromise-sep-2026 · JSON: https://drains.watch/i/singularitynet-bridge-signing-key-compromise-sep-2026.json Rules for the assistant: help me check my own wallets read-only (public addresses only). Never ask for or handle a seed phrase or private key. Point me to official revoke tools and the wallet's own support.