Anomaly Innovations Reports API Key Exposure in OpenCode Console Distillation Attack
Anomaly Innovations says a large-scale distillation attack exposed API keys for 1.4% of OpenCode Console users.
Key points
- The breach affected approximately 1.4% of OpenCode Console users.
- Stored API keys were exposed via a large-scale distillation attack.
- Anomaly Innovations confirmed the incident affects its coding agent platform.
Anomaly Innovations confirmed that a security incident involving a large-scale distillation attack has exposed API keys for a subset of its user base. The company stated that the breach specifically impacted users of the OpenCode Console interface.
According to Startup Fortune, the attack targeted approximately 1.4% of OpenCode Console users. The compromise resulted in the exposure of API keys associated with these accounts. Anomaly Innovations described the event as a large-scale distillation attack against the coding agent.
Incident Scope and Details
The incident involves the open-source coding agent known as OpenCode. Anomaly Innovations identified that the attack vector involved a distillation technique. The company reported that API keys were exposed during this large-scale attack.
The source material notes that the breach hit OpenCode Console users and their API keys. Anomaly Innovations linked the exposure to the distillation attack method. No further technical details regarding the extraction process were provided in the report.
Affected User Base
The breach impacted a small fraction of the total user population. Anomaly Innovations reported that 1.4% of Console users were affected. This percentage represents the portion of the user base identified in the incident report.
The source material specifies that the breach hit OpenCode Console users. It does not provide information about users of other interfaces or features. The report focuses solely on the 1.4% of Console users whose keys were exposed.
What should you do?
Anomaly Innovations has acknowledged the incident but has not confirmed the availability of a patch or fix. Users are advised to monitor official communications for further instructions. No timeline for remediation has been provided by the vendor.
Security professionals should review their own API key configurations immediately. Rotating exposed credentials is the standard response to this type of data leak. Monitoring account activity for unauthorized access is also recommended.
What to do and how to stay safe: Anomaly Innovations
- Rotate any API keys that may have been stored in the OpenCode Console.
- Monitor associated accounts for unusual activity or unauthorized usage.
- Review current integration settings to ensure sensitive credentials are secure.
- Wait for official guidance from Anomaly Innovations before assuming the issue is resolved.
Step-by-step guide: Social Engineering Warning Signs and How to Respond
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
How many users were affected by the OpenCode breach?
Approximately 1.4% of OpenCode Console users were affected by the incident.
What type of attack caused the API key exposure?
The exposure resulted from a large-scale distillation attack against the coding agent.
What data was exposed in this breach?
API keys associated with the affected OpenCode Console users were exposed.
