SingularityNET Bridge Exploit: AGIX Conversions Paused, What to Check

Quick answer: The SingularityNET bridge incident has materially expanded. Reporting based on project updates says unauthorized AGIX and WMTx were minted through compromised bridge-related infrastructure. AGIX-to-FET conversions were paused, and Fetch.ai paused its Ethereum-side bridge as a precaution while teams worked to contain the incident.

What changed

Earlier updates focused on converter-related reports and the Fetch.ai/NuNet security situation. The newer development points specifically to SingularityNET contracts, primarily the bridge between Ethereum and Cardano, and unauthorized minting. That makes this a direct bridge-safety issue for users interacting with AGIX/FET conversion routes or affected bridged assets.

What bridge users should do now

1. Do not initiate an AGIX-to-FET conversion while the official route is paused.
2. Do not use unofficial “mirror” bridges or links posted in replies and DMs.
3. If you recently bridged, record the source transaction hash, destination chain, token contract and receiving address.
4. Verify token contract addresses against official project channels before swapping an asset received during the incident window.
5. Revoke suspicious approvals only through a trusted wallet/security interface; never disclose your seed phrase.

Why unauthorized minting matters

A bridge generally depends on rules that keep representations of an asset synchronized across chains. Unauthorized minting can create tokens that were not backed or authorized as intended, disrupting liquidity and creating uncertainty around contracts, pools and conversion routes.

What not to do

Do not buy an affected token simply because it appears discounted. Do not assume every token with the same ticker is legitimate. Do not connect to a “recovery” dApp advertised by strangers. Security incidents create ideal conditions for secondary phishing attacks.

Fetch.ai bridge status

Reporting says Fetch.ai paused its Ethereum-side bridge as a precaution and stated there was no indication that bridge itself contained the same vulnerability. Users should still wait for explicit official restoration before using paused routes.

Source evidence

A September 21 report compiling project updates describes the bridge attack, unauthorized minting, paused AGIX-to-FET conversions and precautionary Fetch.ai bridge pause: Crypto Times incident update. Treat figures as preliminary until the projects publish final post-mortems.

FAQ

Was the Fetch.ai Ethereum bridge itself exploited?

The cited update says it was paused as a precaution and that there was no indication of a vulnerability in it at that time.

Can I safely use another bridge for AGIX?

Do not improvise around an official pause. Wait for verified project guidance that identifies supported contracts and routes.

What if I already approved a suspicious contract?

Use a reputable approval-management tool or wallet security interface to review permissions, and move assets to a fresh wallet if credible official guidance indicates key exposure.

Informational security guidance only, not investment advice. Incident facts may evolve; verify current project statements before taking on-chain action.