Back Office BeatSubscribe

Published by J9 Systems. What's new in business tech, and what it means for yours.

From the brief of Tuesday, October 20, 2026 · No. 9

From the daily brief · AI

OpenCode Console breach leaks AI API keys of 1.4% of users; most small shops unaffected

Unless a developer on your payroll uses OpenCode Console, this one passes you by, but it shows why every AI account you pay for needs a spend cap.

By Carter Josephson · · 2 min read

What happened

OpenCode, an open-source AI coding agent, said on Saturday, Oct. 17, that attackers broke into an older system behind its OpenCode Console web platform, affecting 1.4% of Console users, some of whom stored API keys for AI services there, and that it notified all affected users by email. The company says its open-source app and command-line tool were not affected, refunds for unauthorized charges are underway, and affected users should revoke and replace their keys directly with each AI provider.

What it means for a 10-to-50-person business

Primary source is OpenCode's own post on X; charge amounts and provider responses come from TechCrunch's reporting. The direct effect on a 10-to-50-person trades or services business is close to zero. OpenCode is a tool for software developers, and only Console users who got an email were hit. The wider lesson is the one worth 15 minutes. An API key is a password that bills you. Take a 25-person accounting firm that pastes an OpenAI key into a Zapier or Make workflow to pull line items off vendor invoices, spending about $40 a month. If that key leaks from any tool that stores it, a stranger can run up charges until someone notices. Affected developers reported hundreds of dollars per account, and a few reported more than $1,000 overnight. A monthly spend cap or budget alert of, say, $75 on each AI account turns an open-ended loss into a small, capped one. Check whether your provider's setting is a hard stop or only an email alert. Firms with no AI API accounts can ignore this entirely.

What to do
Ignore

Unless someone on your team or a contractor uses OpenCode Console, take no action on the breach itself; if you hold OpenAI, Anthropic or Google API keys in any automation tool, spend 15 minutes this month setting a monthly spend cap or budget alert on each account.

What it costs
What it costs
OpenCode exposure for a shop not using Console
$0
Setting spend caps or alerts on 3 AI accounts
15 min (≈ $13 at $50/hr)
Rotating one leaked key and updating it in Zapier or Make, if ever needed
30 min per tool (≈ $25 at $50/hr)
Doing nothing
$0 unless a key leaks; affected developers reported hundreds of dollars, a few over $1,000 per account
Sources
x.com (primary) · TechCrunch: Hackers hit AI coding tool OpenCode, running up charges on users' AI accounts · OpenCode co-founder Dax Raad on refunds for unauthorized charges · Notebookcheck: OpenCode hacked, users urged to revoke their API keys

Questions owners ask

How do I know if my business was affected?

OpenCode says it emailed every affected Console user and that anyone who did not get an email was not impacted. If nobody at your firm or your outside developer uses OpenCode Console, you were not affected.

Were ChatGPT or Claude subscriptions hit?

The exposed items were API keys stored in OpenCode Console workspaces, which bill per use. Anthropic and Google blocked keys they believed were exposed, and OpenAI said it is refunding its API customers for credits used in the attack.

Where do small businesses usually store AI API keys?

Most often inside automation tools such as Zapier, Make or n8n, or in a custom integration a contractor built. Keep a list of where each key lives so you can rotate it quickly.

Three to five of these, every weekday morning.

Related