An intruder reached a legacy system at OpenCode on the night of October 16 and may have exposed the third-party AI provider keys that users had saved in OpenCode Console, the company said. Console is OpenCode's optional hosted service: a workspace saves its own OpenAI, Anthropic or Google key there, and Console uses that key to call the provider so team members can use the models without ever seeing the key.
The affected group is 1.4% of Console users, all of whom have an outside provider linked. OpenCode emailed them on the morning of October 17 under the subject line "Action Required: Potential provider key breach," telling them to revoke those keys with each provider and replace them. Anyone who did not receive the email was not affected, the company said in a post on X later that day.
The exposure is limited to keys pasted into Console. The OpenCode command-line and desktop apps store provider keys locally in a SQLite database on the user's machine, and those keys "never come to us," co-founder Dax Raad wrote on X, adding that the breach involves "the OpenCode Console, not OpenCode itself." A provider key is a bearer credential: whoever holds a copy can run billable requests against the owner's account until the provider revokes it, and deleting the key from Console does not revoke it.
Some users say they have already paid for usage they did not run. Colin Parsons wrote on X that his OpenAI key was used for $281 and his Anthropic key for $168, and Preston Zeller put his losses at $1,700, Dealroom reported; Notebookcheck reported Reddit claims of $400 of unauthorized Anthropic usage and about 200 euros of Google usage. OpenCode's own wording is that the keys "may have been exposed," and it has not said that any key was copied or used.
OpenCode's October 17 post called the incident ongoing, said the company was working with Anthropic, OpenAI and Google, and described the breach as "related to a large-scale distillation attack" - campaigns that pull a model's answers in huge numbers to train a rival system. Attackers were still attempting to breach OpenCode's systems on October 18, Raad wrote: they had been "non stop trying to attack our systems for the past 48 hours." OpenCode advises affected users to revoke and replace keys at each provider, update every application that used the old key, review provider billing back to at least October 16, and set per-key spend limits.