OpenCode breach reveals exposed API keys in AI distillation attacks

What happened with OpenCode

OpenCode, a popular open source project that assists developers in generating code snippets, recently disclosed a security incident that affected a small subset of its users. The project team sent alerts indicating that API keys entered into the platform were unintentionally logged and made accessible to unauthorized parties. The breach was traced to a flaw in the way the service handled external provider credentials during a process known as AI distillation.

How the breach unfolded

Distillation attacks and key leakage

Distillation attacks involve extracting knowledge from a large model by repeatedly querying it and analyzing the responses. In OpenCode's case, the platform forwarded user‑provided API keys to third‑party services as part of the code generation workflow. A misconfiguration caused those keys to be written to a temporary storage file that lacked proper access controls. When attackers executed a series of automated queries, they were able to retrieve the stored credentials.

Scope of affected users

The OpenCode team estimates that fewer than one percent of active users were impacted. Most of the affected accounts belonged to developers who integrated the platform with cloud providers for functions such as code compilation, testing, or deployment. No evidence suggests that the leaked keys were used to compromise additional systems, but the potential for abuse remains high.

Implications for developers and organizations

• Immediate exposure of cloud resources can lead to unauthorized compute usage and inflated bills.
• Compromised keys may allow attackers to read or modify stored data, depending on the permissions granted.
• Supply chain trust is weakened when widely used tools mishandle credentials.
• Regulatory frameworks such as the NIST Cybersecurity Framework stress the importance of protecting authentication material.
• Incident response processes must include rapid rotation of affected keys and thorough audit logs.

Best practices to protect API keys

1. Store keys in a dedicated secret manager rather than embedding them in code or configuration files.
2. Apply the principle of least privilege, granting only the permissions required for a specific task.
3. Enable multi‑factor authentication for accounts that can generate or view keys.
4. Rotate credentials regularly and after any suspected compromise.
5. Monitor usage patterns for anomalies using tools such as the US‑CERT alerts.
6. Audit third‑party integrations to ensure they follow secure handling guidelines.

Response from OpenCode and the community

OpenCode issued a public statement acknowledging the breach and apologizing to users. The team has patched the storage flaw, disabled the vulnerable logging pathway, and released a new version of the software that enforces stricter credential isolation. In addition, they provided a step‑by‑step guide for affected developers to revoke and regenerate their API keys.

Community members have responded with a mix of concern and constructive feedback. Several contributors have submitted pull requests that add encryption for temporary files and improve documentation around secret handling. The incident has also sparked broader discussions on the responsibility of open source maintainers to implement secure defaults.

Looking ahead: strengthening supply chain security

The OpenCode breach highlights a growing challenge in the software supply chain: ensuring that tools designed to accelerate development do not become vectors for credential leakage. Experts recommend adopting a “zero trust” mindset for every integration point, treating even trusted services as potentially compromised until proven otherwise.

Organizations can benefit from frameworks such as the Microsoft Security Blog, which offers guidance on securing development pipelines. Regular third‑party risk assessments, combined with automated scanning for secret exposure in repositories, are becoming essential components of a robust security posture.

As the ecosystem evolves, developers are urged to stay vigilant, keep their tools up to date, and treat API keys as high‑value assets that require the same level of protection as any other sensitive data.