Overview
- Attackers reached a legacy OpenCode Console system on the night of October 16, and OpenCode emailed affected users on October 17, saying 1.4% of Console accounts may have had external provider keys exposed.
- Users reported unexpected spend alerts and unauthorized charges to OpenAI, Anthropic and Google accounts, with some losses reported in the hundreds to about $1,700 and some Google projects suspended.
- Anthropic and Google blocked keys they believed were exposed and OpenAI worked with OpenCode to restore access and refund affected API customers, while OpenCode says reimbursements are underway and the probe remains active.
- OpenCode said the compromise was limited to the hosted Console and did not affect keys stored locally in its CLI and desktop apps, highlighting the security tradeoff between server‑side convenience and local custody.
- Security firms and responders advise revoking and rotating any keys saved to Console, creating per‑project restricted keys with spend limits, reviewing provider billing from October 16 onward, and auditing where credentials are stored.