OpenCode breach: why every small business using AI tools should rotate its API keys
OpenCode, a popular open-source AI coding agent, confirmed a breach of a legacy system behind its hosted Console overnight on 16-17 October 2026. AI provider keys (for example OpenAI and Anthropic) saved in the workspaces of about 1.4% of Console users may have been exposed, and some users report charges they didn’t make. The lesson goes far beyond one tool: any AI key you paste into a third-party service is only as safe as that service.
What happened
On 17 October 2026, OpenCode said on X that it “had a security breach last night related to a large scale distillation attack that impacted 1.4% of OpenCode Console users” and that it emailed everyone affected. According to that email, as shared publicly by recipients, an unauthorized party accessed a legacy system the company was already decommissioning, and third-party provider keys saved in user workspaces may have been exposed.
OpenCode says the app that runs on your own computer keeps keys locally; the problem concerns keys that users chose to save in the hosted Console. Anthropic said it revoked Claude API keys it believes were affected, and OpenCode says it is working with Anthropic, OpenAI and Google. It has not yet explained how the attackers got in, how the keys were stored, or how many were misused. Some affected users report unexpected usage charges, which are self-reported and not independently verified.
What it means for you
- Your AI bill is now an attack surface. A stolen API key is effectively a company credit card. Set a hard monthly spend limit and usage alerts at every AI provider you use (OpenAI, Anthropic, Google and others), and switch off auto-reload where you don’t need it.
- One key per tool, not one key for everything. If your website chatbot, your marketing automation and your developer’s coding tool share a single key, one leak breaks all of them, and you can’t tell which tool leaked. Separate keys make it a five-minute fix.
- Know where your keys live. Make a short list: which tools, plugins and agencies hold your AI keys? Revoke keys at the provider’s own dashboard (not inside the third-party tool), issue new ones, update the tools, and check usage from 16 October onward. Treat “breach” emails with links as possible phishing and go to each dashboard directly.
2-Point Expert Read
Not sure how exposed your website is, or what AI assistants and search engines can see on it? Send me your link. Within 24 hours you get one finding about your website, one about your visibility on Google and in AI search, and a recommended next step. For small businesses and sole traders, no obligation.
Weekly AI Digest for Small Businesses
Once a week: AI news and what it means for your business.
Share this story
Sources
- Cyera Research: OpenCode Breach: What Happened and How to Rotate Exposed AI API Keys (in English)
- VibeIncidents: OpenCode provider key exposure, October 2026 (in English)