WORLDTECH NEWS Global technology intelligence.Contact
← Back to WORLDTECH
Cybersecurity SINGLE SOURCE

OpenCode Console Breach May Have Exposed OpenAI, Anthropic, and Google API Keys

Detailed view of a server rack with a focus on technology and data storage.
Illustrative photo.Photo by panumas nikhomkhai on Pexels

What happened

An intruder reached a legacy system at OpenCode on the night of October 16 and may have exposed the third-party AI provider keys that users had saved in OpenCode Console, the company said. OpenCode Console Breach May Have Exposed OpenAI, Anthropic, and Google API Keys  Swati Khandelwal  Oct 19, 2026 Data Breach / Artificial Intelligence An intruder reached a legacy system at OpenCode on the night of October 16 and may have exposed the third-party AI provider keys that users had saved in OpenCode Console, the company said.

The OpenCode command-line and desktop apps keep provider keys added on the machine in a SQLite database there. Console is OpenCode's optional hosted service: a workspace saves its own OpenAI, Anthropic, or Google key there, and Console operates with that key to call the provider so team members can use the models without ever seeing the key.

The affected group is 1.4% of Console users, all of whom have an outside provider linked, and OpenCode has told them via email to revoke those keys with each provider and replace them. The email went out on the morning of October 17 under the subject line "Action Required: Potential provider key breach."

Anyone who did not get one was not affected, OpenCode said in a post on X later that day. The keys at risk are the ones pasted into Console.

A provider key is a bearer credential: whoever holds a copy can run billable requests against the owner's account until the provider revokes it. Deleting the key from Console does not revoke it, and a Console budget cannot cap that use either, because Console only sees requests that pass through its own gateway .

For a key that was saved in a Console workspace, OpenCode's email and the providers' own guidance give these steps: Revoke the key in the provider's own dashboard and create a new one, following the instructions from OpenAI , Anthropic , or Google . Review usage and billing at the provider for requests you did not make, going back at least to October 16.

Sources & evidence