/
← Voltar ao feed
high technology software development artificial intelligence

OpenCode Console breach via legacy system may expose OpenAI, Anthropic and Google API keys

1 fonte(s) · 1 atualização(ões) · publicado 19/10/2026 10:30 · coletado há 10 horas

OpenCode, the open-source AI agent framework developed by Anomaly, confirmed on October 17 a security breach that occurred the night before and affected its Console service. Console stores each workspace's third-party AI provider credentials centrally. About 1.4% of Console users, those with external providers linked, may have had OpenAI, Anthropic or Google API keys exposed. OpenCode described the incident as related to a "large-scale distillation attack" and said it involved unauthorized access to a legacy system being decommissioned. It notified affected users by email and informed Anthropic, OpenAI and Google. Co-founder Dax Raad stated that only the Console was affected, not OpenCode itself.

Technical Details

  • Unauthorized access to a legacy system that was being decommissioned. The article does not state the initial access method.
  • Console holds workspace-level provider credentials and uses them to authenticate requests to OpenAI, Anthropic and Google, so the keys may have been exposed.
  • The article attributes the incident to a "large-scale distillation attack", per OpenCode. No threat actor is named and no IOCs are published.
  • Affected users received an email titled "Action Required: Potential provider key breach."
  • OpenCode has about 217,000 GitHub stars and, per a July 2026 claim by its CEO, roughly 13 million monthly active users.

Remediation

Per Safeguard's recommendations:

  • Check your inbox for the notification email. If you did not receive it, review your keys anyway.
  • List every OpenAI, Anthropic and Google Gemini key ever stored in a Console workspace, including keys added by other admins.
  • Review provider usage and billing from October 16 onward for spikes, unfamiliar models or unexplained charges.
  • Create replacement keys first, then revoke the old ones. Do not assume a key is safe because it shows no suspicious usage.
  • Update CI/CD secrets, environment files, agent configurations and production applications, then confirm the revoked keys return authentication errors.
  • Use restricted, project-specific keys with spending limits and budget alerts. If you keep using Console, add a dedicated restricted key rather than a production key.

Linha do tempo

  1. infosecurity-magazine.com ↗ · pub. 19/10/2026 10:30 · coletado 20/10 16:31 primeiro registro

    OpenCode Console breach via legacy system may expose OpenAI, Anthropic and Google API keys

    ler a análise desta fonte

    OpenCode, the open-source AI agent framework developed by Anomaly, confirmed on October 17 a security breach that occurred the night before and affected its Console service. Console stores each workspace's third-party AI provider credentials centrally. About 1.4% of Console users, those with external providers linked, may have had OpenAI, Anthropic or Google API keys exposed. OpenCode described the incident as related to a "large-scale distillation attack" and said it involved unauthorized access to a legacy system being decommissioned. It notified affected users by email and informed Anthropic, OpenAI and Google. Co-founder Dax Raad stated that only the Console was affected, not OpenCode itself.

    Technical Details

    • Unauthorized access to a legacy system that was being decommissioned. The article does not state the initial access method.
    • Console holds workspace-level provider credentials and uses them to authenticate requests to OpenAI, Anthropic and Google, so the keys may have been exposed.
    • The article attributes the incident to a "large-scale distillation attack", per OpenCode. No threat actor is named and no IOCs are published.
    • Affected users received an email titled "Action Required: Potential provider key breach."
    • OpenCode has about 217,000 GitHub stars and, per a July 2026 claim by its CEO, roughly 13 million monthly active users.

    Remediation

    Per Safeguard's recommendations:

    • Check your inbox for the notification email. If you did not receive it, review your keys anyway.
    • List every OpenAI, Anthropic and Google Gemini key ever stored in a Console workspace, including keys added by other admins.
    • Review provider usage and billing from October 16 onward for spikes, unfamiliar models or unexplained charges.
    • Create replacement keys first, then revoke the old ones. Do not assume a key is safe because it shows no suspicious usage.
    • Update CI/CD secrets, environment files, agent configurations and production applications, then confirm the revoked keys return authentication errors.
    • Use restricted, project-specific keys with spending limits and budget alerts. If you keep using Console, add a dedicated restricted key rather than a production key.