OpenCode Console breach may have exposed third-party AI API keys
First merged summary.
OpenCode says a legacy Console system was breached and may have exposed API keys for 1.4% of Console users; the incident is ongoing.
OpenCode said an intruder reached a legacy system being decommissioned on the night of October 16 and may have exposed OpenAI, Anthropic, and Google API keys stored in OpenCode Console, an optional hosted workspace proxy. The company emailed affected users on October 17, said they are 1.4% of Console users who had linked an external provider, and told others they were not impacted. It called the incident an ongoing large-scale distillation attack; TechCrunch reports skeptics dispute that description. Local command-line and desktop keys were not involved, and contributor Dax Raad said the OpenCode product itself was not affected. Users reported unauthorized charges, while GBHackers notes the company’s public statement has not confirmed that keys were copied or that losses occurred.
- Affected group is 1.4% of Console users with linked providers; absolute count undisclosed.
- Deleting a Console key does not revoke it at the provider.
- Users reported charges including $1,700, $400, $281, $168, and about €200.
- Anthropic and Google blocked keys; OpenAI refunded attack-related API credits, TechCrunch reports.
- Google suspended some projects after abusive activity on hijacked resources.
- OpenCode has not explained the access path or when access began.
Timeline
dated events in the reporting · oldest first- Oct 16, 2026Unauthorized access reached a legacy OpenCode system overnight. · The Hacker News
- Oct 17, 2026OpenCode emailed affected Console users and announced the breach. · Infosecurity Magazine
- Oct 17, 2026Emails set earliest possible key exposure at 00:30 UTC. · BleepingComputer
What each outlet adds
beyond the shared facts- The Hacker NewsNamed user charges and that Console deletion does not revoke provider keys.
- BleepingComputer48-hour activity window, Google suspensions, and Daybreak defense claim.
- TechCrunchSkeptics dispute distillation claim; provider blocks and OpenAI refunds.
- GBHackersPublic statement does not confirm stolen keys or financial losses.
- Infosecurity MagazineSafeguard published rotate-and-revoke steps; Raad said the product was unaffected.
- Products
- OpenCodeOpenCode Console
Coverage
oldest first · one row per article · UTC- · 6d ago
The Hacker NewsFirst report
OpenCode Console breach may have exposed OpenAI, Anthropic and Google keys
OpenCode emailed 1.4% of Console users on October 17 to revoke provider keys; local app keys were not involved.
- · 6d ago
Infosecurity Magazine
OpenCode Console breach may have exposed provider API keys
OpenCode says 1.4% of Console users with linked external providers were affected; the OpenCode product itself was not.
- · 6d ago
BleepingComputer
OpenCode breach exposes API keys for 1.4% of Console users
Some linked-provider users report overnight charges up to $1,700 and Google Cloud project suspensions.
- · 6d ago
TechCrunch · AI
Attackers breach OpenCode Console and charge users’ AI API keys
About 1.4% of Console users had stored API keys exposed; the open-source app itself was not affected.
- · 5d ago
GBHackers
OpenCode says breach hit 1.4% of Console users
The company ties the October 17 incident to a distillation attack on users with external providers, but has not confirmed stolen API keys.
- · 5d ago
OpenCode 1.0.137–1.18.32 RCE silently fixed in 1.18.33
Pillar Security says a malicious MCP server can run code on Windows during OAuth, and scanners will not flag the flaw.
- · 3d ago
OpenCode MCP sign-in flaw executes code on Windows and WSL
Builds 1.0.137 through 1.18.32 are affected; Anomaly fixed it in 1.18.33 without a CVE or advisory.