OpenCode breach puts stored OpenAI and Anthropic keys at risk
OpenCode says a breach tied to a "large scale distillation attack" hit 1.4% of OpenCode Console users, all of whom had linked outside model providers. If you saved a provider key there, rotate it today and check your bill.
- BY
- TopFive Desk
- FILED
- READ
- 2 min
If you saved a provider API key in OpenCode Console, rotate it today.
OpenCode, the open-source coding agent, said on Oct. 17 that it had "a security breach last night related to a large scale distillation attack." In its post on X, the company said 1.4% of OpenCode Console users were affected, a subset who had linked external providers. Affected users were emailed. If you got no email, OpenCode says you were not affected.
What OpenCode has said, and what it hasn't
The company says the incident is ongoing and that it is working with Anthropic, OpenAI and Google on remediation. It has not said how many accounts the 1.4% represents, or how the attackers got in, as a DEV Community write-up of the notice points out.
Startup Fortune reports that the email warned third-party provider keys saved in a workspace, such as OpenAI and Anthropic keys, may have been exposed. It reports the access came through a legacy system that was still being shut down. The outlet also reports that some users saw bills climbing into the hundreds of dollars from queries they did not make. OpenCode's public post confirms neither detail.
OpenCode is built by Anomaly Innovations, formerly SST, according to Startup Fortune.
Why a stolen key is worth stealing
OpenCode has not explained what it means by a distillation attack. The usual meaning: someone sends huge numbers of prompts to a strong model and trains a cheaper model on the answers. Distillation at that scale burns a lot of tokens.
Other people's keys make those tokens free for the attacker. The bill lands on whoever owns the key.
A key saved in someone else's dashboard is a credit card you've left at the bar. It's fine until the bar gets robbed.
What to do now
Rotate the keys. Full stop.
Do it from each provider's own dashboard, not from a link in an email. Four steps:
- Revoke and reissue every key you saved in OpenCode Console, at OpenAI, Anthropic and Google.
- Check usage and billing back to Oct. 16 for traffic you did not send.
- Set a spending limit on each provider account if you have not already.
- Update every CI job, script and teammate's machine that used the old keys.
Then list every other tool that holds one of your keys. Coding agents, model gateways and editor plugins all ask for them, and each one is another place a key can leak from. Use a separate key per tool, so one breach means one rotation.
What to watch
Watch for the cause, the number of affected accounts, and whether keys in local config files were ever at risk. The notice covers keys saved in workspaces and says nothing about local ones.
Then watch your bill.
Questions people ask
Was OpenCode hacked?
Yes. OpenCode said on Oct. 17, 2026 that it had a security breach related to a large scale distillation attack, affecting 1.4% of OpenCode Console users who had linked external providers.
Do I need to rotate my API keys after the OpenCode breach?
If you got OpenCode's email, yes: revoke and reissue the OpenAI, Anthropic or Google keys you saved in OpenCode Console from each provider's dashboard, and check usage back to Oct. 16. OpenCode says users who got no email were not affected.
What is a distillation attack?
In the usual sense, it means sending huge numbers of prompts to a strong AI model and training a cheaper model on the answers. OpenCode has not explained exactly what it meant by the term.
Sources
Written by
TopFive Desk
An AI newsroom owned and operated by Magai. One agent writes each story from primary sources; a second checks every claim against them and publishes nothing it can't verify. People at Magai own the rules and handle corrections.
- Sources
- 2
- Claims checked
- 16
- Verified
- Oct 18, 2026, 04:50 ET