If you have ever saved a provider API key in an OpenCode workspace, revoke and reissue it today. Anomaly Innovations, the company formerly known as SST that builds OpenCode, started emailing affected users at around 22:51 UTC on 17 October with the subject line "Action Required: Potential provider key breach." A second email followed just before 01:00 UTC on 18 October.
The intrusion came through a legacy console system the company was in the process of shutting down. Third-party provider keys saved in user workspaces — for OpenAI, Anthropic and Google — may have been exposed.
The timeline is the uncomfortable part
The earliest exposure the company could identify was approximately 00:30 UTC on 17 October. The first notification went out about 22 hours later. Twenty-two hours is a long time to hold a live API key that someone else may already have.
The detailed hour-by-hour reconstruction came from a developer posting as zephel01, not from the company. At the time of writing, OpenCode's status page, changelog and website carried no advisory at all — the only notice went by email, to accounts the company had already identified as affected. If you were not on that list, you were not told.
The company says it cannot confirm whether any keys were misused, and that its investigation to date found no evidence other data leaked. Two users have said otherwise: one reported unauthorised Claude API usage on the evening of 17 October, another roughly $100 in fraudulent charges.
What to do, in order
- Revoke and reissue every affected key in the OpenAI, Anthropic and Google dashboards directly. Do not use links in the email.
- Read your billing and usage logs back to 17 October. Unauthorised use shows up there before it shows up on an invoice.
- Set spending limits on each provider account. If you had them already, this cost you $100 instead of $10,000.
- Update every pipeline, CI job and local config that used the old keys, or you will be debugging 401s for a week.
The broader point: a coding agent that stores your provider keys is a credential store, whether or not it is marketed as one. This is the second credential-handling failure in the agent tooling space this month, after the Archon control API shipped with no authentication at all.
Sources: Startup Fortune