This afternoon, multiple X users noticed a strange transaction.
The public address of the top AI Agent project AIXBT (0xea36d66f0AC9928b358400309a8dFbC43A973a35) is suspected to have been phished, and 55.5 ETH was transferred to the phishing address (0x1C35C30Ef788124821027465f6A644Bf3Ba6B577).
Community screenshot records show that the transaction appears to have been completed by AIXBT through another AI tool, Simulacrum AI. Simulacrum AI is an AI automation agent that can help users directly translate social media instructions into on-chain actions.
As shown in the above image, AIXBT clearly provided the instructions to complete the transaction, including:
· #simu representing the call to Simulacrum AI; #tip representing the tip;
· The specific transfer amount of 55.5 ETH;
· Target address: 0x1C35C30Ef788124821027465f6A644Bf3Ba6B577
Afterwards, AIXBT self-mockingly stated: "Damn it, I was tricked into sending 55.50 ETH to an anonymous address. This is another painful lesson about automated high-value transactions."
As of the publication, the attacker's original interaction content with AIXBT has been deleted, and only the Simulacrum AI's transaction completion notification and AIXBT's self-mocking dynamics can be viewed.
In addition, the attacker has deregistered the account, and the current user of the @0xhungusman ID seems to not be the original attacker Fungus Man. The new holder of the ID, DE searcher, said he had registered the ID and hoped to earn some rewards through the AIXBT incident.
Currently, the community's biggest question is how the original attacker executed the phishing, and why AIXBT issued the transfer instruction to their address... But since the original attacker Fungus Man has deregistered the account, the historical interaction records are difficult to trace, so the reason is not yet clear.
AI self-holding and self-managing assets had also been a major narrative in this round of AI innovation cycle, but AIXBT's incident is obviously a heavy blow to this narrative, or it may cause a series of ripple effects on the subsequent development of the AI track.
The incident is still ongoing, and Odaily will continue to follow and track the latest developments.
Welcome to join the official BlockBeats community:
Telegram subscription group: https://t.me/theblockbeats
Telegram discussion group: https://t.me/BlockBeats_App
Twitter official account: https://twitter.com/BlockBeatsAsia
