Flash

Flash·Safety & Risk·2026-11-15 20:14

Cursor Traces Breach to Fireworks Key Leak; Fake Claude Code Extension Reached Up to 5,000 Users

Cursor published on Nov 13 the findings of its October security incident: an attacker used an access key issued to inference vendor Fireworks to copy coding-agent traces from a shared storage bucket, found unredacted credentials in them, and on October 29 placed a tampered Claude Code extension in its VS Code extension marketplace cache.

A bright developer workspace with a laptop showing a code editor on the desk
AI-generated illustration

What happened

The incident started at Fireworks. Cursor says an attacker obtained an access key it had issued to Fireworks, and that the key was exposed by Fireworks; the attacker used it to copy a read-only storage bucket the two companies shared, which held a limited set of coding-agent traces, mostly from 2025 sessions outside Privacy Mode, a small number of which contained credentials that had not been redacted.

The attacker used those credentials to reach some of Cursor’s SaaS tools and obtained archived non-production source repositories, customer support data and email conversations, product usage metrics, summaries of some coding-agent conversations, and credentials users had sent to the support team. On October 29, the attacker used a stolen credential to place tampered copies of Anthropic.claude-code versions 2.1.312 and 2.1.313 directly into the cache that serves the extension marketplace.

The tampered builds sat in the cache for about 11 hours (2:27 a.m. to 1:35 p.m. Pacific Time on October 29), and at most 5,000 users who requested the affected cached versions may have received them. Cursor says Anthropic did not publish these copies, the issue is not in Anthropic’s product, and the marketplace source Open VSX never contained the malware; Microsoft confirmed the malicious packages were not distributed through its Visual Studio Marketplace or npm. Cursor says the last attacker activity it has seen was on November 1, and it was blocked.

Key facts

  1. Origin: An access key issued to Fireworks was exposed, and coding-agent traces in a shared read-only storage bucket were copied
  2. Credentials: Fewer than 0.01% of customers had API credentials exposed; fewer than 0.05% of users had traces exposed
  3. Tampered builds: Anthropic.claude-code versions 2.1.312 and 2.1.313 sat in Cursor’s extension marketplace cache for about 11 hours on October 29
  4. Exposure: At most 5,000 users may have received the tampered builds; Cursor says follow the steps in its October 30 security notice, as uninstalling alone may not be enough
  5. Not affected: Prompts and code in Privacy Mode, customer code repositories, production systems, the Cursor app and its official updates, and release signing keys
  6. Response: All inference traffic moved off Fireworks, the key deactivated, all internal credentials rotated, the extension marketplace rebuilt, external forensic investigators engaged
  7. Attribution: “Exposed by Fireworks” is Cursor’s account; Fireworks’ November 9 update does not mention Cursor

Why it matters

The incident links a vendor key leak, credentials inside agent traces, and extension-marketplace tampering into one chain, making traces a new carrier of credentials; Fireworks’ account has not yet been matched against Cursor’s version, leaving one part of the attribution open.
Useful Tap if this story helped you
Send to a friendMakes a share image for X, WeChat, Telegram and more

SourcesCursor official blog (Nov 13, 2026); iFynx (Nov 14, 2026). This article is compiled from public information and does not constitute investment advice.

From HIMIAO Horizon · himiao.ai

Grab todayOpenAI Codex for Students: $100 in Free CreditsHIMIAO Picks →

Follow HIMIAO Horizon

No sign-up · Unsubscribe any time

Email

Notifications

A ping on your phone or computer when the brief is out. No email needed.

HIMIAO PicksWeekly freebies: one email every Friday, a 5-minute read

Comments

  1. Loading comments…
Ask the cat