A security breach at OpenCode, an open-source AI agent framework provider, may have exposed API keys tied to Anthropic, OpenAI, and Google AI models for a subset of its users. On October 17, the company confirmed unauthorized access to its Console service, which happened the night before and affected 1.4% of Console users. The incident involved what OpenCode described as a "large-scale distillation attack" targeting a legacy system the company was in the process of shutting down.
OpenCode's Console service lets teams share access to AI models through centrally managed API credentials, storing each workspace's authentication keys rather than distributing the underlying OpenAI, Anthropic, or Google keys to individual team members. The platform has gained significant traction among software developers, with 217,000 stars on GitHub. In a July 2026 interview with Y Combinator, which financially backs Anomaly—the company that develops and maintains OpenCode—founder and CEO Jay V stated the platform had reached around 13 million monthly active users and 4.6 million weekly active users. The breach affected only users who had linked external provider credentials to their workspaces, and all impacted individuals received email notifications the morning of October 17.
According to OpenCode's public statements on social media and emails shared by users on Reddit and Discord, the company "identified unauthorized access to a legacy system that we were in the process of decommissioning" and warned that "third party provider keys (e.g. OpenAI, Anthropic) saved in your workspace may have been exposed." Dax Raad, a main contributor to OpenCode and co-founder of Anomaly, clarified on X that the breach hit "the OpenCode Console, not OpenCode itself." The company notified Anthropic, OpenAI, and Google to help address the issue.
Software supply chain security firm Safeguard released an incident response report with detailed steps for OpenCode users to identify exposure and limit damage. The recommended actions include checking email inboxes for a message with the subject line "Action Required: Potential provider key breach," cataloging every OpenAI, Anthropic, and Google Gemini API key ever stored in a Console workspace, and reviewing each provider's usage and billing reports from October 16 forward for unexpected spikes or unfamiliar activity. Users should generate replacement keys before revoking old ones, disable potentially compromised credentials through provider dashboards regardless of whether suspicious usage appears, and update all systems—including CI/CD secrets, environment files, local agent configurations, and production applications—with the new keys. Additional security measures include restricting keys to required projects and APIs, setting spending limits and budget alerts, verifying that revoked keys return authentication errors when tested, and adding dedicated restricted API keys to Console rather than reusing production credentials.
The breach highlights the vulnerability of centralized credential management systems even as they're designed to improve security by limiting direct key exposure to individual developers. Organizations relying on third-party platforms to manage access to AI models now face a trade-off between convenience and the concentration of risk in a single point of failure. Leaders weighing these architectural choices will need to balance operational efficiency against the potential cascade effects when shared infrastructure is compromised.