OpenCode discloses breach affecting 1.4% of Console users, attributed to a 'large-scale distillation attack'
OpenCode disclosed on X on October 17 a security breach affecting 1.4% of its Console users, which it attributes to a "large-scale distillation attack". The affected accounts belong to users who had connected external providers. The company emailed affected users the following morning and says anyone who did not receive a notice was not impacted. That assurance is OpenCode's own assessment, not independently verified. OpenCode is working with Anthropic, OpenAI and Google on the response, but this does not imply their infrastructure was compromised. The incident is described as ongoing.
Technical Details
- The disclosure does not say how attackers gained access, which integration components were involved, or whether API keys, stored secrets or account data were exposed.
- OpenCode has not explained the link between the breach and distillation activity. Claims of stolen API keys, automated model extraction, unauthorized inference requests or financial loss are unconfirmed.
- No IOCs, attacker information, affected integration versions or total number of impacted accounts have been published.
Remediation
- The public statement does not specify customer actions. Affected customers should follow the instructions in the notification email.
- Pending further disclosure, defenders using OpenCode with third-party providers may consider reviewing and rotating provider credentials and checking for anomalous usage. This is a precaution, since the article does not confirm key exposure.
Linha do tempo
-
OpenCode discloses breach affecting 1.4% of Console users, attributed to a 'large-scale distillation attack'
ler a análise desta fonte ocultar
OpenCode disclosed on X on October 17 a security breach affecting 1.4% of its Console users, which it attributes to a "large-scale distillation attack". The affected accounts belong to users who had connected external providers. The company emailed affected users the following morning and says anyone who did not receive a notice was not impacted. That assurance is OpenCode's own assessment, not independently verified. OpenCode is working with Anthropic, OpenAI and Google on the response, but this does not imply their infrastructure was compromised. The incident is described as ongoing.
Technical Details
- The disclosure does not say how attackers gained access, which integration components were involved, or whether API keys, stored secrets or account data were exposed.
- OpenCode has not explained the link between the breach and distillation activity. Claims of stolen API keys, automated model extraction, unauthorized inference requests or financial loss are unconfirmed.
- No IOCs, attacker information, affected integration versions or total number of impacted accounts have been published.
Remediation
- The public statement does not specify customer actions. Affected customers should follow the instructions in the notification email.
- Pending further disclosure, defenders using OpenCode with third-party providers may consider reviewing and rotating provider credentials and checking for anomalous usage. This is a precaution, since the article does not confirm key exposure.