Skip to content
OpenCode’s AI Hack Changes Everything artwork

OpenCode’s AI Hack Changes Everything

AI News Today | Julian Goldie Podcast

October 19, 2026

OpenCode’s AI Hack Changes Everything

Speakers Julian Goldie

TopicsMarketingBusiness

Julian Goldie (0:00)

OpenCode got hacked, and some people actually woke up to find that AI keys have been used all night by a stranger. One person actually says his open-eyed and anthropic keys ran up over $400 in charges by the morning. Another one actually said $1,700.

Here's an example. So if you use AI agents in your business, call Chat, GPT, Gemini, any of them, this story is about you, even if you've never touched OpenCode, because the reason someone wanted those keys is an interesting part. It tells you where AI is heading, it changes how you should set up every single agent you run. So in this video, you'll find out what happened, why thieves wanted AI keys of all things, and the simple setup that keeps this from happening to you.

Let's start with one word, which is key.

When you use AI inside a tool, you often paste in something called an API key. Think of it like a house key for your AI account. Whoever holds the key can walk in and use your AI, and the charges land on your account, not theirs. Most people paste that key in once, then they forget about it.

Here's the problem, though. You hand your key to a tool, the tool saves it somewhere, now your key lives in a place you can't see. On a server, you don't run next to thousands of people's other keys. That's fine until it isn't, and that's actually what happened to OpenCode. So OpenCode is a popular open source coding agent. The company behind it is Anomaly Innovations. They also run something called OpenCode Console, and Console is the online version for teams. You can link your AI accounts like OpenAI, Anthropic, or Google. Your whole team can use those models without ever seeing the key, which is pretty handy, right? Your team doesn't need the key. Console holds them. But that also means the Console was sitting on a pile of live keys. And on the night of October 16th, someone actually got into one of OpenCode systems.

And the next morning, some Console users got an email. The subject line, as she said, action required, potential provider, key breach. The email said OpenCode found unauthorized access to a Lexi system. Lexi system just means an old one. This old system was one OpenCode was already in the middle of shutting down. Then came the line that mattered. Keys from outside providers, like OpenAI, Anthropic, Saving Your Workspace, may have been exposed. Now, security researcher Matt Johansson was one of the first people to actually flag it publicly.

Example right here.

And he basically said, confirmed, OpenCode hacked, keys stolen. And a few hours later, OpenCode actually converted itself. They said they had a security breach related to a large scale distillation attack. Now, if you're wondering what distillation is, we'll come on to that in a minute.

It's a key to this whole story, so we'll unpack that. And let me run you through the numbers first. So OpenCode actually says 1.4% of console users were hit.

Not 1.4% of everyone who uses OpenCode, just console users, and only the ones who had linked an outside AI provider. Now, OpenCode actually says it emailed every person affected. If you didn't get an email, they say you weren't affected.

And let's talk about the charges. These come from users, not from OpenCode. So one user actually said he's opening AI anathropic keys, keys he only ever used inside OpenCode, ran up over $400 overnight. Another user said $1,700. Max Weinbach, who writes about tech, confirmed he was hit too. His Open AI and anathropic balances were drained. His Google account got limited and drained a bit too. And yes, he got the email from OpenCode. And then it got personal for the company. So Dax Road, one of OpenCode's co-founders, said his own personal accounts were now being targeted too. And he summed it up like this. Whole new world with AI-powered hacking. So even the people who built the tool were getting hit. Now, here's what OpenCode has not told us yet. How many people 1.4% actually is? How the thief got in? How long they had access? And whether every key was really taken or just exposed? OpenCode's own words were, the incident is ongoing, so we can't share more details at this point. So we know the shape of it, we just don't know the full size of it yet. But the most useful number in this whole story isn't the $1,700. It's a number Anthropic published six days before this breach. And once you see it, the whole thing makes sense. We'll get there in a moment. Quick one, if you're running Claude, Hermes, OpenCode, or any agent in your business right now, you probably have keys sitting in more places than you can remember. Now inside the AI Profit Boardroom, that's exactly what we help you sort out.

12 more minutes of transcript below

Thousands of transcripts fetched by people building searchable podcast archives

Fetch the whole transcript

The demo key returns a sample episode in full, no card needed:

request
curl -H "x-api-key: pt_demo" \
  https://spoken.md/transcripts/1000651996090

Markdown with the speakers named, for your notes, your knowledge base, or anything that makes HTTP calls.

From $0.10 per transcript. No subscription. Credits never expire. Prices exclude VAT, added at checkout for EU customers. Not what you expected? Email us within 14 days with 20 or fewer credits used and we refund the pack in full.

Using your own key:

request
curl -H "x-api-key: YOUR_KEY" \
  https://spoken.md/transcripts/1000797040731