AI News · The messy stuff ·

OpenCode breach exposes stored API keys and runs up charges on AI accounts

Open-source AI coding agent OpenCode said attackers broke into an older system, affecting 1.4% of users of its OpenCode Console platform, where some users store API keys. Developers reported unauthorized charges on OpenAI, Anthropic and Google accounts, some above $1,000. OpenCode said refunds are underway and the incident is ongoing.

Key points

  • The breach affected 1.4% of OpenCode Console users, where some API keys were stored.
  • Some users reported unauthorized AI charges of more than $1,000.
  • OpenCode has not disclosed how attackers got in or how keys were stored.

What happened: OpenCode, an open-source AI coding agent that competes with Claude Code and Cursor, said attackers broke into an older system overnight, TechCrunch reported. The incident affected 1.4% of users of OpenCode Console, the company's online platform where some users store API keys for AI model providers. The company wrote on X that the breach was "related to a large-scale distillation attack," though it did not say how the attack happened.

Who it affects: Developers reported spending alerts and unauthorized charges across OpenAI, Anthropic and Google accounts. Some charges reached hundreds of dollars and a few totaled more than $1,000. Anthropic and Google blocked the exposed keys, and OpenAI said it worked with OpenCode to restore access and refund API customers for credits used in the attack. Co-founder Dax Raad said the open-source app and command-line tool were not affected.

The details: OpenCode said AI models it used to analyze the attack stopped working when the malicious code triggered safety filters. It later gained access to OpenAI's Daybreak Blue program, which gives vetted users models that are less likely to refuse defensive security work.

What to watch: OpenCode has not explained how attackers got in, how keys were stored or the full extent of misuse. It has told affected users to revoke and replace their keys with each provider and said refunds are underway.

Our take

Storing model provider API keys in third-party tools creates real financial exposure, so teams should scope keys, set spending limits and rotate them quickly.

Sources