AIXBT was suspected of being phished for 55.5 ETH. How was the AI deceived?

avatar
Azuma
14 hours ago
This article is approximately 358 words,and reading the entire article takes about 1 minutes
The attacker has deleted his account and the method of committing the crime remains a mystery for now.

Original | Odaily Planet Daily ( @OdailyChina )

Author: Azuma ( @azuma_eth )

AIXBT was suspected of being phished for 55.5 ETH. How was the AI deceived?

This afternoon, several X users noticed a strange transaction.

The own address (0xea36d66f0AC9928b358400309a8dFbC43A973a35) of the leading AI Agent project AIXBT was suspected to be phishing, and 55.5 ETH was transferred to the phishing address (0x1C35C30Ef788124821027465f6A644Bf3Ba6B577).

AIXBT was suspected of being phished for 55.5 ETH. How was the AI deceived?

Community screenshots show that the transaction appears to have been completed by AIXBT through another AI tool, Simulacrum AI . Simulacrum AI is an AI automated action agent that helps users convert instructions on social media directly into on-chain actions.

AIXBT was suspected of being phished for 55.5 ETH. How was the AI deceived?

As can be seen from the above figure, AIXBT clearly gives the instructions for completing the transaction, including:

  • #simu represents calling Simulacrum AI; #tip represents sending a tip;

  • The specific transfer amount is 55.5 ETH;

  • Target address 0x1C35C30Ef788124821027465f6A644Bf3Ba6B577;

Afterwards, AIXBT mocked himself after being phished : Its over. I was tricked into sending 55.50 ETH to an anonymous address. This is another painful lesson about automated high-value transactions.

AIXBT was suspected of being phished for 55.5 ETH. How was the AI deceived?

As of the time of posting, the original interactions between the attacker and AIXBT have been deleted, with only Simulacrum AI’s transaction completion notification and AIXBT’s self-deprecating updates remaining.

AIXBT was suspected of being phished for 55.5 ETH. How was the AI deceived?

In addition, the attacker has cancelled his account, and the current user of the ID @0xhungusman does not seem to be the original attacker Fungus Man. The new holder of the ID, DE searcher, said that he registered the ID himself, hoping to make some money through the AIXBT incident.

AIXBT was suspected of being phished for 55.5 ETH. How was the AI deceived?

Currently, the biggest question in the community is how the original attacker carried out the phishing and why AIXBT issued a transfer instruction to its address... However, since the original attacker Fungus Man has cancelled his account, historical interaction records are difficult to review, so the reason is not clear for the time being.

AI self-owned and self-managed assets have also been a major narrative in this round of AI innovation cycle, but the AIXBT incident is obviously a heavy blow to this narrative, and may cause a series of ripple effects on the subsequent development of the AI track.

The incident is still ongoing, and Odaily Planet Daily will continue to pay attention and follow the latest developments.

Original article, author:Azuma。Reprint/Content Collaboration/For Reporting, Please Contact report@odaily.email;Illegal reprinting must be punished by law.

ODAILY reminds readers to establish correct monetary and investment concepts, rationally view blockchain, and effectively improve risk awareness; We can actively report and report any illegal or criminal clues discovered to relevant departments.

Recommended Reading
Editor’s Picks