Title: Cursor Pins Trojanized Claude Code Extension on a Fireworks AI Key Theft, Says Incident Is Contained
Summary: Cursor has published an investigation update on the October 29 incident in which malicious, unauthorized copies of Anthropic’s official Claude Code extension appeared on the cache serving its VS Code extension marketplace — and the root cause, per the company, is a stolen vendor key. Per the company, the entry point was an access key Cursor itself had handed to Fireworks AI: once Fireworks disclosed its own breach, that key fell into the attacker’s hands, and it was used to pull data out of a read-only storage bucket the two companies maintained for exchanging model-training data. Stored inside was a narrow set of coding-agent records — most of them dating from 2025 and drawn only from sessions where Privacy Mode was off — and in a handful of those records the credentials had never been scrubbed, which is how API keys belonging to under 0.01% of customers leaked. Starting from those credentials, the attacker reached select SaaS tools Cursor uses and pulled archived non-production source repositories, limited customer support data and email conversations, product usage metrics, summaries of some coding agent conversations, and some credentials users had sent to support. On October 29 the attacker used a stolen credential from that exposed data to place the trojanized extension directly on the marketplace’s serving cache — Anthropic did not publish the copy and its product was not vulnerable, and the Open VSX marketplace source never contained the malware. Cursor calculates that no more than 5,000 users — the people who asked for particular cached builds that day — could have been served the malicious extension, which presented itself as Anthropic.claude-code 2.1.312 or 2.1.313 and tried to plant a persistent SSH backdoor; it stayed in place for roughly 11 hours before Cursor pulled it. Cursor notified affected users on October 30 with indicators of compromise and checking scripts, cautions that simply removing the extension may not fully clean an affected machine, and asked the third-party services whose keys were exposed to revoke them. The company says the last attacker activity it observed was November 1 and was blocked, and it has moved all inference traffic off Fireworks, deactivated the vendor key, rotated credentials, and rebuilt the marketplace store. Not affected, per Cursor: Privacy Mode users’ prompts and code, production systems, the Cursor app and its official updates, all other marketplace extensions, and customer code repositories. The blast radius from the underlying Fireworks breach keeps widening: Uber has confirmed attackers used compromised service-provider credentials to steal thousands of drivers’ license records (with TechCrunch identifying the provider as Fireworks AI), and Notion confirmed last week its data was stolen in the same incident.
References: