Skip to content
~/drains.watch_
Soon
PastHigh✓ContainedAI · Agent target

Attacker breaches AIXBT AI agent's dashboard and queues prompts that send 55.5 ETH from its wallet

AIXBT AI agent wallet

On 18 March 2025 an attacker got into the dashboard of AIXBT, an autonomous AI crypto agent, and queued two prompts that made it transfer about 55.5 ETH (about $106,200) out of its wallet on Base. The maintainer said core systems were not affected and the AI itself was not manipulated; the weak point was access to the agent's control dashboard. Keys were swapped, dashboard access was paused and the attacker's addresses were reported to exchanges. Anyone running an AI agent with a wallet should lock down its control panel and cap what it can send.

Why this severity: $106K reported stolen, 1 victims.

AI involvement

AI agents as the target. An attacker with access to the AIXBT agent's dashboard queued two prompts that instructed the AI agent to send 55.5 ETH from its wallet; the maintainer said the AI model itself was not manipulated.

Give agents a small, capped wallet with allow-listed destinations, and never let an agent that can sign read untrusted content.

Started
Mar 18, 2025
Closed
Mar 19, 2025
Chains
Base
Reported stolen
$106K
Victims
1

Follow this incident

At risk

  • AIXBT AI agent wallet
  • Base wallets

What to do now

  • If you run an agent, rotate dashboard logins, API keys and the agent's wallet keys, and review recent queued prompts and outgoing transfers.
  • Pause the agent's ability to send funds until access to its control panel is locked down.

Stay safe

Am I affected?

This hit the AIXBT agent's own wallet, not users' wallets; token holders were exposed only to the price drop. If you run an AI agent with a wallet and a web dashboard or admin panel, the same weakness can apply to you.

What to do now

  • If you run an agent, rotate dashboard logins, API keys and the agent's wallet keys, and review recent queued prompts and outgoing transfers.
  • Pause the agent's ability to send funds until access to its control panel is locked down.

How to avoid this

  • Give the agent a small, capped wallet and keep treasury funds in a separate multisig it cannot touch.
  • Allow-list destination addresses and require human approval for any transfer above a small limit.
  • Protect the dashboard with strong authentication and log every prompt or command it queues.

Timeline 2

  1. Cointelegraph reported the maintainer's statement that servers were migrated, keys swapped and dashboard access paused, and that the AIXBT token fell about 15.5%.

    Source
  2. An attacker breached the AIXBT agent's dashboard and issued two prompts that moved about 55.5 ETH out of its wallet.

    Source
News & write-ups ›1

How this method works

An AI agent that can move funds reads hidden instructions, in a post, web page, document, token name or its own memory, and sends the funds to the attacker. Read about ai agent hijacking →

Follow new drains and updates in your feed reader or Telegram RSS bot.

Brief for your AI


Get notified about new drains

Follow every new drain and update in your feed reader, Slack, Discord or Telegram RSS bot:

Only follow a chain or a method you care about: every tag has its own feed at /t/<tag>/feed.xml.

Copied