# OpenCode Console breach may have exposed users' saved AI provider keys

Source: https://startwithidentity.com/blog/2026-10-17-opencode-console-breach-may-have-exposed-users-ai-provider-keys/
Last updated: 2026-10-17
License: content by Start with Identity. Cite the source URL.

---

OpenCode, maker of an AI coding agent, told users on October 17 that an intruder reached a legacy system the night before and may have exposed third-party AI provider keys (OpenAI, Anthropic or Google) saved in OpenCode Console, its optional hosted service. It emailed the 1.4% of Console users with an outside provider linked; users who got no email were not affected, it said. Keys kept by the OpenCode command-line and desktop apps in a local SQLite database "never come to us," co-founder Dax Raad wrote. OpenCode has not said how the intruder got in, what the legacy system was, or whether any key was used. Users have publicly reported unexplained provider charges, one of $1,700, according to The Hacker News; OpenCode has not confirmed them.

## Why it matters

A provider [API key](https://startwithidentity.com/glossary/api-key/) is a bearer credential with a billing account attached. Stolen AI keys are resold or burned for model access, the pattern called [LLMjacking](https://startwithidentity.com/glossary/llmjacking/), and the bill is how most victims find out. Any hosted tool that stores your keys to call models on your behalf is holding a secret it can leak.

If you were notified, revoke the key in the provider's dashboard (deleting it in Console does not revoke it), issue a new one, and update every script that used it. Review provider usage back to October 16. Give each tool its own key with a spend cap or alert, so one breach has a known blast radius. Where a provider supports short-lived or scoped credentials, prefer them over a long-lived key pasted into a third-party service.

Source: [OpenCode on X](https://x.com/opencode/status/2111519637049319818)