> ## Content Index
> Fetch the complete content index at: https://digirolla.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# OpenCode Console Breach May Have Exposed Users' AI Keys, and Some Are Reporting Surprise Bills
- URL: https://digirolla.com/opencode-console-breach-may-have-exposed-users-ai-keys-and-some-are-reporting-surprise-bills/
- Published: 2026-10-20T07:14:06.000Z
- Updated: 2026-10-20T07:14:06.000Z
- Description: AI coding agent OpenCode says an intruder reached a legacy system and may have exposed the OpenAI, Anthropic and Google API keys saved by 1.4% of OpenCode Console users. Some users report hundreds of dollars in charges they didn't make.
- Author: Digirolla
- Tags: Apps

OpenCode, the open-source AI coding agent, says a breach of one of its older systems may have exposed the AI provider keys that some users had saved in its hosted service, and some of those users say the keys were used to run up charges on their accounts.

## What happened

OpenCode said on X on Saturday, October 17: "We had a security breach last night related to a large-scale distillation attack that impacted 1.4% of OpenCode Console users." It said all affected users were notified by email that morning, and that anyone who didn't get an email was not affected.

According to BleepingComputer, the email says the earliest possible exposure of users' keys was at **00:30 UTC on October 17**, or **5:30 PM PT on October 16**. The Hacker News reports the email went out under the subject line "Action Required: Potential provider key breach."

## Who is affected

Only **OpenCode Console** is involved. Console is OpenCode's optional hosted service: a workspace can save its own OpenAI, Anthropic or Google key there so team members can use those models without seeing the key. The affected users are Console users who had an outside provider linked.

The open-source app and command-line tool were not affected, according to co-founder Dax Raad. "Note this is the OpenCode Console, not OpenCode itself, those keys never come to us," he wrote on X. The Hacker News notes that keys added in the command-line and desktop apps are stored locally on the user's machine.

## Surprise charges

After the breach, developers posted spending alerts and unauthorized charges on Reddit and X, TechCrunch reports. Users described charges in the hundreds of dollars on individual accounts, and a few reported totals above $1,000\. One user reported losses of $1,700, according to BleepingComputer and The Hacker News. BleepingComputer also reports that some users said Google suspended their cloud projects after detecting "abusive activity consistent with hijacked resources."

According to TechCrunch, Anthropic and Google blocked the API keys they believed were exposed, and OpenAI said it worked with OpenCode to restore access and refund its API customers for credits used in the attack. OpenCode says refunds for unauthorized charges are underway.

## A defense slowed by guardrails

Raad said attackers had been trying to break into OpenCode's systems nonstop for 48 hours. He said AI models the team used for analysis helped for a while but began refusing to work when the malicious code they were asked to examine tripped safety filters. TechCrunch reports OpenCode later got access to OpenAI's Daybreak Blue program, which gives vetted users models that are less likely to refuse defensive security work, and Raad said that improved the team's investigation.

OpenCode has not said how attackers reached the older system, how keys were stored, how many keys were involved, or how the breach connects to the distillation attack it described. The company says the incident is ongoing.

## What affected users should do

Based on OpenCode's email and the providers' own guidance, as summarized by The Hacker News:

- Revoke the key in each provider's dashboard and create a new one. Deleting it from Console does not revoke it.
- Update every app and script that used the old key.
- Review provider usage and billing for requests you didn't make, going back to at least October 16.
- Set spend limits or alerts with each provider, and give each tool its own key.

## Sources

- [TechCrunch: Hackers hit AI coding tool OpenCode, running up charges on users' AI accounts](https://techcrunch.com/2026/10/19/hackers-hit-ai-coding-tool-opencode-running-up-charges-on-users-ai-accounts/?ref=digirolla.com)
- [BleepingComputer: OpenCode hack exposes API keys amid AI distillation attacks](https://www.bleepingcomputer.com/news/security/opencode-hack-exposes-api-keys-amid-ai-distillation-attacks/?ref=digirolla.com)
- [The Hacker News: OpenCode Console Breach May Have Exposed OpenAI, Anthropic, and Google API Keys](https://thehackernews.com/2026/10/opencode-console-breach-may-have.html?ref=digirolla.com)