HOT RADAR
toolsHEAT 0.0°

AI CURATED HOT STORY · 10/18/2026

OpenCode Key Leak Sparks Billing Fraud, Distillation Claim Met With Skepticism

5 reports archived0 independent sourcesupdated 10/20/2026, 03:28:34
Synthesis & Latest Updates

Open-source AI coding tool OpenCode disclosed that its legacy system suffered unauthorized access, leaking plaintext API keys for approximately 1.4% of users. This breach triggered widespread billing fraud, with some victims facing losses up to $1,700 in a single day across major providers like Anthropic, OpenAI, and Google.

While OpenCode attributed the incident to a "model distillation attack," community scrutiny highlights fundamental security failures as the root cause. The compromised system stored keys in plaintext without rotation mechanisms, allowing attackers to bypass quotas and execute high-frequency abuse. Although cloud vendors have intervened to revoke keys and process refunds, delayed risk control responses underscore significant supply chain vulnerabilities.

The incident serves as a critical warning for the AI ecosystem, demonstrating how poorly secured AI applications can become vectors for automated attacks. It emphasizes the urgent need for stricter key management standards and real-time monitoring to prevent infrastructure flaws from cascading into severe financial and operational damages.

LATEST/OpenCode continues remediation efforts with Anthropic, OpenAI, and Google, focusing on revoking leaked keys and processing refunds. However, trust remains fragile as the official "distillation attack" narrative lacks transparency and technical specifics, leaving the developer community skeptical about the platform's underlying security posture.

Coverage timeline

Total 5 reports · Latest first
  1. TechCrunch AIT2·78 pts
    • A security breach in OpenCode Console affected ~1.4% of users, primarily involving leaked API keys for AI services.
    • The attack was described as a 'large-scale distillation attack,' using leaked keys to generate high-volume outputs for model training or replication.
    • The incident underscores the difficulty of defending against AI-driven automated cyberattacks without vetted access controls.
  2. InfoQ 中文T2·78 pts
    • OpenCode's deprecated system stored keys in plaintext without rotation mechanisms, affecting 1.4% of users.
    • Attackers exploited leaked keys to bypass quota limits via high-frequency calls, causing losses up to $1,700/day per user.
    • Cloud providers (Anthropic/OpenAI/Google) initiated refunds and key revocations, though risk control responses were delayed.
  3. IT之家 · 智能时代T2·68 pts
    • OpenCode confirmed a security breach affecting ~1.4% of users, primarily involving the leakage of external API keys stored in user workspaces.
    • Attackers accessed a decommissioning legacy system to steal keys and initiate malicious requests, causing unexpected high charges (e.g., $400 unauthorized spend on an Anthropic account).
    • Some users detected anomalies via service alerts from OpenAI and Anthropic before receiving official notifications, highlighting the lag risk in supply chain security incidents.
  4. OpenCode (@opencode)T2·68 pts
    • OpenCode confirmed a large-scale distillation attack on its Console affecting 1.4% of users.
    • The impacted subset consisted mainly of users who had linked external model provider accounts within OpenCode.
    • Remediation is ongoing, with OpenCode collaborating directly with Anthropic, OpenAI, and Google.
    • This incident underscores the security risks inherent in third-party AI tool integrations.