OpenCode Says Distillation Attack Hit 1.4% of Console Users
OpenCode says a large-scale distillation attack affected 1.4% of Console users and that it is working with Anthropic, OpenAI and Google to remediate, but the ongoing incident leaves the attack method and impact details 未
OpenCode disclosed a security breach tied to what it called a large-scale distillation attack, saying the incident affected 1.4% of OpenCode Console users. The company said it emailed all affected users and that the incident remains ongoing, limiting further detail.
OpenCode added that it is working with Anthropic, OpenAI, and Google to remediate. OpenCode did not specify the nature of the impact, how the attack unfolded, or when the incident began beyond 'last night.'
The bits that matter
- OpenCode said the breach occurred 'last night' and was related to a large-scale distillation attack, a term it did not define in the disclosure.
- The company said 1.4% of OpenCode Console users were affected and that all of them were notified by email this morning.
- OpenCode said the incident is ongoing, so it cannot share more details at this point.
- The company said it is working with Anthropic, OpenAI, and Google to remediate.
Discussion analysis
Analysis details
9 comments analyzed. Analyzed .
The sample selects active discussion branches and includes available parent comments. It may omit parts of the full thread. The analysis included 9 of 15 usable stored comments because of the input limit. Selected themes do not measure community opinion or how common a view is.
Why OpenCode held API credentials
The breach raises a custody question: an open-source client still relies on inference APIs that bill users, but that does not explain why OpenCode's servers would hold API credentials. Server-side storage centralizes secrets and broadens the impact of a leak, a concern the disclosure does not address.
Invalidation endpoint risks denial of service
One suggestion is a universal invalidate_api_key endpoint so a storing party or whitehat can revoke all keys after a leak, rather than relying on users to act. The counter is that an endpoint reachable from anywhere turns a credential leak into a denial-of-service vector, so revocation needs authentication and rate limits.
Flagging claims and moderation evidence
The submission's ranking is disputed. The author says OpenCode supporters flagged the post and asks for upvotes; a reply asks how that was determined, and another points to downvotes and relative position. A separate reply attributes the effect to bad automated flagging and vouches for the comments, leaving the cause unresolved.