OpenCode Breach Exposes API Keys for 1.4% of Console Users

OpenCode confirmed on October 17 that a security breach exposed third-party API keys for 1.4% of its Console users. The company linked the incident to a large-scale distillation attack and stated it is working with major AI providers to address the exposure.

The disclosure followed an earlier confirmation by OpenCode that user credentials had been compromised in an unauthorized access event, as Threat Times reported on October 17. The new details specify that the exposure involves API keys stored in workspaces linked to external providers such as OpenAI and Anthropic.

View the original post on X

Context and Background

OpenCode stated that attackers gained unauthorized access to a legacy system that the company was already preparing to shut down. This access potentially exposed provider keys saved in user workspaces. The company did not provide technical evidence showing how the breach supported the reported distillation activity or how long attackers remained inside the system.

Distillation involves training one AI model using responses generated by another. In unauthorized campaigns, attackers can collect large amounts of model output without permission. Cyber Security News previously covered warnings from Anthropic about these large-scale distillation attacks, noting how repeated requests can transfer capabilities between models.

OpenCode has not explained whether the exposed credentials were actually used to make those requests. The public statement establishes a reported connection between the breach and the attack type, but it does not offer a complete account of the intrusion or name a specific threat actor.

Who Is Affected

The incident affects only 1.4% of OpenCode’s Console users, not its entire user base. The affected group was limited to those who had linked external providers to their workspaces. OpenCode said it emailed every impacted user that morning and stated that anyone who did not receive an email was not affected by this specific incident.

The company’s notification described possible exposure rather than confirming that every affected key was stolen or used. There is no confirmed loss figure in the public disclosure. The notice asks recipients to review recent usage for unexpected activity and update any applications that rely on the compromised keys.

What should you do?

For notified users, the immediate response is the key replacement process described in the warning. Users must revoke and replace their keys through each provider’s dashboard. The company did not specify how many keys were involved or provide a timeline for when the legacy system was fully secured.

What to do and how to stay safe: OpenCode

• Check your email for notifications from OpenCode indicating whether your Console account was affected by this specific incident.
• Revoke and replace any third-party API keys linked to your workspace through the respective provider dashboards, such as OpenAI or Anthropic.
• Review recent usage logs for unexpected activity that might indicate unauthorized access to your accounts or applications.
• Monitor your accounts for further updates from OpenCode regarding the status of the legacy system and any additional remediation steps.

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

How many users were affected by the OpenCode breach?

The breach affected 1.4% of OpenCode’s Console users, specifically those who had linked external providers to their workspaces.

What type of attack was linked to this incident?

OpenCode linked the incident to a large-scale distillation attack, which involves training one AI model using responses generated by another.

Is there a patch or fix available for this issue?

No fix has been confirmed yet; users are advised to revoke and replace their API keys through provider dashboards.