OpenCode Got Hacked Badly (My API Keys Got Drained)

Item: OpenCode Got Hacked Badly (My API Keys Got Drained)
Rating: 4
Author: PostSingularity Institute

Title history

OpenCode Got Hacked Badly (My API Keys Got Drained) — observed on 20261031-2304 UTC (YouTube)

by Kai · View the channel on PSI

Applied Sciences & Engineering Computing & Cybersecurity URComputer security URHComputer fraud and hacking

🎙 Kai 👥 65K 📅 October 20, 2026 ⏱ 19 min 👁 44K 📄 news review 🧭 2026-10-31

Available in: English (current) Français

Keywords

OpenCodeAPI key leakdistillation attackspend limitskey rotation

Summary

The video analyzes the OpenCode security breach of October 17, 2026, where attackers accessed a legacy database containing developers’ API keys for OpenAI, Anthropic, and Google, leading to unauthorized usage and financial losses ranging from $16 to $3,000. The creator explains the difference between the local terminal app and the web-based Console, emphasizing that the breach affected the latter’s BYOK feature. A timeline shows the attack began early in the morning, escalated within hours, and OpenCode’s official statement came 17.5 hours later. The video reveals that many keys were stored as plaintext in the database, despite encryption at rest, and criticizes the initial framing as a ‘distillation attack’ when evidence suggests it was a key validation sweep and theft. The key differentiator in losses was each user’s API spend limit and auto-reload settings, not attacker sophistication. Practical advice includes revoking keys at the provider, rotating all third-party keys, enabling hard limits on OpenAI, disabling auto-reload, reducing balances, deleting forgotten keys, and using separate keys per service. The creator also notes that real developer accounts are valuable on gray markets due to their history and trust.

185 words

Critical Evaluation

Value of the Information & Strength of the Argument

The video provides high informational value by combining a timeline, technical analysis of the database schema, and practical security recommendations. It effectively argues that the financial impact was determined by user-configured limits rather than attacker intent, supporting this with concrete examples (e.g., Max Weinbach’s prepaid balance halting charges). The argumentation is logical and well-supported, citing official statements, tweets from victims, and public code commits. The creator acknowledges uncertainties, such as the exact entry point, which adds credibility. However, some conclusions (e.g., distillation as a misnomer) are presented as strong opinions though based on limited evidence.

Scientific Rigor, Source Quality, Title Accuracy

The video references numerous sources, including OpenCode statements, TechCrunch, Anthropic’s distillation defense research, CISA advisory, and provider spend limit documentation, all linked in the description. These sources are credible and relevant. The analysis uses publicly accessible code commits to support claims about plaintext storage and failed deletion attempts. The title accurately reflects the content, focusing on the hack and API key drain. The creator maintains a balance between factual reporting and commentary, though some interpretations are presented with confidence. The inclusion of diverse sources strengthens the overall rigor.

198 words

Title / Content Match

The title accurately reflects the content: it covers the OpenCode hack, API key theft, and personal financial losses. It is slightly sensationalist but not misleading.

Quality & Reliability

7/10

The video relies on multiple official statements, a TechCrunch article, and public code commits, but the exact attack vector remains unconfirmed and some conclusions are inferential. Overall, it is fairly reliable with some speculative elements.

Chapters

Cited Sources

Gemini API billing — Reference for Gemini API billing and spend limits
OpenAI spend limits — Reference for OpenAI API hard limits and alerts
OpenCode commit removing legacy database — Evidence of the attempted removal of legacy database
Anthropic rate limits — Reference for Anthropic API tiers and limits
Anthropic auto-reload support — Reference for auto-reload on prepaid accounts
TechCrunch article on OpenCode hack — Coverage of the OpenCode breach and user impact
Anthropic distillation defenses — Reference to distillation attacks and defenses
CISA advisory AA26-251A — Advisory on API proxy services and criminal laundering
Reddit r/opencode thread — Community discussion of the breach

Concurring Sources

TechCrunch — Confirms opencode breach and user impact
OpenCode statement on X — Official acknowledgment of the breach

Dissenting Sources

Nathan Lambert's tweet — Questions the classification of the attack as distillation, suggesting it may be more accurately described as credential theft

External References

Contribution & Novelties

The video offers a concise, well-researched analysis of a recent security incident, highlighting the crucial role of API spend limits in determining damage extent. It debunks the ‘distillation attack’ narrative with concrete evidence (e.g., the test ping) and provides actionable security steps. The insight that real developer accounts are valuable due to their history and trust is a refreshing perspective.

Pour aller plus loin :

API key rotation best practices — Google’s guide on key management, relevant to rotating keys.
CISA advisory on API security — Official guidance on mitigating API-related threats.
Anthropic’s distillation defenses — Research on protecting models from distillation attacks, contextualizing the threat.

106 words

Radar Profile

The radar profile shows a balanced video with high quantitative and qualitative information, moderate technical depth, and strong reliability. The user likely values actionable insights and clear explanations.

Reliability 7/10

💬 Équilibré : Sur les 30 commentaires analysés, la majorité apprécie l'information et les conseils pratiques, mais plusieurs critiquent l'utilisation d'une voix IA et le ton répétitif, et certains questionnent la sécurité de BYOK.