Skip to content
World clockEU--:--UK--:--USA--:--CN--:--PLDEFRIT中文EN

portal about AI and technologyevents · analysis · interviews · technical background

Search
LIVE
›

OpenCode says breach hit 1.4% of Console users

OpenCode said on 17 October that attackers breached a legacy system behind OpenCode Console, a hosted service where some users store API keys, affecting 1.4% of Console users, some of whom reported unauthorised charges.

AI & modelsAnalysisGrace OkonkwoPublished: 5 November 20264 min readSources 18
OpenCode says breach hit 1.4% of Console users

OpenCode, an open source AI coding agent, wrote on X: "We had a security breach last night related to a large-scale distillation attack that impacted 1.4% of OpenCode Console users. We have notified them all this morning via email." The company said users who did not receive an email were not impacted. Co-founder Dax Raad said the open source app and command-line tool were not affected. "Note this is the OpenCode Console, not OpenCode itself, those keys never come to us," he wrote on X.

OpenCode Console is the hosted platform where some users store API keys for services including OpenAI, Anthropic and Google. Affected accounts were a subset of Console users who had linked external providers, OpenCode said. CPO Magazine reported OpenCode has about 16 million active monthly users. The 1.4% figure applies to Console users, not that wider base. Console stores credentials for connected providers and injects them into requests forwarded through its gateway, CPO Magazine reported. That design means a stolen key can be used at the account holder's expense until the provider revokes it.

OpenCode has not disclosed how attackers gained access to the older system, how keys were stored, or the full extent of any misuse. It also has not given a total for fraudulent charges. It has not named the threat actor. It has not said how many Console users had saved API keys in the service or linked an external provider. The company said the incident remains ongoing and that it is working with Anthropic, OpenAI and Google.

What users reported

Developers began posting spending alerts and unauthorised charges on Reddit and X overnight. One wrote: "I saw my Open AI, Anthropic, and Google AI spend alerts all fire off before going to bed wondering what was going on." TechCrunch reported that charges ran into the hundreds of dollars on individual accounts, and a few users described totals above $1,000. In a Reddit thread cited by Notebookcheck, one user reported $400 in unauthorised charges on an Anthropic account, while another said Google usage charges reached around €200 and their project was suspended for excessive abuse. CPO Magazine reported one case of charges up to $1,700.

Anthropic and Google blocked the API keys they believed had been exposed, TechCrunch reported. OpenAI said it worked with OpenCode to restore access and refunded credits its API customers lost in the attack. Raad said OpenCode's own refunds for unauthorised charges were already underway.

Why the distillation label is disputed

The company's label, a large-scale distillation attack, is disputed. Distillation in this context means querying frontier models at volume and using the answers to train or improve another model at a fraction of the cost. Leaked API keys can help users in countries with restricted access to American models generate the high volume of outputs needed for that process, TechCrunch reported. Operators in those countries can also route requests through intermediary services known as LLM gateways or proxy networks to obscure who they are. Skeptics called the framing an overstretch and said use for distillation remains unproven. CPO Magazine noted that no concrete evidence currently shows the incident was a distillation attack.

What affected users should do

OpenCode told affected users to revoke and replace their provider keys, update applications that use them and review recent usage for unexpected activity. The company also advised reviewing usage and billing for unfamiliar requests dating back to 16 October and setting spending limits. Deleting a key inside Console does not end an attacker's access. Users have to revoke it in the provider's dashboard.

Comments 0

Sources

18
  1. 01Hackers hit AI coding tool OpenCode, running up charges on users' AI accountsEN
  2. 02OpenCode confirms breach as users report AI charges they never authorisedEN
  3. 03OpenCode AI Coding Tool Exposes API Keys in Suspected Distillation Attack, Triggering Unauthorized ChargesEN
  4. 04OpenCode Suffers Security Breach; Users Report Unauthorized AI ChargesEN
  5. 05AI coding tool OpenCode breached, unauthorized charges made with stored OpenAI, Anthropic, and Google API keysEN
  6. 06Google: LLMjacking attacks rack up $1 million in cloud AI chargesEN
  7. 07OpenCode Hacked: Stolen API Keys Spark Massive AI Billing FraudEN
  8. 08Pangram expands its AI detection tools to video and imagesEN
  9. 09OpenAI acquires Pierre Computer Company to make Git keep up with AI coding agentsEN
  10. 10STAT+: Sens. Wyden and Sanders, backers of ‘Medicare for All,’ set to take charge of key committeesEN
  11. 11Google will let schools skip AI tools, but they have to give up search, tooEN
  12. 12bp pulse makes 850+ EV fast chargers easier to use in the USEN
  13. 13 Creality K3 Review: It’s a Tool Changer, not a game changer EN
  14. 14Wheel-e Podcast: New Amflow, Trek e-bikes, ALSO runs out of charge, moreEN
  15. 15Uber Builds MCP Gateway to Govern Access to 800+ Servers and 5,000+ AI Agent ToolsEN
  16. 16DeepSeek unveils AI ‘super agent’ in coding race with OpenAI, AnthropicEN
  17. 17Launch HN: Momentic (YC W24) – Agents that catch bugs by using your appEN
  18. 18NVIDIA Cosmos Opens New Tools to Train, Evaluate and Deploy World ModelsEN

All figures and quotations in this text come from the sources listed below.

Content prepared by the editorial team with AI assistance.

Grace Okonkwo

Grace Okonkwo

AI, models and technology

Grace Okonkwo covers AI, models and technology for FLASH24, working from primary sources such as model cards, API documentation and benchmark papers rather than vendor summaries. She checks training data provenance, evaluation conditions and reported scores against the underlying datasets before any figure reaches print. She interviews researchers and engineers directly, tracks release calendars from major labs, and compares successive model versions on the same tests. Her own self-hosting, home-network and documentation-reading habits feed straight into that desk, since she tests tools on her own hardware first. She does not publish benchmark claims without a reproducible method.

Newsroom →

Comments

0
  1. No comments yet — be the first.

Write a comment

Comments are public. We do not publish abuse, spam or advertising.