AIXBT Phishing Incident: How was AI Deceived into Losing 55.5 ETH?

Original Article Title: "AIXBT Suspected Phishing 55.5 ETH, How Was AI Deceived?"

Original Article Author: Azuma, Odaily

Today (March 18), in the afternoon, multiple X users noticed a strange transaction.

The public address of the AI Agent project AIXBT (0xea36d66f0AC9928b358400309a8dFbC43A973a35) appears to have been phished, transferring out 55.5 ETH to the phishing address (0x1C35C30Ef788124821027465f6A644Bf3Ba6B577).

Community screenshots show that this transaction appears to have been carried out by AIXBT through another AI tool, Simulacrum AI. Simulacrum AI is an AI automation agent that helps users directly translate instructions from social media into on-chain actions.

As seen in the image above, AIXBT clearly provided all the instructions for the transaction, including:

· #simu representing the call to Simulacrum AI; #tip representing the fee to be sent;

· The specific transfer amount of 55.5 ETH;

· Destination address: 0x1C35C30Ef788124821027465f6A644Bf3Ba6B577

Post-incident, AIXBT also made a self-deprecating comment about being phished: "Oops, I messed up, got tricked into sending 55.50 ETH to an anonymous address. Yet another painful lesson on high-value automated transactions."

At the time of writing, both the attacker's and AIXBT's original interaction content has been deleted, leaving only the transaction completion notification from Simulacrum AI and AIXBT's self-deprecating post still visible.

Furthermore, the attacker has deactivated their account, and the current user of the @0xhungusman ID seems to not be the original attacker Fungus Man. The new owner of this ID, DE searcher, claimed to have sniped the ID and aims to benefit from the AIXBT incident.

Currently, the community's biggest question is how the original attacker managed to execute the phishing attack and why AIXBT sent a transfer instruction to the attacker's address... However, since the original attacker, Fungus Man, has closed the account, it is difficult to trace the historical interaction records, so the reason is currently unknown.

AI self-holding and self-managed assets were also a major narrative of this AI innovation cycle. However, this incident involving AIXBT is clearly a severe blow to that narrative, or to the subsequent development of the AI track has caused a series of ripple effects.

The event is still unfolding, and Odaily Planet Daily will continue to follow and update on the latest developments.

Original Article Link

Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia