Incidents: security events for AI agents that touch money
How we use this list. Only incidents with an official source (the vendor's own disclosure, advisory or security release) are added, and we only state amounts the official source states. When an incident names a listed tool, it shows on that tool's page and lowers the incident record input of its Agent Risk Score: an unresolved incident in the last 12 months scores 0 of 10, one resolved incident 5. The tracker started on October 23, 2026, so older incidents appear only once they are added with an official source.
Under review: unconfirmed reports
- 2026-10-26 Unconfirmed Reports that wallets used with the Bloom trading bot were drained: about 9,408 SOL from 41 to 48 wallets moved to one address within a minute, each transfer signed with the owner's own key. Bloom says 49 wallets belonging to 9 users were affected, that it will fully reimburse those users to new wallets they choose, and that it is still investigating the root cause, including whether a third-party provider was compromised; earlier it said all other wallets remain safe and temporarily disabled some services. Bloom staff earlier pointed to another tool. Check page
October 24, 2026
- 2026-10-24 Incident Open / not stated as resolved Initia said a bug in MoveVM script caching let an attacker credit themselves unbacked WETH, iUSD and USDC and bridge about $2.7M out (via LayerZero and CCTP, swapped to 1,135.52 ETH) before it halted the L1 and its rollups; it said no native INIT was minted and that a fix was being written and audited. Source
- 2026-10-24 Incident Open / not stated as resolved Keystone said a third party pulled customer shipping data (names, contact details, shipping addresses, items bought and prices) from its website store via the Shopify API, detected October 20 and confirmed October 23; it said payment details, recovery phrases, private keys and wallet passwords were not exposed, and warned of scammers posing as Keystone with refunds or replacement devices. Source
October 23, 2026
- 2026-10-23 Incident Open / not stated as resolved Electrum released 4.8.3 as a security update; press reports of its advisory say earlier versions let a malicious Electrum server plant a fake pending payment so that a later fee bump (RBF) paid the attacker, and that users of trusted servers were not exposed. Update to 4.8.3 or later. Source
October 21, 2026
- 2026-10-21 Incident Open / not stated as resolved Railway disclosed that an unauthorized third party may have accessed encrypted environment variables and obtained the decrypted contents of some of them; it told users to immediately roll all environment variables and API keys stored in Railway and paused all deployments while it investigates. Source
- 2026-10-21 Incident Open / not stated as resolved Microsoft reported that the China-state aligned actor Storm-0940 used ARTEX, an open-source multi-agent LLM penetration-testing framework, to automate scanning, password spraying and OAuth app abuse in a ConnectWise cloud backup supply-chain compromise aimed at hundreds of organizations. Source
- 2026-10-21 Incident Resolved Node.js security releases v22.23.4, v24.22.1 and v26.12.1 fix ten vulnerabilities, including a high-severity Brotli decoder out-of-bounds write that permits remote code execution (CVE-2026-111497) in the 22.x, 24.x and 26.x lines. Source
What to do when an incident hits a tool you use
Already lost funds? Follow what to do if a bot or wallet is drained.
- Rotate any API key, secret or environment variable the affected service could read, starting with exchange keys that can trade.
- Check that trading keys have withdrawals off and are bound to your server's IP.
- Pause the agent until the vendor says the incident is contained.