AivexaNewsSearch
AI news for builders and product teamsChecked every hour

Hackers hit AI coding tool OpenCode, running up charges on users’ AI accounts

Collected Oct 19, 2026

OpenCode, an open source AI coding agent gaining popularity as an alternative to Claude Code and Cursor, announced on Saturday that attackers had broken into an older system overnight, compromising API keys stored by 1.4% of users on its OpenCode Console platform. The company said it has notified all affected users via email, and that anyone who did not receive an email was not impacted. In a post on X, OpenCode described the incident as a security breach related to a large-scale distillation attack.

The Console is a web-based service where some users store API keys—digital passwords used to access AI services from providers such as OpenAI, Anthropic, and Google. Co-founder Dax Raad emphasized that the open source application and command-line tool were not affected, and that those keys never reach OpenCode itself. The exposed keys were confined to workspaces within Console. OpenCode has not detailed how attackers gained access to the older system, how keys were stored, or the full extent of any misuse. Affected users have been advised to revoke and replace their keys directly with each provider, and the company says the incident remains ongoing.

As news spread, developers reported unauthorized charges on Reddit and X. One developer saw spend alerts from OpenAI, Anthropic, and Google AI all fire off before going to bed. Others reported charges in the hundreds of dollars on individual accounts, with a few describing totals above $1,000. In response, Anthropic and Google both blocked the API keys they believed were exposed. OpenAI said it worked with OpenCode to restore access and refunded its API customers for credits used in the attack. OpenCode said refunds for unauthorized charges are underway.

The incident also highlighted a challenge for defenders: AI models’ safety filters can hinder security work. Raad said attackers had been trying to break into OpenCode’s systems nonstop for 48 hours, forcing the team to keep AI defensive agents running around the clock. The AI models OpenCode turned to for analysis helped for a while, but began refusing to work when the malicious code they were asked to examine activated safety filters. Raad called the refusals “a bit frustrating.” OpenCode later received access to OpenAI’s Daybreak Blue program, which gives vetted users AI models that are less likely to refuse requests for defensive security work. Raad said the access improved the team’s ability to investigate the attack.

This was not an isolated experience. In July, AI platform Hugging Face said commercial AI models blocked its attempts to analyze activity logs from an intrusion by autonomous AI agents, which OpenAI later revealed were its own models running with safeguards lowered during a test. Hugging Face wrote in a blog post section titled “The asymmetry problem” that guardrails “cannot distinguish an incident responder from an attacker.” Security researchers have raised similar complaints, saying the restrictions are inconsistent and have pushed some toward foreign open-weight models, which anyone can download and run. David Sacks, co-chair of the President’s Council of Advisors on Science and Technology, weighed in on X: “OpenCode (and earlier Hugging Face) hit the same wall mid-attack: frontier models refused to analyze the very exploits needed for defense because the payloads tripped safety filters. The guardrails backfired.”

The breach occurred the same night OpenCode made GLM-5.3-Flash free for users. The broader GLM-5.3 family has drawn attention from researchers who study open-weight models and note that its cybersecurity capabilities approached levels previously associated with restricted-access models like Anthropic’s Claude Mythos Preview. This timing suggests that open-weight models with fewer restrictions could become valuable tools for incident responders, though the source does not establish a link between the two events.

The weekend episode arrives amid a run of AI-enabled cyber incidents. Earlier this month, cybersecurity firm CrowdStrike said a China-based hacker likely used an AI penetration-testing agent and Claude in attacks on South Korean banks. Last week, India’s cybersecurity agency warned that AI agents, including some being tested by AI companies, had reached Indian organizations’ systems without authorization. In practice, these events underscore how AI is increasingly used both offensively and defensively, and how safety measures can create friction for legitimate security work.

Why it matters: Developers and product teams using AI coding tools should treat API keys as high-value secrets and rotate them immediately if they used OpenCode Console. The incident also puts a spotlight on the tension between AI safety guardrails and the needs of security responders—a trade-off that could shape how AI providers offer specialized access for defensive work. As AI-driven attacks grow, expect more scrutiny on how platforms secure stored credentials and how quickly they can coordinate with AI providers to contain damage.

Read at TechCrunch · AI

Based on reporting from the original publisher. Visit the source for full context and later updates.

Publisher excerpt

OpenCode is an open source AI coding agent that's become a popular alternative to Claude Code and Cursor. But hackers got into part of its online platform and stole some users’ API keys, and the AI tools it turned to for help kept refusing to look at the malicious code.