SingularityNET contract exploit forces Fetch.ai to pause AGIX-FET conversions

A SingularityNET contract exploit surfaced on September 19, prompting Fetch.ai to issue a rapid public update on the state of its systems and the wider fallout across the two connected blockchain ecosystems. The company moved quickly to separate its own token operations from the incident, confirming that FET contracts remain untouched while the breach itself struck a specific cross-chain route tied to SingularityNET’s infrastructure.

Key takeaways

• An exploit hit SingularityNET contracts on September 19, mainly through the SingularityNET Bridge linking Ethereum and Cardano.
• Fetch.ai contracts are not affected, and FET token operations continue normally.
• AGIX to FET conversions are paused until further notice as a precaution.
• Fetch.ai’s Ethereum-side bridge contract has also been paused, though no vulnerability was found in it.
• The exploit has been contained, an investigation is ongoing, and Fetch.ai is coordinating with the SingularityNET team.

SingularityNET Contract Exploit Overview

The exploit centered on SingularityNET’s own contracts rather than Fetch.ai’s infrastructure, with the attack specifically routed through the bridge connecting Ethereum and Cardano. Fetch.ai’s public statement, posted shortly after reports of the breach emerged, laid out where the damage occurred and drew a clear line around what remained secure.

Details of the Unauthorized Mint

According to Fetch.ai, the unauthorized mint was carried out through that same bridge route, meaning whoever exploited the system used the cross-chain pathway itself to generate tokens without authorization. The company did not offer a deeper technical breakdown of how the mint was executed, but it was explicit that this was the mechanism attackers relied on.

Targeted Blockchain Bridges

The SingularityNET Bridge, which handles the transfer of value between Ethereum and Cardano, was identified as the primary point of failure. Bridges like this one are frequent targets in the crypto space because they often hold or control token supply across two separate chains, and a flaw in that logic can be leveraged to mint assets that were never meant to exist.

Operational Status of Fetch.ai and Related Services

Fetch.ai says its own contracts are secure and that no vulnerability has been found on its side, even as it takes precautionary steps around services connected to the broader incident. That distinction between “affected” and “precautionary” is central to understanding how the company is handling the fallout.

FET Token Operations Remain Unaffected

Fetch.ai stated plainly that its contracts are not affected and that no contract is under threat at this time. As a direct result, Fetch.ai’s FET operations continue normally, with the token functioning as usual despite the turbulence surrounding SingularityNET’s bridge.

Precautionary Pauses on Bridge Contracts and Conversions

Even so, Fetch.ai chose to pause two specific services tied to the incident. AGIX to FET conversions are paused until further notice, cutting off that particular swap path while the situation is assessed. Separately, the company’s own bridge contract on the Ethereum side has also been paused as a precaution, with Fetch.ai explicitly noting there is no indication of any vulnerability in that contract. Both moves reflect a standard approach to blockchain bridge security: freeze first, confirm safety, then resume.

This is where the incident carries broader weight beyond the immediate technical details. Cross-chain bridges have repeatedly proven to be one of the more fragile points in crypto infrastructure, and a pause of adjacent, technically unaffected contracts shows how quickly caution spreads through connected systems even when a direct link to the exploit hasn’t been established.

Investigation and Collaboration Efforts

Fetch.ai says the exploit has already been contained and that an investigation into the root cause is underway. The company is working directly with the SingularityNET team, and it has committed to sharing further updates as the probe develops.

Both paused services, the AGIX to FET conversion tool and Fetch.ai’s Ethereum-side bridge contract, are expected to be restored once conditions are deemed safe, according to the company’s statement. No firm timeline was given for when that restoration will happen, leaving the pace of recovery tied to how the joint investigation with SingularityNET unfolds.

FAQ

Are Fetch.ai contracts currently affected by the SingularityNET exploit?

Fetch.ai contracts are not affected and FET operations continue normally.

What was the vector used in the SingularityNET exploit?

The unauthorized mint was carried out through the SingularityNET Bridge between Ethereum and Cardano chains.

What precautions have been taken by Fetch.ai following the exploit?

Fetch.ai’s bridge contract on the Ethereum side and AGIX to FET conversions have been paused until further notice.

What is the status of the investigation and future service restoration?

The exploit has been contained, the investigation is ongoing, and paused services will be restored when safe.

{"@context":"","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Are Fetch.ai contracts currently affected by the SingularityNET exploit?","acceptedAnswer":{"@type":"Answer","text":"Fetch.ai contracts are not affected and FET operations continue normally."}},{"@type":"Question","name":"What was the vector used in the SingularityNET exploit?","acceptedAnswer":{"@type":"Answer","text":"The unauthorized mint was carried out through the SingularityNET Bridge between Ethereum and Cardano chains."}},{"@type":"Question","name":"What precautions have been taken by Fetch.ai following the exploit?","acceptedAnswer":{"@type":"Answer","text":"Fetch.ai's bridge contract on the Ethereum side and AGIX to FET conversions have been paused until further notice."}},{"@type":"Question","name":"What is the status of the investigation and future service restoration?","acceptedAnswer":{"@type":"Answer","text":"The exploit has been contained, the investigation is ongoing, and paused services will be restored when safe."}}]}

Article produced with the assistance of artificial intelligence and reviewed by the editorial team.