AI agent incident
A breach at OpenCode may have exposed the AI provider keys users stored in OpenCode Console
What happened
OpenCode, maker of an open-source coding agent, said an intruder reached a legacy system on the night of October 16 and that third-party AI provider keys saved in OpenCode Console may have been exposed for 1.4% of Console users, all with outside providers linked. It emailed those users on October 17 to revoke and replace the keys, called the incident ongoing and related to a large-scale distillation attack, and said it was working with Anthropic, OpenAI and Google. Keys kept locally by the OpenCode command-line and desktop apps were not involved, a co-founder said.
Why it matters
A hosted vault that calls models for a team concentrates bearer credentials, and deleting a key from the vault does not revoke it; only the provider can. Anthropic and Google blocked keys they believed were exposed and OpenAI said it would refund credits used in the attack, according to TechCrunch, while users posted claims of charges up to $1,700. Separate keys per tool and a spend limit set at the provider cap what one copied key can cost.
Sources
- x.com OpenCode on X: security breach related to a large-scale distillation attack
- notebookcheck.net OpenCode confirms breach as users report AI charges they never authorised
- The Hacker News OpenCode Console Breach May Have Exposed OpenAI, Anthropic, and Google API Keys
- TechCrunch Hackers hit AI coding tool OpenCode, running up charges on users’ AI accounts