OpenCode said on X on 17 October that it “had a security breach last night related to a large scale distillation attack that impacted 1.4% of OpenCode Console users.” The affected users were the ones “who had external providers linked.”
A customer email shared on X the same day told recipients that third-party provider keys, such as OpenAI and Anthropic keys, saved in their workspace “may have been exposed”, and asked them to revoke and replace those keys.
Business Pill · DISTILLATION
A one-minute explainer of model distillation: how a smaller model is trained to imitate a larger one. It teaches the general idea only and says nothing about OpenCode or this incident.
The key insight: As we read it, the exposure sits in the keys users brought to the tool: OpenCode says the impact was limited to Console users “who had external providers linked”, and the email asks them to revoke and replace those provider keys.
OpenCode posted its statement on X at 18:08 UTC on 17 October. In full:
“We had a security breach last night related to a large scale distillation attack that impacted 1.4% of OpenCode Console users”
“We have notified them all this morning via email. If you did not get an email you were not impacted, it was a subset of users who had external providers linked”
“The incident is ongoing so we cannot share more details at this point but we are working with Anthropic, OpenAI, and Google to remediate”
OpenCode said the impact was limited to a subset of Console users with external providers linked, and that users who did not receive an email were not affected.
OpenCode said a breach it ties to a large-scale distillation attack impacted 1.4% of OpenCode Console users, a subset with external providers linked. Affected users were emailed on the morning of 17 October to revoke and replace provider keys; the security researcher Matt Johansen posted at 15:30 UTC, and OpenCode confirmed at 18:08 UTC that it is working with Anthropic, OpenAI and Google to remediate. Sources: OpenCode on X; the customer email as shown in an r/opencode screenshot shared by Johansen; Johansen on X.
What Was Posted on X
We had a security breach last night related to a large scale distillation attack that impacted 1.4% of OpenCode Console users
We have notified them all this morning via email. If you did not get an email you were not impacted, it was a subset of users who had external providers linked
The incident is ongoing so we cannot share more details at this point but we are working with Anthropic, OpenAI, and Google to remediate
OpenCode’s own statement, posted at 18:08 UTC on 17 October: a breach it ties to a large scale distillation attack impacted 1.4% of OpenCode Console users, a subset with external providers linked; affected users were emailed, and OpenCode says it is working with Anthropic, OpenAI and Google to remediate.
The security researcher Matt Johansen’s post at 15:30 UTC, with a screenshot of an r/opencode forum post showing the customer email that asks users to revoke and replace provider keys. The ‘Confirmed’ wording is his; OpenCode’s own confirmation came at 18:08 UTC.
What the Email Told Users
The email, headed “Action Required: Potential provider key breach”, appears in a screenshot of a post on the r/opencode forum that the security researcher Matt Johansen shared on X. It reads:
“We identified unauthorized access to a legacy system that we were in the process of decommissioning. Third party provider keys (eg OpenAI, Anthropic) saved in your workspace may have been exposed.”
It asks users to “revoke and replace those keys through the relevant provider’s dashboard, update any applications using them, and review recent usage for unexpected activity.”
How It Surfaced
Johansen, founder of the security newsletter Vulnerable U, posted at 15:18 UTC: “Seems OpenCode customers getting notices of a breach. Got some DMs that people’s API keys are running up charges.” Twelve minutes later he wrote: “Confirmed. OpenCode hacked. Keys stolen. Telling customers to revoke.”
OpenCode’s own statement followed at 18:08 UTC. The charges Johansen mentions are his report of messages he received; OpenCode’s post does not give figures on unauthorised usage.
What Users Are Asked to Do
Per the email, users with keys saved in their OpenCode workspace should revoke and replace them in each provider’s dashboard, update any applications that use those keys, and check recent usage for unexpected activity. OpenCode said users who did not get an email were not impacted.
The Distillation Link
OpenCode described the breach as “related to a large scale distillation attack”, and said it is working with Anthropic, OpenAI and Google to remediate.
As we read it, the email and the post describe two sides of one incident: the email speaks of “unauthorized access to a legacy system” and of keys that “may have been exposed”, while OpenCode’s post ties the breach to a “large scale distillation attack”. Neither text explains how the two connect.
As we read it, the remediation runs through the model providers: OpenCode says it is working with Anthropic, OpenAI and Google, and users are asked to act in each provider’s own dashboard.
As we read it, the first public signal came from users rather than from OpenCode: Johansen reported DMs about keys “running up charges” nearly three hours before OpenCode’s post.
OpenCode, on X, 17 October 2026
“If you did not get an email you were not impacted, it was a subset of users who had external providers linked”
Three Implications
OPENCODE CONSOLE USERS WHO GOT THE EMAIL The email asks them to revoke and replace provider keys saved in the workspace, update any applications using them, and review recent usage for unexpected activity.
USERS WHO DID NOT GET AN EMAIL OpenCode says they were not impacted.
TEAMS THAT LINK PROVIDER KEYS TO CODING TOOLS The keys OpenCode’s email names as examples, OpenAI and Anthropic keys, are the ones users saved in their workspace.
The framework describes the governance layer this way: “It is where decisions are made about who gets access to frontier intelligence, under what conditions, and for which purposes.”
As we read it, provider keys are that access in its most literal form, and OpenCode says the breach is tied to a distillation attack, the practice of training a model on another model’s outputs. The framework was published in June 2026 and does not discuss OpenCode.
What Is Not Established
OpenCode said it cannot share more details while the incident is ongoing. Its post and the email do not say how many users 1.4% represents, which legacy system was accessed, or how the distillation attack and the exposure of keys are connected.
The email text comes from a screenshot of a forum post shared by Johansen; it matches OpenCode’s own description of notifying users by email, but we have not seen the email directly. We did not contact OpenCode.
Business Engineer Framework
Inside Anthropic’s Permission Layer
A Business Engineer analysis of the governance layer that decides who gets access to frontier intelligence.
OpenCode says a breach it ties to a large-scale distillation attack affected 1.4% of OpenCode Console users, a subset who had external providers linked, and that it is working with Anthropic, OpenAI and Google on remediation.
The email tells those users to revoke and replace their provider keys and to check recent usage.
A note on sourcing. This piece is based on OpenCode’s own post on X of 17 October 2026, the text of the customer email as shown in a screenshot of an r/opencode forum post shared by the security researcher Matt Johansen, and Johansen’s posts on X. We did not see the email directly and did not contact OpenCode. The references to our earlier reporting link to our own pieces.
Gennaro Cuofano is a CRO and tech executive who has worked in AI since late 2015, starting with bringing NLP, natural-language generation, voice and chatbot products to the marketing industry. His background is in law and finance: he holds a Master's degree in Law and an International MBA with an emphasis on corporate finance (LUISS Business School and the University of San Diego, 2012), and worked as a financial analyst at a real-estate investment firm in San Diego and as an assistant controller. His work focuses on business model strategy, business engineering and, more broadly, structural analysis: how companies make money, read from their own filings. He created FourWeekMBA and leads research there and at The Business Engineer, his newsletter on AI and business strategy, with over 95,000 subscribers and more than 1,000 published analyses. His writing has also appeared on Entrepreneur, HackerNoon and Search Engine People. Find him on LinkedIn and Substack. See how we source.
Scroll to Top
Discover more from FourWeekMBA
Subscribe now to keep reading and get access to the full archive.
