OpenCode Console says the breach occurred last night and involved a large-scale distillation attack. Affected users were notified by email this morning; those who did not receive an email were not impacted. The company says the affected group was a subset of users who had external providers linked. The incident is described as ongoing, so the company says it cannot share more details at this point. It states it is working with Anthropic, OpenAI, and Google on remediation.

AI summary of the linked source — not editorial content.

Story signal · how it spread on X · via Elfa

as of
Spread
i
Distinct X and Telegram accounts Elfa counted behind this story’s reports, summed over the thread. Not posts, not impressions.
3 accounts

first post
Leviathan +5.3 h later

ANTHROPIC reaction
i
Price change from the first post to 24 hours later (Hyperliquid). BTC over the same window is shown so a market-wide move is not mistaken for a reaction to this story. Not advice.
+0.6% 24h after post

$1,878 → $1,888
BTC −0.1% same window

OPENAI reaction
i
Price change from the first post to 24 hours later (Hyperliquid). BTC over the same window is shown so a market-wide move is not mistaken for a reaction to this story. Not advice.
+1.1% 24h after post

$1,490 → $1,506
BTC −0.1% same window

Thread · 1 event
  1. First reportOpenCode reports a breach affecting API keys for some users3 acc.
  2. Leviathan published this article

All times UTC.

Cited posts

  • @captainPURU Captain PURUOn X ↗

    Oh look, API keys need to be secured properly https://t.co/glzBPlunK5

  • @dani_avila7 Daniel SanOn X ↗

    I’m very selective about which third-party services I trust with my API keys The risk is simply too high, regardless of what opencode’s postmortem reveals OAuth should be the standard, otherwise, API keys should have strict token limits, usage caps, and per-service alerts… https://t.co/rWnEQiZhlf

  • @karankendre KaranFirst reportOn X ↗

    The main question is why are you storing users API keys on your servers? Shouldn’t they be stored locally? or am I missing something https://t.co/gfget2e6iS

TradersTrader calls tracked by Elfa · not advice

Positioning · ANTHROPIC

Open106 open positions · 81 long · 25 short

Tracked accounts lean long about 97% of the time, so a long-heavy book is normal, not a signal. As of 17 Oct 05:03 UTC.

Whole crypto market, not this story

Crowding88th percentile · vs last 28 days, 50 typical
Pulse 24h8/100 · unusualness of new calls, 0–100, 50 typical, higher means more long than usual
Book97.4% long · 11,296 accounts

As of 18 Oct 01:35 UTC.

Social-monitoring data, not investment advice Elfa prices Hyperliquid post text from Xas of

Explore the topic

Loading related coverage…

Explore the full feed

Comments

Loading comments…