Skip to main content
AVOID.NET
← aixbt (AIXBT)1 decision on this page

Audit log

Every state-changing event for aixbt (AIXBT): moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1publishby system:backfill
    2026-10-13 05:10:02Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 456,321,597
    sig
    xjnjcYtCz3bw…cF5F77Szexplorer ↗
    hash
    6gKvUex5dKvK…Ew85et2Asha256 → base58
    verifying row…full verify ↗
    canonical bytes (5962 B) ▸
    {"actor":"system:backfill","investigation_id":"abd73d9c-ad66-4aa6-93d9-cc8c81575aa8","kind":"publish","page_slug":"aixbt-aixbt","published_at":"2026-10-13T05:10:02.666Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"aixbt (AIXBT)","sections":[{"content":"Cointelegraph reported that on 18 March 2025, at about 1:58 am UTC, an attacker breached the dashboard of the aixbt bot and queued two prompts that caused 55.5 ETH (about $106,200) to be moved out of the bot's wallet. Observers initially believed the AI had been manipulated, after Simulacrum AI posted that it had sent a 55.5 ETH tip to an X account, 0xhungusman, which has since been suspended. The maintainer, rxbt, stated that core systems were not affected and that the breach did not result from manipulating the AI. Remediation steps reported were migrating servers, swapping keys, pausing dashboard access for security upgrades, and reporting the attacker's addresses to exchanges. The AI Incident Database (incident 1003) records the event as an alleged compromise and lists rxbt as developer and 0xhungusman as alleged deployer; the attribution is unconfirmed and the identity of the attacker has not been established in the sources reviewed. Per CoinGecko data cited by Cointelegraph, the AIXBT token fell 15.5% to about 9 cents after the incident.","heading":"March 2025 dashboard compromise","severity":"high","sources":[{"credibility":2,"name":"Cointelegraph: Hacker breaches AI crypto bot aixbt, steals 55 ETH","type":"news_article","url":"https://cointelegraph.com/news/hacker-breaches-ai-crypto-bot-aixbt-steals-55-eth"},{"credibility":2,"name":"AI Incident Database, Incident 1003","type":"research","url":"https://incidentdatabase.ai/cite/1003"}]},{"content":"Sources describe the project as maintained by a pseudonymous developer, rxbt. The 2025 incident involved a dashboard that allowed prompts to direct the agent to move funds, which the maintainer characterized as an access breach rather than AI manipulation. A researcher quoted by Cointelegraph (S4mmy) said AI agents managing crypto funds need more testing to resist compromise. Only one explainer-type source (low credibility) describes the pseudonymous team; no formal complaint or enforcement action naming any individual was found.","heading":"Pseudonymous maintainer and operational security","severity":"medium","sources":[{"credibility":2,"name":"Cointelegraph: Hacker breaches AI crypto bot aixbt, steals 55 ETH","type":"news_article","url":"https://cointelegraph.com/news/hacker-breaches-ai-crypto-bot-aixbt-steals-55-eth"},{"credibility":3,"name":"Plisio: AIXBT explained (explainer)","type":"other","url":"https://plisio.net/de/ai/aixbt"}]},{"content":"On a CoinGecko page fetched on 13 October 2026, AIXBT showed a price of about $0.02065 and a market cap of about $20.6M (the page also gave $20,537,701 in its FAQ); circulating, total and maximum supply were each listed as 1 billion. Other CoinGecko-derived snapshots in search results showed values between roughly $19.4M and $26.9M, so the figure is time-dependent; the requester's $20.8M figure on 7 October could not be independently reproduced but is consistent with this range (a Blockworks page powered by CoinGecko listed $20.86M). CoinGecko lists an all-time high of $0.9426 and an all-time low of $0.01634 on that page, implying a decline of roughly 98% from peak. Low-credibility guides report similar drawdowns.","heading":"Market profile and volatility","severity":"medium","sources":[{"credibility":2,"name":"CoinGecko: aixbt","type":"other","url":"https://www.coingecko.com/en/coins/aixbt"},{"credibility":2,"name":"Blockworks: AIXBT price","type":"other","url":"https://blockworks.com/price/aixbt"}]},{"content":"No regulatory action, court filing or formal investigation concerning aixbt was found in the searches performed. This reflects limited search coverage and is not a clearance.","heading":"Regulatory and legal status","severity":"low","sources":[{"credibility":2,"name":"CoinGecko: aixbt","type":"other","url":"https://www.coingecko.com/en/coins/aixbt"}]}],"sources_used":[{"credibility":2,"name":"Cointelegraph: Hacker breaches AI crypto bot aixbt, steals 55 ETH","type":"news_article","url":"https://cointelegraph.com/news/hacker-breaches-ai-crypto-bot-aixbt-steals-55-eth"},{"credibility":2,"name":"AI Incident Database, Incident 1003","type":"research","url":"https://incidentdatabase.ai/cite/1003"},{"credibility":2,"name":"CoinGecko: aixbt","type":"other","url":"https://www.coingecko.com/en/coins/aixbt"},{"credibility":2,"name":"Blockworks: AIXBT price","type":"other","url":"https://blockworks.com/price/aixbt"},{"credibility":3,"name":"Plisio: AIXBT explained","type":"other","url":"https://plisio.net/de/ai/aixbt"}],"summary":"aixbt (AIXBT) is an AI-agent token, listed on CoinGecko on Base, Ethereum and Solana, associated with an AI bot that posts crypto market commentary and maintained by a pseudonymous developer known as rxbt. On 18 March 2025 an attacker allegedly accessed the bot's operator dashboard and moved about 55.5 ETH (about $106,200 at the time); the maintainer stated the AI itself was not manipulated. This search found no regulatory action against the project, but its maintainer is pseudonymous and the token trades far below its all-time high.","timeline":[{"date":"2025-03-18","date_evidence":"Date: March 18, 2025, at 1:58 am UTC","event":"Attacker allegedly accessed the aixbt dashboard and moved 55.5 ETH (about $106,200); maintainer rxbt said the AI was not manipulated.","source":"Cointelegraph","source_url":"https://cointelegraph.com/news/hacker-breaches-ai-crypto-bot-aixbt-steals-55-eth"},{"date":"2025-03","event":"AIXBT token reportedly fell 15.5% to about 9 cents after the incident; dashboard access was paused and keys swapped.","source":"Cointelegraph","source_url":"https://cointelegraph.com/news/hacker-breaches-ai-crypto-bot-aixbt-steals-55-eth"}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 86816e71-aa7b-489e-9c1f-ef11430bb07a
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.