OpenCode breach leaks stored provider API keys
Partly confirmed
The takeaway
On Oct 17, 2026 OpenCode (made by Anomaly Innovations) said a breach “related to a large scale distillation attack” hit about 1.4% of OpenCode Console users: those who had linked external providers, whose stored OpenAI, Anthropic and Google API keys were exposed.
Status
- Claim
Partly confirmed
- Our reporting
- Medium confidence
- Importance
- 3 of 5
- Last verified
- 20 October 2026
Your AI and this story
- GPT-6 Astra170 days after its cutoff
- Claude Opus 5.5109 days after its cutoff
- Gemini 4 Argon200 days after its cutoff
- Grok 4.7139 days after its cutoff
None of these four assistants can know about it. The closest, Claude Opus 5.5, stops 109 days before it.
Key facts
- OpenCode on X (Oct 17, 18:08 UTC, ~903k views): breach from ‘a large scale distillation attack that impacted 1.4% of OpenCode Console users’; affected users emailed; only users with linked external providers affected; incident ‘ongoing’; working with Anthropic, OpenAI and Google
- Exposed: OpenAI, Anthropic and Google API keys saved in users’ Console workspaces, from a ‘legacy system’ being shut down (per the company notice as reported by Startup Fortune)
- Company: no evidence ‘to date’ that other data leaked; cannot confirm whether keys were used maliciously; advises revoking and reissuing keys in each provider’s dashboard, checking usage from Oct 17 and setting spending limits
- Anthropic’s Lydia Hallie (Claude Code team, Oct 17): Anthropic worked with OpenCode and ‘revoked Claude API keys we believe were affected’
- Unverified user reports on X: unauthorized charges ‘in the hundreds of dollars’, a suspended Google Cloud project, an OpenAI account deleted for terms violations
- Open questions: how attackers got in, how many accounts 1.4% is, and why it is called a distillation attack (commentators incl. Nathan Lambert asked whether it means stolen keys used to harvest model outputs)
- User report (Max Weinbach, X, Oct 17 18:01 UTC, ~105k views): ‘My OpenAI and Anthropic balances got drained, Google account got limited and drained a bit and OpenCode did email me’ — first public account of affected keys being used to spend users’ credits
- Day 2 (Oct 18): OpenCode developer Dax (@thdxr, profile: ‘building @opencode at @anomalyco’): ‘they’ve been non stop trying to attack our systems for the past 48 hours … we basically need agents going 24/7 because that’s what they have’ (~818k views); mid-incident the frontier models used for defense ‘did quite a bit and then started refusing’, fixed once OpenCode ‘got access to daybreak blue’ (~208k views; OpenAI’s Daybreak trusted cyber-defense program)
Show 2 more
- Reaction: Andrew Curran: like Hugging Face earlier, OpenCode’s defensive models began refusing because analysing the attacks triggered safety guardrails (~242k views); Zvi Mowshowitz noted the same fix as Hugging Face, joining the labs’ cyber-defense programs; Dean Ball called it ‘a fairly modest hindrance’ quickly resolved through a trusted access program
- TechCrunch (Oct 19): attackers broke into ‘an older system’; users reported charges in the hundreds of dollars and a few totals above $1,000; Anthropic and Google blocked keys they believed exposed, while OpenAI said it worked with OpenCode to restore access; some skeptics called the ‘distillation attack’ framing an overstretch for a plain breach; TechCrunch frames it as a sign that companies without vetted access to less-restricted models struggle to defend against large-scale AI-driven attacks
What happened
OpenCode, the open-source coding agent built by Anomaly Innovations, emailed affected users on Oct 17 and posted on X that a breach tied to “a large scale distillation attack” had hit about 1.4% of OpenCode Console users. Only users who had linked external model providers were affected; their stored provider API keys (OpenAI, Anthropic, Google) were exposed. The company said the incident was ongoing and that it was working with the three labs. Anthropic’s Lydia Hallie said Anthropic had revoked the Claude API keys it believed were affected. Startup Fortune reported that the keys came from a legacy system being shut down and that some users reported unauthorized charges; those reports are unverified.
The company did not explain the “distillation” label. A plausible reading, not confirmed by OpenCode, is that the attackers wanted other people’s keys to pull large volumes of frontier-model outputs for training their own models while hiding behind many accounts.
Why it matters
Labs have described distillation campaigns run through fake or resold accounts (see Anthropic’s reports). This incident points to a different supply route: stolen keys from third-party agent tools, where users pay the bill. It also shows the risk of storing frontier API keys in hosted consoles of agent tools.
Sources
10 sources from 3 sites. Numbers match the chips in the text.
10 sources: 1 primary, 2 press, 7 reactions
Primary
- OpenCode on X: breach notice (Oct 17)x.com, official
Press
- Startup Fortune: OpenCode breach exposes stored OpenAI and Anthropic keys, prompts urgent key rotationstartupfortune.com, press
- TechCrunch: Hackers hit AI coding tool OpenCode, running up charges on users’ AI accountstechcrunch.com, press
Reactions
- Lydia Hallie (Anthropic) on X: Claude API keys revokedx.com, discussion
- Max Weinbach on X: OpenAI and Anthropic balances drained (Oct 17)x.com, discussion
- Nathan Lambert on X: why is a key-stealing attack called ‘distillation’? (Oct 17)x.com, discussion
- Dax (@thdxr, OpenCode) on X: 48 hours of non-stop attacks (Oct 18)x.com, discussion
- Dax (@thdxr) on X: models started refusing mid-incident; Daybreak access fixed it (Oct 18)x.com, discussion
- Andrew Curran on X: defensive models refused, as at Hugging Face (Oct 18)x.com, discussion
- Dean Ball on X: a modest hindrance resolved by trusted access (Oct 18)x.com, discussion
Changes
- TechCrunch follow-up: >$1,000 charges for some users, provider responses, skepticism of the distillation framing
- Added video(s) code-bear-opencode-got-hacked-badly, david-ondrej-opencode-hack-is-insane
- Second day: sustained attacks, defensive models refusing until OpenAI Daybreak access (@thdxr, 818k views), reactions by Curran, Zvi, Dean Ball
- Added Max Weinbach’s drained-balances report (~105k views) and Nathan Lambert’s post
- Filed (OpenCode and Hallie posts read via fxtwitter; Startup Fortune)