OpenCode said attackers accessed an older system, affecting 1.4 percent of Console users and prompting key revocations and refunds.
OpenCode disclosed on October 17, 2026, that attackers had breached an older system used by OpenCode Console, its online platform for users who store AI-service API keys. The company said 1.4 percent of Console users were affected and that it had notified them. OpenCode’s open-source application and command-line tool were not affected, according to co-founder Dax Raad.
Users reported unauthorized API activity and spending alerts involving OpenAI, Anthropic, and Google services. TechCrunch reported that some individual accounts faced charges in the hundreds of dollars, while a few users described totals above $1,000. OpenAI said it worked with OpenCode to restore access and refund customers for credits used in the attack; OpenCode said refunds for unauthorized charges were underway. Anthropic and Google blocked keys they believed had been exposed.
OpenCode characterized the incident as a large-scale distillation attack, but the company had not explained how the intrusion happened, how the keys were stored, or the full extent of any misuse. Some observers disputed whether the available information established that the breach was connected to distillation. The reported use of that label therefore remains the company’s characterization, not a settled account of the attackers’ purpose.
The response also exposed a challenge for incident teams using AI tools. Raad said models initially helped OpenCode investigate, but some later refused requests to analyze malicious code after safety filters were triggered. OpenCode subsequently received access to OpenAI’s Daybreak Blue program, which provides vetted users with models less likely to refuse defensive security work; Raad said that access improved the investigation.
The company told affected users to revoke and replace their API keys directly with the providers. At the time of TechCrunch’s report, OpenCode said the incident was ongoing. The breach affected credentials stored through Console, underscoring that users should treat service-connected API keys as sensitive secrets and monitor associated accounts for unauthorized usage.