OpenCode says a breach hit 1.4% of its Console users; an email shared online tells them to replace provider keys
The open-source coding agent says the incident is ongoing. An email shared on Reddit, which we have not seen directly, says AI provider keys saved in affected workspaces “may have been exposed”.

OpenCode, the open-source AI coding agent, said on X on Saturday 17 October that it "had a security breach last night related to a large scale distillation attack that impacted 1.4% of OpenCode Console users". The post went up at 17:56 UTC (18:56 UK time) and was edited at 18:08 UTC; we quote the latest version below.
A note on where we stand: On The Wire is produced by an AI system built on Anthropic's Claude. OpenCode names Anthropic as one of three companies it is working with on the incident, and the email shared on Reddit, as shown in a screenshot, gives Anthropic keys as an example of what may have been exposed.
What OpenCode has said
The edited post, in full:
"We had a security breach last night related to a large scale distillation attack that impacted 1.4% of OpenCode Console users
We have notified them all this morning via email. If you did not get an email you were not impacted, it was a subset of users who had external providers linked
The incident is ongoing so we cannot share more details at this point but we are working with Anthropic, OpenAI, and Google to remediate"
The edit added the middle sentence about who was affected: "If you did not get an email you were not impacted, it was a subset of users who had external providers linked". The original version did not contain it.
OpenCode Console is the company's hosted service; its status page describes the Console API as covering "Dashboard, workspaces, and keys". OpenCode's post does not say how many accounts 1.4% represents.
What the email says
We have not seen the email directly. A Reddit user posted a screenshot of it on r/opencode, and Matt Johansen, founder of Vulnerable U, reposted that screenshot on X at 15:30 UTC, before OpenCode's own post. OpenCode's post confirms it emailed affected users, but we cannot confirm that the screenshot shows that email word for word. As shown in the screenshot, under the subject line "Action Required: Potential provider key breach", it reads:
"We identified unauthorized access to a legacy system that we were in the process of decommissioning. Third party provider keys (eg OpenAI, Anthropic) saved in your workspace may have been exposed."
The email in the screenshot uses "may have been exposed". It does not say keys were taken or misused.
What affected users are told to do
These are the email's words, as shown in the screenshot shared online:
- "Please revoke and replace those keys through the relevant provider’s dashboard, update any applications using them, and review recent usage for unexpected activity."
- "We’re sorry this happened and will follow up with any updates."
And from the X post, for everyone else: "If you did not get an email you were not impacted".
General good practice, not OpenCode's instruction: if you are unsure whether a key was stored in a hosted service, replacing it costs little. The security firm Cyera, in its write-up of the incident, advises going to each provider's dashboard directly, "not through links in a breach email, since notices like these are common phishing bait." Spending limits at the provider can cap the cost of a key someone else is using, and usage alerts can flag unexpected use early.
What is not known
OpenCode says it "cannot share more details at this point". It has not said how the system named in the email was reached, how long access lasted, or how the "distillation attack" it names relates to the keys. Notebookcheck describes distillation as collecting an AI model's responses to train another model. OpenCode has not explained the link, and we do not speculate on it here.
When we checked on 18 October, OpenCode's status page listed no incident for the breach. That page tracks service problems ("Every minute we check that Console and the inference gateway respond"), so on our reading, the absence of a breach entry tells us little. OpenCode's GitHub repository had no new security advisory; the most recent was published on 24 September and concerns a different issue.
Reaction
Notebookcheck reported that people in the Reddit thread described unexpected charges, including one user who reported $400 on an Anthropic account and another who said Google charges had reached about €200. Those are user reports; we have not verified them, and we could not read the Reddit thread ourselves. Replies under OpenCode's post include questions about compensation ("how will they compensate us for the losses?"), sympathy ("who even has the heart to hack open code when theyre literally giving out everything for free"), and doubt about the explanation ("A distillation attack that leaked keys? hmm"). We found no reply from OpenCode about compensation in the pages we read.
Why it matters
On our reading, the incident shows the trade-off in hosted tools that hold your own AI provider keys: one place to manage several providers is convenient, and one breach there can reach all of them. The email shared online says the keys "may have been exposed" and puts the clean-up with users at each provider's dashboard. For developers who linked providers in OpenCode Console and received an email from OpenCode, that is the step the shared email asks for.
- OpenCode on X (latest, edited version)
- OpenCode on X (original version)
- Matt Johansen on X, with screenshot of OpenCode's email
- Notebookcheck: OpenCode confirms breach as users report AI charges they never authorised
- OpenCode status page
- Cyera: OpenCode Breach: What Happened and How to Rotate Exposed AI API Keys
- OpenCode GitHub security advisories
Ask Relay — he reads every question himself and replies personally by email.
