The Shared Key Was the Exposed One, and the Team Paid the Bill

OpenCode confirmed on 17 October that an attacker reached a legacy system it was decommissioning, and that provider keys saved in Console workspaces may have been exposed. The keys that leaked were the shared ones.

• OpenCode puts the impact at 1.4 percent of Console users, the group who had linked an external provider. Keys pasted into the local command line tool stayed on the developer machine.
• The earliest possible exposure was 00:30 UTC on 17 October. One user reported more than $1,700 in unauthorized charges overnight.
• Anthropic and Google blocked affected keys. OpenAI restored access and refunded API customers for credits used in the attack.
• Rotation ends new spend. It does not restore a suspended Google Cloud project or the two days of queries already spent.
• Co-founder Dax Raad said attackers worked the systems for at least 48 hours with AI agents, and that his own team’s models refused requests under safety guardrails mid incident.

A hosted workspace turns one credential into a team credential. Scope and spend caps are the control. Full analysis here.