OpenCode says breach may have exposed linked provider API keys

OpenCode confirmed the breach on October 17 and described it as a large-scale distillation attack.[1][2] The company said the incident was ongoing and that it could not share more details at that point.[2] It also said it was working with Anthropic, OpenAI and Google to remediate the incident.[2] The disclosure establishes the reported scope and the potential exposure, but does not give further details about how the attack occurred. For teams assessing their response, distinguish the company’s description of the incident from details OpenCode said it could not yet share.[2]

OpenCode said 1.4% of OpenCode Console users were affected.[2] OpenCode warned that third-party provider keys saved in affected workspaces may have been exposed; the named providers were OpenAI, Anthropic and Google.[2][1] The disclosure describes possible exposure, not confirmation that every listed key was accessed or misused. Users who did not receive an email from OpenCode were told they were not affected.[2]

OpenCode said it notified affected users individually by email and asked those users to revoke and replace their provider keys.[2] It also advised updating applications that use the keys and reviewing recent usage for unexpected activity.[2] Those steps matter beyond the OpenCode workspace: replacing a key alone may not update applications that were configured to use it, so affected teams should account for those applications when carrying out the company’s guidance. OpenCode said it was working with the named providers on remediation.[2]

OpenCode patched the issue in version 1.1.10.[2] Separately, users reported unauthorized charges of $400 on an Anthropic account and Google usage charges of around €200, with one user also saying their project was suspended for excessive abuse.[3] Some users said their OpenCode service API keys expired and social sign-in attempts failed after the breach.[3] These are user reports; the evidence does not establish that each reported charge or access problem resulted from the breach. OpenCode also said the incident was ongoing when it could not yet share more details.[2]