Act nowSupply chain

OpenCode Console breach: if you saved AI provider keys there, revoke them at the provider

OpenCode said on 17 Oct 2026 that attackers reached AI provider keys stored by about 1.4% of its Console users, and some owners saw charges of up to 1,700 dollars. Here is what to revoke and check.

How urgent

Act now

Who is affected

People who linked OpenAI, Anthropic or Google API keys in an OpenCode Console account. OpenCode says about 1.4% of Console users were affected and that it emailed them

What to do

If you saved provider keys in OpenCode Console, revoke them on each provider's own dashboard (removing them in Console is not enough), create new ones, check your usage and billing, and set a spend limit

Published 28 Oct 2026 · Sources last checked 28 Oct 2026No. 18 / 87

What happened

On Saturday 17 October 2026 OpenCode, a popular open-source coding agent, announced a breach of its Console, the hosted service where users can store keys for other AI providers. According to BleepingComputer, which cites OpenCode's own statement and the email it sent to users, the earliest possible exposure of keys was 17 October at 00:30 UTC.

OpenCode says the incident affected about 1.4% of Console users, only those who had linked external providers. It calls it a "large-scale distillation attack". Distillation means copying how a model answers by sending it a huge number of queries, and it becomes an attack when it is done with accounts or keys that are not yours. Co-founder Dax Raad said the attackers had been going after the systems for at least 48 hours using AI agents.

What was exposed

The stored API keys for external AI providers. BleepingComputer names Anthropic, OpenAI and Google. According to the email OpenCode sent, no data other than the keys appears to have been exposed.

What users reported

Some users reported charges on their AI accounts from several hundred dollars to more than 1,700 dollars overnight, and some said Google suspended their projects for activity consistent with hijacked resources. OpenCode's message mentions possible reimbursement. OpenCode says it is working with Google, OpenAI and Anthropic.

Who is affected

Only people who linked provider keys in an OpenCode Console account. OpenCode says it emailed every affected user. If you never used Console, or you never saved a provider key there, this story does not apply to you.

Why it matters if you build with AI

This is the same lesson as Railway and LiteLLM this month: a key stored in someone else's platform is only as safe as that platform. An AI provider key is also money. Whoever has it can run up your bill, and they do it without touching your app.

What to do

  1. Revoke the keys at the provider, not in Console. Open the OpenAI, Anthropic or Google dashboard and delete or rotate every key you saved in OpenCode. Removing a key from Console leaves the old key working.
  2. Create new keys and use them only where needed. Give each tool its own key, so you can cut one off without breaking the rest. This is our advice, not OpenCode's.
  3. Check your usage and billing. Look for activity you do not recognise from 16 October on, and report charges to the provider.
  4. Set a spend limit on every provider account. A cap turns a stolen key from a large bill into a small one. This is also our advice.
  5. Look for the same key elsewhere. If you pasted it in a repository, a chat or a document, revoke it too.

What we could not confirm

We read BleepingComputer's report, which quotes OpenCode's statement. We could not open OpenCode's own post and have not read the email it sent. OpenCode has not published how the attackers got in, who they are or how many users were affected, and we have not verified the charges users reported. We are publishing this later than the incident because the lesson links to the other stories this month, and the steps above still apply.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks