Threat Intelligence

OpenCode Console Breach Puts Saved AI Provider Keys at Risk

The Hacker News · 19 Oct 2026
Key Takeaway If you store AI provider keys in any third-party service, revoke and replace them at the provider immediately after a breach notice, since deleting them from the service does not stop them working.

OpenCode says an intruder reached a legacy system on the night of October 16 and may have exposed third-party AI provider keys that users saved in OpenCode Console, its optional hosted service. About 1.4% of Console users are affected, all of whom had an outside provider linked. OpenCode emailed them on the morning of October 17 with the subject line "Action Required: Potential provider key breach", and said anyone who did not receive it was not affected.

Co-founder Dax Raad said the breach involves the Console, not OpenCode itself, and that keys added in the command-line and desktop apps "never come to us". A provider key works like a password that anyone holding a copy can use to run billable requests on the owner's account until the provider revokes it. Deleting the key from Console does not revoke it, and a Console budget cannot cap misuse, because Console only sees requests that pass through its own gateway. Affected users are told to revoke and replace keys with each provider.

Some users say they have already been charged for usage they did not run. One reported $281 on OpenAI and $168 on Anthropic, another put losses at $1,700, and Reddit users claimed about $400 on Anthropic and around €200 on Google. These are the users' own accounts. OpenCode says the keys "may have been exposed" and has not said any key was copied or used.

API keys AI security Data breach OpenCode Credential management
Building or buying AI systems? Governing them under ISO 42001 ->

Summarised by CISO AI from The Hacker News, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.