OpenCode confirms breach: distillation-linked incident hit ~1.4% of Console users; remediating with OpenAI, Anthropic, Google

Core Background & Industry Pain Points

Coding agents need provider API keys to run. Once keys live in a hosted Console/workspace, risk moves beyond local config. On Oct 17 OpenCode disclosed an overnight breach tied to a large-scale distillation attack; it has not yet explained how distillation connects to credential exposure.

Architecture Highlights & Internals

The official post: ~1.4% of Console users impacted; emailed that morning (no email = not impacted); subset with external providers; ongoing remediation with Anthropic, OpenAI and Google. Third-party summaries of user-shared emails mention legacy-system access that may have exposed workspace keys—second-hand, not an official blog. SECURITY.md says the local agent does not sandbox; this case is Console-hosted keys.

Authoritative Benchmarks & Measured Scores

Incident disclosure, no benchmarks. Officials have not published key counts, root cause, encryption details, or confirmed billing abuse. The status page showed availability blips without a dedicated security incident. Unverified charge reports are not treated as facts here.

Developer Hands-on Guide

Check for OpenCode's email. If you ever saved provider keys in Console, revoke/reissue in each vendor dashboard and review Oct 16–17 usage with spend limits. Local subscription-only users without BYOK in Console are generally outside the stated subset. Avoid parking long-lived high-quota keys in Console until root cause is clear.