OpenCode says a security breach tied to a large scale distillation attack hit 1.4% of OpenCode Console users with external providers linked
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
Context
Coding tools that store users' links to model providers are attractive targets, and a breach like this can expose access that attackers use to extract model outputs.
This is a first hand statement from OpenCode, the open source coding agent. The company says the incident is ongoing and has shared few details, so the cause, scope and what data was exposed remain unconfirmed.
Deep dive
On October 17, OpenCode posted that it had a security breach the night before related to a large scale distillation attack that impacted 1.4% of OpenCode Console users.
It said it notified all affected users that morning by email, that anyone who did not get an email was not affected, and that the breach hit a subset of users who had external providers linked. It added that the incident is ongoing, so it cannot share more details yet, and that it is working with Anthropic, OpenAI and Google to remediate.
The post was edited. An earlier version, posted about twelve minutes before, did not include the lines saying users without an email were not affected or that only users with external providers linked were hit.
In AI, a distillation attack generally means sending large numbers of requests to a model to collect its outputs and train another model on them. OpenCode did not explain how the attack worked or how it led to the breach, and the involvement of Anthropic, OpenAI and Google suggests their model accounts were involved, though OpenCode has not said so.
OpenCode has not said whether keys, tokens or other data were exposed, how many users 1.4% represents, or what affected users should do.
What to expect next
Watch for a fuller incident report from OpenCode explaining how the breach happened, what data or credentials were exposed and what affected users should do.
Also watch whether Anthropic, OpenAI or Google comment on the distillation attack, and whether other coding tools that store links to model providers review their own security. Advice to rotate keys or reconnect providers would be a sign of how serious the exposure was.