/
← Voltar ao feed
high technology

OpenCode Console legacy system breach may have exposed saved OpenAI, Anthropic and Google API keys of 1.4% of users

1 fonte(s) · 1 atualização(ões) · publicado 19/10/2026 03:07 · coletado há 3 dias

An intruder reached a legacy system at OpenCode on the night of October 16, and the company says third-party AI provider keys saved in OpenCode Console "may have been exposed." About 1.4% of Console users, all with an outside provider linked, were notified by email on October 17 and told to revoke and replace their OpenAI, Anthropic or Google keys. Some users report unauthorized charges, including $281 on OpenAI and $168 on Anthropic (Colin Parsons) and $1,700 in total losses (Preston Zeller). OpenCode has not confirmed that any key was copied or used. The company calls the incident ongoing and "related to a large-scale distillation attack," but has not named anyone or explained the link. Co-founder Dax Raad said attackers were still probing its systems on October 18.

Detalhes técnicos

  • Only keys pasted into the hosted Console are at risk. Keys stored locally by the OpenCode CLI and desktop apps (SQLite database) "never come to us" and are not involved.
  • Provider keys are bearer credentials: whoever holds a copy can run billable requests until the provider revokes it.
  • Deleting a key from Console does not revoke it, and a Console budget cannot cap abuse because Console only sees requests passing through its own gateway.
  • Unconfirmed user reports include about $400 of unauthorized Anthropic usage and about €200 of Google usage (via Notebookcheck and Dealroom).
  • Not disclosed: the legacy system's identity, how it was reached, when access began, how many keys it held, and how many users 1.4% represents.
  • Context: Anthropic said in September that distillation campaigns use fake accounts built on stolen cards, credentials and harvested API keys. Criminal markets also resell AI keys and tokens.

Remediação

  • Revoke the key in the provider's dashboard (OpenAI, Anthropic, Google) and create a new one.
  • Update every application and script that used the old key.
  • Review provider usage and billing for requests you did not make, going back at least to October 16.
  • Set spend limits or alerts at the provider and give each tool its own key.

Linha do tempo

  1. thehackernews.com ↗ · pub. 19/10/2026 03:07 · coletado 19/10 17:53 primeiro registro

    OpenCode Console legacy system breach may have exposed saved OpenAI, Anthropic and Google API keys of 1.4% of users

    ler a análise desta fonte

    An intruder reached a legacy system at OpenCode on the night of October 16, and the company says third-party AI provider keys saved in OpenCode Console "may have been exposed." About 1.4% of Console users, all with an outside provider linked, were notified by email on October 17 and told to revoke and replace their OpenAI, Anthropic or Google keys. Some users report unauthorized charges, including $281 on OpenAI and $168 on Anthropic (Colin Parsons) and $1,700 in total losses (Preston Zeller). OpenCode has not confirmed that any key was copied or used. The company calls the incident ongoing and "related to a large-scale distillation attack," but has not named anyone or explained the link. Co-founder Dax Raad said attackers were still probing its systems on October 18.

    Technical Details

    • Only keys pasted into the hosted Console are at risk. Keys stored locally by the OpenCode CLI and desktop apps (SQLite database) "never come to us" and are not involved.
    • Provider keys are bearer credentials: whoever holds a copy can run billable requests until the provider revokes it.
    • Deleting a key from Console does not revoke it, and a Console budget cannot cap abuse because Console only sees requests passing through its own gateway.
    • Unconfirmed user reports include about $400 of unauthorized Anthropic usage and about €200 of Google usage (via Notebookcheck and Dealroom).
    • Not disclosed: the legacy system's identity, how it was reached, when access began, how many keys it held, and how many users 1.4% represents.
    • Context: Anthropic said in September that distillation campaigns use fake accounts built on stolen cards, credentials and harvested API keys. Criminal markets also resell AI keys and tokens.

    Remediation

    • Revoke the key in the provider's dashboard (OpenAI, Anthropic, Google) and create a new one.
    • Update every application and script that used the old key.
    • Review provider usage and billing for requests you did not make, going back at least to October 16.
    • Set spend limits or alerts at the provider and give each tool its own key.