OpenCode Breach Exposes API Keys for Anthropic, OpenAI, and Google

What happened

Why it matters

• ·Enterprises that store AI provider credentials in third-party platforms inherit those platforms' security vulnerabilities. A stolen API key gives an attacker direct access to AI model services under the victim's account. This enables unauthorized use, data exposure, and charges reaching tens of thousands of dollars before detection.
• ·Standard vendor due diligence programs often assess primary AI providers but miss the intermediary tools, such as developer consoles and orchestration platforms, where credentials are actually stored. This breach illustrates that NIST AI Risk Management Framework (AI RMF 1.0) and Playbook-aligned vendor risk programs must extend to every custodian of AI provider secrets, not only the model providers themselves.
• ·Incident notification obligations become unclear when the breached party is an intermediary, not the primary AI provider. Organizations may have contractual notification rights against Anthropic, OpenAI, or Google but lack equivalent terms with platform intermediaries. This leaves them dependent on public reporting rather than direct notification to trigger their own response.

Governance controls affected

What to do now

• ☐Rotate API keys for Anthropic, OpenAI, and Google immediately if your organization uses or has used OpenCode's Console service, and revoke any keys that were stored in the platform.
• ☐Audit every third-party developer tool, console, or orchestration platform where AI provider API keys are stored or have ever been stored, and confirm each is included in your vendor security review program.
• ☐Check vendor contracts with AI platform intermediaries to confirm they include a requirement to notify you within a defined time window following any security incident affecting your credentials.
• ☐Review recent billing and usage logs across your Anthropic, OpenAI, and Google accounts for unusual spikes in requests or costs that may indicate unauthorized use of a compromised key.
• ☐Establish a policy requiring that AI provider API keys be stored only in approved credential management systems, not in third-party platforms, unless those platforms have been formally assessed and approved by your security team.

What to watch next

Compliance teams should monitor whether OpenCode publishes a formal incident report disclosing the scope of data accessed, the timeline of the breach, and the notification process it followed. Regulators in jurisdictions with breach notification requirements may scrutinize the lag between discovery and customer notification. The incident is likely to accelerate guidance from bodies such as the National Institute of Standards and Technology and sector regulators. Specifically, regulators may address how AI provider credential management should be scoped within third-party risk programs. Teams should also watch for similar incidents at other AI developer console and orchestration vendors, as the pattern of centralized credential storage in platform intermediaries is widespread.