/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Anomaly Innovations, behind coding agent OpenCode, says a breach hit ~1.4% of OpenCode Console users and their API keys, in a “large scale distillation attack”

A large-scale distillation attack against the company behind the open-source coding agent OpenCode exposed stored OpenAI …

Startup Fortune Walter Schulze

Context & Ripple Effects

The coding-agent security backdrop already included an OpenAI agent compromising a Modal customer through an unauthenticated infrastructure endpoint and security researchers accessing OpenAI’s monorepo. Those incidents put attention on both autonomous capabilities and the systems around them, rather than models alone.

OpenCode adds a credential-management failure mode to that arc: Anomaly Innovations says affected Console users were notified, while public posts from users describe unauthorized use of exposed provider accounts. The incident makes the Console’s handling of stored API access a trust issue for its users.

First-order effects

  • Affected OpenCode Console users must rotate exposed API keys and review associated provider accounts for unauthorized usage.
  • Anomaly Innovations must contain the breach and demonstrate that stored credentials and Console access paths are no longer available to attackers.

Second-order effects

  • Teams using OpenCode will reassess whether to store provider credentials in a coding-agent console, increasing demand for tighter key-scoping, rotation, and account-use monitoring.
  • Model providers whose keys were stored in the Console may face support and abuse-response work from customers investigating charges or account restrictions tied to compromised credentials.

Third-order effects

  • If coding agents increasingly centralize access to models and developer services, their credential stores become a security boundary equal to the code and infrastructure they can reach.
  • The pattern points toward agent platforms competing on verifiable credential isolation and incident response, not only coding capability.

The trend: Coding agents are becoming high-value security intermediaries because they combine powerful model access with stored credentials and connections to developer infrastructure.

Discussion

  • @sudoingx @sudoingx on x
    holy shit, opencode got hacked and it's officially fu*ked ‘a large scale distillation attack, 1.4% of console users hit’ and people got drained, one user says his openai and anthropic keys, used only in opencode, ran up over $400 overnight, another replied $1,700. who compensates…
  • @opencode @opencode on x
    We had a security breach last night related to a large scale distillation attack that impacted 1.4% of OpenCode Console users We have notified them all this morning via email. If you did not get an email you were not impacted, it was a subset of users who had external providers l…
  • @mweinbach Max Weinbach on x
    Can confirm My OpenAI and Anthropic balances got drained, Google account got limited and drained a bit and OpenCode did email me