← All incidents

OpenCode confirms a breach and tells affected Console users that AI provider keys saved in their workspaces may have been exposed

Incident · OpenCode Console / cloud workspaces (saved third-party AI provider keys) · HIGH

Summary

OpenCode, the open-source AI coding agent made by Anomaly, said on X on Oct 17, 2026 that it "had a security breach last night related to a large scale distillation attack that impacted 1.4% of OpenCode Console users", and that it had notified all of them by email that morning. It added that users who did not get an email were not affected, and that those affected were a subset of users with external providers. The email, which recipients shared publicly under the subject "Action Required: Potential provider key breach", says OpenCode identified unauthorized access to a legacy system it was in the process of decommissioning, and that third-party provider keys saved in a user's workspace (it names OpenAI and Anthropic as examples) may have been exposed. It asks users to revoke and replace those keys at each provider, update any apps that use them and review recent usage. Some users reported unexpected spend on provider keys they say were stored only in their OpenCode account. Those reports are self-reported and we have not verified them. OpenCode said in its first post that the incident is ongoing. It has not said how the attacker got in, how many keys were involved, or how the breach relates to what it calls a distillation attack.

Severity

Timeline

1. Oct 16–17, 2026 (overnight)
   OpenCode says the breach happened "last night", per its Oct 17 post on X.
2. Oct 17, 2026, early morning ET
   Users on r/opencode and X begin reporting unexpected usage on AI provider keys. Some say the keys were saved only in their OpenCode account (self-reported).
3. Oct 17, 2026, morning
   OpenCode emails affected users under the subject "Action Required: Potential provider key breach" (per recipients' screenshots). A screenshot of the email is posted to r/opencode at 10:14 a.m. ET and reshared on X.
4. Oct 17, 2026, 1:56 p.m. ET
   OpenCode posts on X that it had a security breach affecting 1.4% of OpenCode Console users, related to what it calls a large scale distillation attack, and that the incident is ongoing.
5. Oct 17, 2026, 2:08 p.m. ET
   An edited version of the post adds that users who did not get an email were not affected.
6. Oct 17, 2026, about 3 p.m. ET
   OpenCode's status page lists no security incident, and Anomaly has not published a GitHub security advisory or blog post about the breach.

How it happened

Most of what is known comes from OpenCode's email, as recipients shared it, and its post on X. The email says OpenCode identified unauthorized access to a legacy system that it was in the process of decommissioning, and that third-party provider keys saved in a user's workspace may have been exposed. OpenCode itself runs on your machine and normally keeps provider keys there. The breach concerns keys that users chose to save in their workspace on OpenCode's Console, its hosted service. On X, OpenCode linked the breach to "a large scale distillation attack" but has not explained how that connects to the access to the legacy system. It also has not said how the access happened, when it was detected, how many keys were involved, whether the keys were encrypted at rest, or whether anything besides provider keys was in that system. We won't guess at those details, and we will update this entry if OpenCode publishes them.

How to check your app

• If you ever saved an OpenAI, Anthropic, Google, OpenRouter or other provider key in an OpenCode workspace, revoke it in that provider's dashboard and create a new one, even if you see no unusual activity and got no email.
• OpenCode says users who did not get its email were not affected. Check the inbox tied to your OpenCode account, including spam, for "Action Required: Potential provider key breach".
• Review usage per key at each provider (OpenAI, Anthropic Console, Google Cloud or AI Studio, OpenRouter and others) for the past several days, especially overnight Oct 16–17, 2026, and note anything you didn't run. Most providers show usage by key or project.
• If you see charges you didn't make, contact the provider's billing support with the key ID, the dates and the fact that OpenCode notified you of a possible exposure.
• Set monthly spend limits or budget alerts at each provider, turn off auto-reload where you don't need it, and use a separate key per tool so one leak can be revoked without breaking everything else.
• Update any apps, CI jobs or scripts that used the old key so they don't fail silently after you revoke it.

Sources

• OpenCode on X: breach statement (Oct 17, 2026, edited version)
• OpenCode on X: first version of the statement (Oct 17, 2026)
• r/opencode post sharing a screenshot of OpenCode's email (Oct 17, 2026)
• X post resharing the email screenshot, with reports of unexpected charges (Oct 17, 2026)
• X post by a recipient saying they got OpenCode's email (Oct 17, 2026)
• X post by another recipient describing the email and checking their provider dashboards (Oct 17, 2026)
• OpenCode status page

Corrections and updates

None. Re-checked against every source on Oct 17, 2026.