OpenCode Console breach may have exposed AI provider keys
OpenCode says an intruder may have accessed provider keys saved in Console, affecting 1.4% of users with an outside AI account linked.
OpenCode says an intruder reached a legacy system on 16 October and may have exposed third-party AI provider keys saved in OpenCode Console. The company told affected users to revoke those keys with their provider and replace them. The incident concerns Console, OpenCode's optional hosted service, rather than the command-line or desktop applications. 12
Who may be affected
The potentially affected group is 1.4% of Console users who had linked an outside provider account. Console can store an OpenAI, Anthropic or Google key for a workspace, then use it to call the selected provider without showing the key to other team members. OpenCode said users who did not receive its 17 October warning email were not affected, although the company has not published a full incident report. 12
Keys entered directly into OpenCode's local applications are stored on the user's machine, according to the provider documentation. The reported exposure concerns credentials pasted into Console. Deleting a key from Console is not the same as revoking it: a copied bearer token may still be used for billable requests until its owner disables it. 13
What users should do
Anyone who saved a provider key in Console should revoke it in the provider's own dashboard, create a replacement, update applications that used the old credential and check usage and billing from 16 October onwards. OpenAI, Anthropic and Google each provide key-security guidance. Users should also set spend alerts where available and avoid reusing one credential across unrelated tools. 1
OpenCode has not said that every exposed key was copied or used. It has not identified the intruder, explained how the legacy system was reached or published the number of users represented by 1.4%. Reports of unauthorised charges are individual claims, not a confirmed total. 1
Our opinion
The useful part of this warning is its narrow scope: it is not evidence that every OpenCode installation or local provider key was compromised. It is still serious because a provider key is effectively a payment credential. Revoke-first advice is appropriate; waiting for a complete post-mortem only prolongs the risk for people who know they used Console. OpenCode's next job is to publish enough technical detail for affected customers to judge what happened.