OpenCode is one of the most-talked-about coding agents on X right now, with about 24,900 posts in our sample this week. The OpenCode Console breach was one of the big OpenCode stories: a Hacker News thread titled "OpenCode Hacked" hit 974 points on Oct 17.
Here's what's confirmed, what's only reported, and what to do if you're affected.
What OpenCode itself said
OpenCode's official statement is a post on X from Oct 17, 2026 (2:08 PM Toronto time):
"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"
That's the only first-party source. Everything below is reported by The Hacker News and BleepingComputer, both on Oct 19.
What was reported
What Console is. As reported by The Hacker News, Console is OpenCode's optional hosted service. A team saves its own OpenAI, Anthropic or Google key there, and Console calls the provider so team members can use the models without seeing the key.
What was exposed. THN says an intruder reached a "legacy system" on the night of Oct 16. It may have exposed those saved provider keys. OpenCode's wording is that keys "may have been exposed". It hasn't said any key was copied or used.
When. As reported by BleepingComputer, the email to affected users puts the earliest possible exposure at Oct 17, 2026, 00:30 UTC. That's 8:30 PM Toronto time on Oct 16. The email subject was "Action Required: Potential provider key breach".
What wasn't affected. THN reports that the OpenCode CLI and desktop apps store keys added on your machine in a local SQLite database. Co-founder Dax Raad wrote that the breach involves "the OpenCode Console, not OpenCode itself."
The damage. Both outlets cite user reports of unexpected charges, from a few hundred dollars up to about $1,700. BleepingComputer says some users had Google Cloud projects suspended for "abusive activity consistent with hijacked resources." It also says OpenCode's notice mentions the possibility of reimbursement. These are users' own accounts, not confirmed totals.
Still unknown. OpenCode hasn't said what the legacy system was, how it was reached, how many keys it held, or how many people 1.4% represents.
If you got the email: rotate your keys now
A provider key is a bearer credential. Whoever holds a copy can run billable requests until the provider revokes it. Deleting the key from Console doesn't revoke it, and a Console budget can't cap use that never goes through Console.
- Revoke the key at the provider. Do this in the OpenAI, Anthropic or Google dashboard, then create a new key.
- Replace it everywhere. Update every app, script, CI secret and
.envfile that used the old key. - Check usage and billing for requests you didn't make. Go back to at least Oct 16.
- Set a spend limit or alert at each provider.
- Give each tool its own key. If one leaks, it does less damage and is easier to trace.
- Write things down. Screenshot unexpected charges in case reimbursement is offered.
If you didn't get the email
OpenCode says you weren't affected. It's still a good week to tighten up:
- If you keep keys in any hosted dashboard, ask whether you need to. Local storage plus per-tool keys limits the blast radius.
- Check your agent's permissions while you're at it. Our guides on running coding agents safely and the LiteLLM supply-chain attack cover the same "assume a secret leaks" mindset.
- The vibe-coding security checklist has a key-hygiene section you can run in ten minutes.
Why "distillation" is in the story
Distillation means harvesting a strong model's answers at scale to train a rival model. Stolen keys let someone do that on another person's bill. OpenCode linked the breach to a "large scale distillation attack" but hasn't explained how the two connect. Until it publishes a fuller write-up, treat that as OpenCode's description, not an established finding.
If you use OpenCode with local models, your keys never leave your machine at all. Our OpenCode local LLM setup guide shows how.
