OpenCode disclosure October 17, 2026; analysis updated October 17 to 19, 2026
OpenCode Console Breach Exposed Stored AI Provider Keys for 1.4 Percent of Users
OpenCode confirmed on October 17 that a breach of a legacy Console system it was in the process of retiring exposed provider API keys that users had stored in Console workspaces, affecting approximately 1.4 percent of Console users, specifically those who had linked external providers. The exposed keys were for OpenAI, Anthropic, Google, and other providers, and OpenCode described the incident as a large-scale distillation attack, in which stolen keys are used to run high-volume automated queries against frontier models and capture the outputs, leaving the key owners with the charges. Affected users reported unauthorized charges ranging from a few hundred dollars to more than $1,700, and some Google projects were suspended after being flagged for abusive activity consistent with hijacked resources. OpenCode emailed affected users, said anyone who did not receive an email was not impacted, and worked with Anthropic, OpenAI, and Google on revocation and remediation. The local OpenCode command-line tool was not the affected system: keys added locally never came to OpenCode. How the attackers got in and how the keys were stored had not been explained in the verified reporting, and no technical indicators of compromise had been publicly disclosed.
Executives
The stolen asset here was not data. It was billable access to frontier models, spent within hours. Any tool where your staff paste provider keys becomes part of your credential estate, and this incident shows the two controls that cap the damage: per-project scoped keys and hard spend limits on every provider account, set before an incident, not during one.
CIO / CISO
Ask every development team whether anyone received the OpenCode notice, rather than waiting for it to reach security. Require key ownership records for provider credentials, because unowned keys are the ones nobody rotates, and treat hosted consoles that store third-party secrets as in-scope vendors under your ISO 27001 access control and supplier processes. Legacy systems awaiting decommissioning that still hold live credentials belong at the top of the risk register until they are actually off.
Engineers
Revoke exposed keys in each provider's own dashboard, not inside OpenCode, because deleting a key from the console does not stop someone who already copied it. Go to the dashboard directly rather than through links in a breach email, issue replacements, move every consumer to the new key, and confirm the old key returns HTTP 401. Review provider usage and billing from October 16 onward for spikes and unfamiliar models, and set spend alerts on every account.
Everyone (non-IT)
If you pasted a work AI key into any online tool, tell your IT team which tool and which key, even if you never got a breach email. Rotating a key takes minutes, and it is far cheaper than explaining a four-figure charge that arrived overnight.