OpenCode Security Breach Exposes API Keys of 1.4% of Console Users
Key Takeaways
- •OpenCode reported that a security breach tied to a large-scale distillation attack affected approximately 1.4% of its Console users, potentially exposing API keys for OpenAI, Anthropic, and Google.
- •The unauthorized access occurred through a legacy system that OpenCode had been preparing to decommission.
- •OpenCode announced the incident on X on October 17, 2026, and said it notified all identified affected users by email the following morning, adding that users without a notification email were not impacted.
- •Affected users were instructed to revoke and replace their exposed keys, update dependent applications, and review their accounts for unexpected usage and charges.
- •The investigation remains ongoing, and OpenCode has not disclosed the total number of affected accounts or further technical details, though it is working with the affected providers.
OpenCode has disclosed a security breach that exposed third-party API keys belonging to approximately 1.4% of its Console users. According to the company's customer notification, the credentials exposed in the incident may have included API keys for OpenAI, Anthropic, and Google. The breach involved unauthorized access to a legacy system that OpenCode had been preparing to decommission, and the company said attackers carried out a large-scale distillation attack, although it has not released further technical details.
Affected users were instructed to revoke their keys, replace them with new credentials, and check their accounts for unexpected usage and charges. The company said users who did not receive a notification email were not among those impacted.
The disclosure raises concerns about credential security across AI development tools. Users who connect external providers through third-party platforms may face financial risks when attackers obtain their credentials, and the incident illustrates how an exposure at one service can quickly affect accounts across multiple providers.
How the Breach Unfolded
OpenCode announced the incident on X on October 17, 2026, confirming that unauthorized access had affected a subset of Console users with external providers linked. The company said it notified all identified affected users by email on the morning following the breach.
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…
According to the post, the breach occurred overnight and notification emails went out the following morning. The company emphasized that the incident was limited to users who had connected external providers to their Console accounts.
The customer notice identified a legacy system as the entry point. OpenCode had been preparing to decommission that system when the unauthorized access occurred. Third-party provider keys stored in user workspaces may have been exposed. That detail fits a familiar concern in security practice: systems awaiting decommissioning can continue to hold live credentials and stay reachable until they are fully retired.
The company is working with OpenAI, Anthropic, and to address the incident. However, OpenCode said the investigation remains ongoing and declined to share additional details.
Security commentator Matt Johansen also reported customer concerns about stolen keys and unexpected API charges. Community discussions described users receiving breach notifications and warnings to revoke their credentials.
Confirmed. OpenCode hacked. Keys stolen.
Telling customers to revoke. pic.twitter.com/onOyjWevr0
OpenCode has not disclosed the total number of affected accounts or confirmed the full extent of the attackers' access. The 1.4% figure represents the share of Console users affected, not the percentage of exposed keys or compromised providers. The company has also not said how many individual accounts that percentage represents.
What a Distillation Attack Means for API Security
A distillation attack involves querying an AI model extensively to collect outputs that can help train another model. Developers can use these responses to approximate aspects of a more capable model's behavior.
In this incident, OpenCode identified a large-scale distillation attack but has not explained which models the attackers targeted. It has also not disclosed the query volume, the duration of the activity, or the identity of those responsible.
Scale is what connects the technique to cost: producing enough outputs to approximate another model can require substantial query volume, and when that volume runs through credentials obtained without authorization, the resulting usage lands on the victim's account.
Stolen API keys can allow attackers to make requests using a victim's provider account. Depending on the provider's billing arrangements and account permissions, unauthorized requests can generate charges for the key's owner. This creates a direct financial risk for developers and businesses that store provider credentials in external applications. A compromised key may remain usable until its owner revokes it or the provider otherwise disables access.
What Affected Users Should Do
OpenCode instructed affected customers to revoke and replace exposed keys through their providers' dashboards. Users must also update any applications that rely on those credentials and review recent usage for suspicious activity. Rotating keys quickly can prevent further unauthorized requests using the compromised credentials.
Beyond immediate remediation, spending limits and usage alerts can help reduce potential losses, while secure credential storage can limit exposure.
The incident highlights the risks of linking external AI services to development platforms. Until OpenCode provides further findings, affected users should treat potentially exposed credentials as compromised and verify their provider usage for any unauthorized activity. The open questions — the technical mechanics of the distillation attack, the full scope of the attackers' access, and the outcome of OpenCode's work with OpenAI, Anthropic, and Google — are the details to watch as the investigation continues.
Source: Blockonomi
