/
← Voltar ao feed
high technology software development

OpenCode Console breach exposes AI provider API keys of 1.4% of users, driving unauthorized charges

1 fonte(s) · 1 atualização(ões) · publicado 19/10/2026 16:28 · coletado há 4 dias

OpenCode, an open-source AI coding agent, disclosed on Saturday that attackers broke into an older system overnight and affected 1.4% of users of its online platform, OpenCode Console. Some of those users store API keys for AI services there. The company called it a "large-scale distillation attack", but skeptics say it was a straightforward breach and that its use for distillation is unproven. Developers reported unauthorized charges on OpenAI, Anthropic and Google accounts, typically in the hundreds of dollars and in a few cases above $1,000. OpenCode says the incident is ongoing and has not explained how the attackers got in.

Detalhes técnicos

  • The exposed keys were confined to OpenCode Console workspaces. According to co-founder Dax Raad, the open-source app and CLI were not affected, and those keys never reach OpenCode.
  • OpenCode has not disclosed the initial access method, how the keys were stored, or the full extent of misuse.
  • Leaked API keys can help users in countries with restricted access to American models generate the high volume of outputs distillation needs, but the article does not confirm this was the purpose.
  • Raad said attackers had been trying to break in nonstop for 48 hours, and the team ran AI defensive agents around the clock. Commercial AI models eventually refused to analyze the malicious code because it triggered their safety filters.
  • OpenCode later got access to OpenAI's Daybreak Blue program, which gives vetted users models less likely to refuse defensive security work. Hugging Face reported a similar problem in July.
  • The breach occurred the same night OpenCode made GLM-5.3-Flash free for users. The article draws no causal link.

Remediação

  • Affected users were notified by email. Users who received no email were not impacted.
  • Affected users should revoke and replace their API keys directly with each AI provider.
  • Anthropic and Google blocked the keys they believed were exposed. OpenAI worked with OpenCode to restore access and refund customers for credits used in the attack. OpenCode says refunds for unauthorized charges are underway.
  • Users should monitor provider spend alerts and avoid storing long-lived provider keys in shared workspaces.

Linha do tempo

  1. techcrunch.com ↗ · pub. 19/10/2026 16:28 · coletado 19/10 17:55 primeiro registro

    OpenCode Console breach exposes AI provider API keys of 1.4% of users, driving unauthorized charges

    ler a análise desta fonte

    OpenCode, an open-source AI coding agent, disclosed on Saturday that attackers broke into an older system overnight and affected 1.4% of users of its online platform, OpenCode Console. Some of those users store API keys for AI services there. The company called it a "large-scale distillation attack", but skeptics say it was a straightforward breach and that its use for distillation is unproven. Developers reported unauthorized charges on OpenAI, Anthropic and Google accounts, typically in the hundreds of dollars and in a few cases above $1,000. OpenCode says the incident is ongoing and has not explained how the attackers got in.

    Technical Details

    • The exposed keys were confined to OpenCode Console workspaces. According to co-founder Dax Raad, the open-source app and CLI were not affected, and those keys never reach OpenCode.
    • OpenCode has not disclosed the initial access method, how the keys were stored, or the full extent of misuse.
    • Leaked API keys can help users in countries with restricted access to American models generate the high volume of outputs distillation needs, but the article does not confirm this was the purpose.
    • Raad said attackers had been trying to break in nonstop for 48 hours, and the team ran AI defensive agents around the clock. Commercial AI models eventually refused to analyze the malicious code because it triggered their safety filters.
    • OpenCode later got access to OpenAI's Daybreak Blue program, which gives vetted users models less likely to refuse defensive security work. Hugging Face reported a similar problem in July.
    • The breach occurred the same night OpenCode made GLM-5.3-Flash free for users. The article draws no causal link.

    Remediation

    • Affected users were notified by email. Users who received no email were not impacted.
    • Affected users should revoke and replace their API keys directly with each AI provider.
    • Anthropic and Google blocked the keys they believed were exposed. OpenAI worked with OpenCode to restore access and refund customers for credits used in the attack. OpenCode says refunds for unauthorized charges are underway.
    • Users should monitor provider spend alerts and avoid storing long-lived provider keys in shared workspaces.