After stealing $1.56 million in FET, the same hacker breached SingularityNET and illegally minted 260 million AGIX tokens. The incident has affected multiple AI projects, cross-chain bridges, and token contracts, with broad implications for user asset security. Further details await official disclosure.
The FET/AGIX chain of attacks has become one of the most closely watched security incidents in the crypto space today. Based on information disclosed so far, the same attacker first stole FET assets, causing losses of $1.56 million, and then breached SingularityNET to illegally mint 260 million AGIX tokens. As both attacks targeted projects within the ASI Alliance ecosystem and were carried out by the same attacker, the incident has been classified as a coordinated chain of attacks. The event has also affected multiple AI projects, with cross-chain bridges and token contracts impacted to varying degrees, posing significant challenges to user asset security.
The core entities involved in this incident are the ASI Alliance and SingularityNET. According to disclosed information, the ASI Alliance encompasses multiple AI projects, with FET and AGIX serving as its associated tokens. SingularityNET, as the entity at the center of the illegal AGIX minting, became the attacker's primary target. Based on available information, the attacker did not select targets at random but acted systematically against different assets within the ASI Alliance ecosystem. The sequence — first stealing FET, then breaching SingularityNET to mint AGIX — was tightly connected in timing and highly correlated in targeting, forming a typical chain-attack pattern.
In terms of attack sequence, the FET theft was the first to be disclosed. The attacker stole $1.56 million from FET-related assets. Subsequently, the same attacker shifted focus to SingularityNET and completed the illegal minting of 260 million AGIX tokens. Although the targets differed, both attacks were directed at AI projects within the ASI Alliance ecosystem. The incident has been deemed a "chain attack" precisely because the attacker was identical, the targets were interrelated, and the attacks occurred in succession.
In terms of scope, the incident involves not only losses or inflation of a single token but also affects cross-chain bridges and token contracts. The fact that both cross-chain bridges and token contracts were impacted means the attacker reached beyond a single infrastructure component. For users, since related assets may be held in different ways, the impact extends beyond SingularityNET alone to multiple AI projects within the ASI Alliance ecosystem. As a result, the scope of impact on user asset security is assessed to be relatively broad. To date, the specific damage to each cross-chain bridge and token contract has not been disclosed in further technical detail by the relevant authorities.
The illegal minting of 260 million AGIX tokens is one of the most prominent aspects of this incident. Illegal minting means the token supply was altered without going through proper procedures, directly affecting AGIX's total supply and holder rights. Under normal circumstances, token minting should be strictly controlled, and any unexpected supply expansion could dilute the holdings of existing token holders. Based on disclosed information, an exploitable anomaly appears to exist in SingularityNET's related contracts. However, questions such as exactly how the attacker executed the operation, whether contract permissions were breached, and whether the illegally minted tokens have entered circulation remain pending official investigation and cannot yet be confirmed as established facts.
From the perspective of user asset security, the FET theft and the AGIX illegal minting represent two distinct types of risk. The $1.56 million loss from the FET theft constitutes a direct loss of existing assets, with affected users potentially facing the risk of asset transfer. The illegal minting of AGIX, by contrast, represents token supply inflation risk that could dilute the holdings of existing token holders. The combination of these two risk types has created greater uncertainty for holders of assets within the ASI Alliance ecosystem. As information is still being disclosed gradually, users are currently unable to fully determine whether their own positions have been directly affected, which further heightens market attention on the incident's subsequent developments.
This chain of attacks has also exposed potential weaknesses in security protection for alliance-based projects. The ASI Alliance aggregates multiple AI projects, and this ecosystem structure may enable an attacker to continue targeting other related projects within the ecosystem after breaching one target. However, whether the projects share common components, cross-chain interoperability mechanisms, or a unified security boundary has not yet been officially confirmed. Therefore, the actual degree of interconnection between the projects remains undisclosed information, and the surface-level pattern of the chain attacks alone cannot be used to determine the specific technical causes.
At present, this incident has been recognized as a major security event of the day and has drawn significant attention. The issues that the ASI Alliance and related project teams will need to address include the progress of the investigation, the status of affected contracts and cross-chain bridges, the flow of the illegally minted AGIX tokens, and whether any arrangements will be made for affected users. All of these matters are currently awaiting official responses. The pace of handling and the content of disclosures will directly influence market assessments of the ASI Alliance's security capabilities.
From an industry perspective, the fact that the same attacker successively targeted two projects highlights the importance of security coordination in cross-project and cross-chain scenarios. The chain attack suffered by the ASI Alliance provides a security case worthy of continued tracking for AI projects operating under alliance-based structures. The investigation results may also offer reference points for other projects adopting similar ecosystem architectures.
Future attention should focus on three main areas: first, the official findings regarding the FET theft and the illegal AGIX minting; second, whether the security status of the affected cross-chain bridges and token contracts is confirmed and remediated; and third, whether asset protection and follow-up arrangements for affected users are clearly communicated. Given that original information remains limited, these areas will depend on further disclosures from the ASI Alliance, SingularityNET, and related platforms. Overall, this incident warrants continued tracking and in-depth reporting, and its subsequent developments remain worthy of close attention.
