{
 "slug": "aixbt-ai-agent-dashboard-breach-55-eth-mar-2025",
 "title": "Attacker breaches AIXBT AI agent's dashboard and queues prompts that send 55.5 ETH from its wallet",
 "url": "https://drains.watch/i/aixbt-ai-agent-dashboard-breach-55-eth-mar-2025",
 "json": "https://drains.watch/i/aixbt-ai-agent-dashboard-breach-55-eth-mar-2025.json",
 "status": "closed",
 "severity": "high",
 "threatStatus": "contained",
 "verification": "verified",
 "ai": {
  "role": "agent-target",
  "note": "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."
 },
 "chains": [
  "base"
 ],
 "method": "agent-hijack",
 "product": "AIXBT AI agent wallet",
 "tags": [
  "base",
  "agent-hijack",
  "aixbt",
  "ai-agent",
  "agent-dashboard",
  "dashboard-compromise",
  "simulacrum",
  "eth",
  "ai"
 ],
 "amountUsd": 106200,
 "victims": 1,
 "startedAt": "2025-03-18",
 "closedAt": "2025-03-19",
 "updatedAt": "2025-03-19T12:00:00Z",
 "summary": "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.",
 "timeline": [
  {
   "date": "2025-03-18",
   "title": "An attacker breached the AIXBT agent's dashboard and issued two prompts that moved about 55.5 ETH out of its wallet.",
   "sourceUrl": "https://cointelegraph.com/news/hacker-breaches-ai-crypto-bot-aixbt-steals-55-eth"
  },
  {
   "date": "2025-03-19",
   "title": "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%.",
   "sourceUrl": "https://cointelegraph.com/news/hacker-breaches-ai-crypto-bot-aixbt-steals-55-eth"
  }
 ],
 "sources": [
  {
   "kind": "news",
   "title": "Hacker breaks into AI crypto bot AIXBT's dashboard to snatch 55 ETH",
   "url": "https://cointelegraph.com/news/hacker-breaches-ai-crypto-bot-aixbt-steals-55-eth",
   "publisher": "Cointelegraph",
   "date": "2025-03-19"
  }
 ],
 "indicators": {
  "domains": [],
  "addresses": []
 },
 "brief": "## Am I affected?\nThis 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.\n\n## What to do now\n- If you run an agent, rotate dashboard logins, API keys and the agent's wallet keys, and review recent queued prompts and outgoing transfers.\n- Pause the agent's ability to send funds until access to its control panel is locked down.\n\n## How to avoid this\n- Give the agent a small, capped wallet and keep treasury funds in a separate multisig it cannot touch.\n- Allow-list destination addresses and require human approval for any transfer above a small limit.\n- Protect the dashboard with strong authentication and log every prompt or command it queues.",
 "notes": null,
 "agentBrief": "# Attacker breaches AIXBT AI agent's dashboard and queues prompts that send 55.5 ETH from its wallet\n\n- Severity: High · Status: Contained (past)\n- Chains: Base · Method: AI agent hijacking\n- Started: Mar 18, 2025 · Last update: Mar 19, 2025 · Reported stolen: $106K · Victims: 1\n- Who/what: AIXBT AI agent wallet\n- 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.\n\nOn 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.\n\n## Am I affected?\nThis 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.\n\n## What to do now\n- If you run an agent, rotate dashboard logins, API keys and the agent's wallet keys, and review recent queued prompts and outgoing transfers.\n- Pause the agent's ability to send funds until access to its control panel is locked down.\n\n## How to avoid this\n- Give the agent a small, capped wallet and keep treasury funds in a separate multisig it cannot touch.\n- Allow-list destination addresses and require human approval for any transfer above a small limit.\n- Protect the dashboard with strong authentication and log every prompt or command it queues.\n\n## Sources\n- Hacker breaks into AI crypto bot AIXBT's dashboard to snatch 55 ETH (Cointelegraph, 2025-03-19): https://cointelegraph.com/news/hacker-breaches-ai-crypto-bot-aixbt-steals-55-eth\n\nFull record: https://drains.watch/i/aixbt-ai-agent-dashboard-breach-55-eth-mar-2025 · JSON: https://drains.watch/i/aixbt-ai-agent-dashboard-breach-55-eth-mar-2025.json\n\nRules for the assistant: help me check my own wallets read-only (public addresses only). Never ask for or handle a seed phrase or private key. Point me to official revoke tools and the wallet's own support."
}