OpenCode breach may have exposed users' OpenAI, Anthropic and Google API keys

OpenCode, the open-source AI coding agent developed by Anomaly Innovations (formerly SST), disclosed on Saturday, October 17, that attackers gained unauthorized access to a legacy system behind its OpenCode Console and may have exposed third-party AI provider API keys stored in user workspaces. According to Startup Fortune and Blockonomi, the company said roughly 1.4% of Console users were affected, specifically those who had linked external provider accounts such as OpenAI, Anthropic and Google. The incident matters because stolen provider keys can be used to run AI queries billed to the victim, and several users say that has already happened.

What happened

Blockonomi reports that OpenCode announced the incident on X on October 17, saying the breach occurred the night before, and emailed affected users the following morning. Startup Fortune notes that accounts differ on whether the notification emails went out on October 17 or the morning of October 18.

In its notice, as quoted by Startup Fortune, the company said it "identified unauthorized access to a legacy system" and that provider keys saved in users' workspaces "may have been exposed." Blockonomi says the legacy system was one OpenCode was preparing to decommission. The company described the incident as "related to a large scale distillation attack", but, according to both outlets, has not released technical details on how the attackers got in, who was responsible or how long the activity lasted.

OpenCode said it has notified every affected account, is working with Anthropic, OpenAI and Google, and has so far found no evidence that other data leaked. The company also said it could not confirm whether the exposed keys were used maliciously and that the investigation is ongoing.

Reported impact

Startup Fortune reports that some users said their OpenAI and Anthropic bills were "climbing into the hundreds of dollars" from queries they did not make, in some cases before they received the company's email. The outlet also cites unverified posts on X claiming that one developer's Google Cloud project was suspended and that OpenAI deleted another developer's account over terms violations; Startup Fortune said it could not verify these claims. OpenCode co-founder Dax Raad reportedly said his personal accounts were also targeted.

The term "distillation" usually refers to training a model on another model's outputs, and Startup Fortune notes that it does not by itself explain how the keys were obtained. The outlet suggests the keys may have been exposed and then used at scale for distillation queries, a sequence the company has not confirmed.

Who is affected

The exposure concerns provider keys stored in the OpenCode Console, the company's hosted service, for users with linked external providers. OpenCode has not disclosed how many accounts the 1.4% figure represents, and Startup Fortune notes it is unclear whether keys kept in local configuration files were affected.

What to do

Both outlets advise OpenCode Console users, particularly those who received the notification, to:

• Revoke and reissue every OpenAI, Anthropic and Google key used with the Console, directly from each provider's dashboard rather than through links in emails.
• Review billing and usage logs from October 17 onward for unexpected activity.
• Set spending limits and usage alerts on provider accounts.
• Update pipelines, CI jobs and local setups that relied on the old keys.

Until OpenCode publishes its findings, any key that was stored in the Console should be treated as compromised.