OpenCode Console breach exposes users' saved OpenAI / Anthropic / Google API keys
› OpenCode Console (hosted service by Anomaly)
Get an email when a new major security incident drops. No spam, unsubscribe any time.
- started
- Oct 17, 2026
- closed
- ongoing
- CVEs
- none
- sources
- 6
## summary
On the night of Oct 16 2026 an intruder reached a legacy OpenCode Console system that was being decommissioned and may have exposed third-party AI provider keys saved in Console workspaces. OpenCode says 1.4% of Console users (those with external providers linked) were affected and tied it to a large-scale distillation attack. Users reported unauthorized charges up to ~$1,700 and some Google Cloud project suspensions. Anthropic and Google revoked/blocked exposed keys; OpenAI refunded drawn credits. The OpenCode app itself (local keys) was not affected.
severity: Credential exposure with confirmed abuse (unauthorized API charges); no CVE - platform incident
## affected
- OpenCode Console workspaces with saved OpenAI, Anthropic or Google provider keys (~1.4% of Console users; affected users were emailed)
## fixed in
no fixed release yet
## timeline[6]
Anthropic credit restoration still in progress; OpenCode says it will cover them itself if not done this week.
sourceBleepingComputer and The Hacker News report unauthorized charges up to ~$1,700 and Google Cloud project suspensions; OpenAI says it refunded affected credits.
sourceDax says attackers have been 'non stop' attacking OpenCode's systems for 48 hours; systems being hardened.
sourceEarliest possible exposure of saved provider keys (per OpenCode's email to affected users).
sourceOpenCode emails affected users, then announces the breach on X, tied to a 'large scale distillation attack' affecting 1.4% of Console users.
sourceDax (OpenCode) clarifies only the hosted Console is affected; keys used locally with the OpenCode app never reach OpenCode. Anthropic and Google revoke/block exposed keys; refunds start.
source
## news & write-ups[3]
## posts[3]
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
@lydiahallie note this is the OpenCode Console, not OpenCode itself, those keys never come to us
they've been non stop trying to attack our systems for the past 48 hours a side effect is everything is getting hardened but damn we basically need agents going 24/7 because that's what they have
## notes & caveats
No official OpenCode blog post found; facts come from OpenCode/Dax posts on X plus THN/BleepingComputer (which quote OpenCode's email). How the legacy system was accessed is undisclosed. Kept live/partial: OpenCode called it ongoing, and refunds and provider-side revocation were still in progress on Oct 20. OpenCode's own tweet text may be truncated by the API at 'external providers'.
