Hackers Breach AI Coding Tool OpenCode, Rack Up AI Charges

A breach at AI coding tool OpenCode exposed stored API keys for about 1.4% of OpenCode Console users, leading to unauthorized charges on OpenAI, Anthropic and Google AI accounts.

Hackers Breach AI Coding Tool OpenCode, Rack Up AI Charges: key figures
ShareXLinkedInEmail

THE RUNDOWN

1

OpenCode is a popular open-source alternative to Claude Code and Cursor, so a breach of its hosted Console touches a widely used developer tool.

2

Attackers ran up hundreds, and in some cases over $1,000, in unauthorized AI API charges before OpenAI and OpenCode intervened.

3

The company's own 'large-scale distillation attack' framing is disputed -- skeptics call it a more conventional credential breach.

4

Developers should treat any AI coding tool that stores provider API keys as a credential-management risk, not just a productivity tool.

The VC Read

Value Add VC analysis

The actual diligence item here isn't whether OpenCode's distillation-attack framing holds up -- it's that an open-source coding agent with a large user base was storing live OpenAI, Anthropic and Google API keys in a way that let attackers run up charges for 48 hours before detection. Any dev-tool startup handling third-party API keys on a user's behalf needs a credible answer for key rotation, scoped permissions and anomaly detection, not just a blog post after the fact.

Analysis

OpenCode, an open-source AI coding agent that has become a popular alternative to Claude Code and Cursor, said attackers breached an older part of its system and accessed API keys stored by users of OpenCode Console, its hosted platform, according to TechCrunch. The company said the breach affected 1.4% of Console users and happened the same night it made its GLM-5.3-Flash model free to use.

Developers reported unauthorized spending alerts across OpenAI, Anthropic and Google AI accounts; some individual accounts were hit with charges in the hundreds of dollars, and a few topped $1,000. Co-founder Dax Raad said attackers had been trying to break in for 48 hours, and that AI models the team used to investigate refused to continue once the malicious code triggered safety filters -- OpenCode later got access to OpenAI's Daybreak Blue program, meant for vetted users doing defensive security work that models would otherwise decline.

What OpenCode hasn't explained

The company has not disclosed how attackers obtained the keys, how they were stored, or the full scope of misuse. It called the incident a "large-scale distillation attack," implying the goal was harvesting model outputs to train a rival model, but skeptics see that framing as unproven and the incident as a more conventional credential breach dressed up in AI language. Raad said the open-source app and command-line tool were unaffected, since exposed keys were confined to the Console product.

Anthropic and Google blocked the keys they believed were compromised, and OpenAI worked with OpenCode to restore access and refund credits used in the attack. OpenCode says refunds for other unauthorized charges are underway, and it has told affected users to revoke and replace their keys directly with each provider.

For a tool built on the premise that developers can trust it with API access to multiple AI providers, the breach is a reminder that convenience and credential exposure are the same tradeoff: the more providers a coding agent can reach on a user's behalf, the more valuable -- and more exposed -- those stored keys become if the agent's own infrastructure isn't hardened to match.

ShareXLinkedInEmail

Key Sources

1 source

Reported by TechCrunch · Analysis by Value Add Pulse.

← Back to Pulse

THE WIRE in your inbox— Tech, startup & VC news with The VC Read, a few times a week. Free to subscribe, no spam.

No spam, unsubscribe anytime. Sent via Substack · Privacy · or subscribe on Substack ↗