Short answer
OpenCode said an intruder broke into a legacy system overnight on 16 October 2026 and that AI provider keys saved in its hosted Console may have been exposed for about 1.4% of Console users. Some users reported hundreds to over 1,700 dollars in charges, which the company has not confirmed in full.
If you think your details were included, start with our checklist on what to do after a data breach.
Key facts
| Organization | OpenCode |
|---|---|
| Incident type | Data breach |
| Status | Confirmed by the organization |
| Sector | Developer tools (AI coding agent) |
| Country | United States |
| Detected | 2026-10-16 |
| Disclosed | 2026-10-17 |
| People or records affected | About 1.4% of OpenCode Console users (the company has not given a count) |
What data was exposed
- Third-party AI provider API keys (OpenAI, Anthropic, Google) saved in OpenCode Console
- Not affected, per the company: keys stored locally by the open source app and command-line tool
What happened
OpenCode, an open source AI coding agent, said an intruder reached an older internal system overnight on 16 October 2026. The Hacker News and TechCrunch both reported it on 19 October. The system held AI provider keys that users had saved in OpenCode Console, the company’s optional hosted service.
OpenCode emailed affected users on the morning of 17 October. It says about 1.4% of Console users were affected, all of them people who had linked an outside provider such as OpenAI, Anthropic or Google. It has not said how many people that is.
What was exposed
The company says the keys “may have been exposed.” It has not said whether specific keys were copied. The open source app and command-line tool were not affected, because keys they store stay in a local database on your machine and never reach OpenCode, according to co-founder Dax Raad.
Reported misuse
Several developers said they saw overnight spending alerts. According to The Hacker News, one reported $281 on an OpenAI key and $168 on an Anthropic key, another put losses at $1,700, and other users reported hundreds of dollars on Anthropic and Google. These figures are users’ own reports.
TechCrunch reports that Anthropic and Google blocked the keys they believed were exposed, and that OpenAI worked with OpenCode to restore access and refund its API customers for credits used in the attack. OpenCode said refunds for unauthorized charges were underway.
The distillation claim
OpenCode called the incident “a large-scale distillation attack.” Distillation means using a stronger model’s outputs to train another one, which needs large volumes of requests that stolen keys could pay for. The company has not explained how it knows this, who the attackers are, how they got in or when access began. TechCrunch notes that some skeptics see a plain breach whose distillation use is unproven. Raad also said attackers had tried to break in nonstop for 48 hours and that the company kept AI-based defensive agents running.
As of the reports, OpenCode called the incident ongoing.
What to do
Revoke and replace the key at the provider, because removing it from Console does not disable it. Then check billing, set spending limits, and give each tool its own key so one leak does not cover everything.
This overlapped with other developer platform incidents that month, including the Railway security incident.
Start with our data breach checklist. Copycat notices that ask you to log in to a provider fit the pattern in our guide to phishing messages.
Scams to watch for after this breach
Criminals use breach news as cover. Expect messages that mention the incident, quote real details, or offer help.
- Phishing emails copying OpenCode's 'Action Required' notice to steal your provider login.
- Fake refund or recovery offers aimed at people who report unauthorized AI charges.
- Stolen keys sold or used by others, producing large bills before you notice.
What to do if you are affected
- 01If you got OpenCode's 'Action Required: Potential provider key breach' email, revoke the key in your provider's dashboard and create a new one. Deleting it from Console does not revoke it.
- 02Update every app and script that used the old key.
- 03Review provider usage and billing back to at least 16 October for requests you did not make.
- 04Set a spend limit or alert at the provider, and use a separate key for each tool.
- 05If you did not get the email, OpenCode says you were not affected, but verify the email's sender before clicking anything.
Frequently asked questions
Am I affected if I only use the OpenCode command-line tool?
Co-founder Dax Raad said the open source app and command-line tool were not affected and that keys stored locally never come to OpenCode. The exposure is limited to keys saved in the hosted Console.
How do I know if my key was exposed?
OpenCode emailed affected users on 17 October with the subject 'Action Required: Potential provider key breach'. The company says anyone who did not get that email was not affected.
Were the charges people reported confirmed?
The reported charges come from users' own accounts of their bills, such as $281 on OpenAI and $168 on Anthropic for one developer and about $1,700 for another. OpenCode said refunds for unauthorized charges were underway, and OpenAI said it would refund its customers affected.
Was this really a distillation attack?
That is OpenCode's description. It has not explained the link, and TechCrunch notes skeptics who call it a plain breach with unproven distillation use.
Sources
- OpenCode Console Breach May Have Exposed OpenAI, Anthropic, and Google API Keys, The Hacker News, 2026-10-19
- Hackers hit AI coding tool OpenCode, running up charges on users' AI accounts, TechCrunch, 2026-10-19
This post summarises public reporting as of 2026-11-05. Details of live incidents change; we update posts when the organization or regulators publish new facts. Spot an error? See our editorial and corrections policy.