Skip to content
See the World Through ScienceA project of ALLATRA

Cursor Says a Key It Gave a Supplier Led to the Tampered Claude Code Extension

AI & Technology

Republish this story

Our work is licensed under Creative Commons BY-NC 4.0. You may republish this piece for free — with credit to ALLATRA Media and a link to the original, unedited beyond length trims, and not for commercial use.

Read the full license

An aerial view over downtown San Francisco, with glass office towers above dense city blocks and the bay beyond.
Downtown San Francisco from the air on Aug. 4, 2025. Anysphere, the company behind Cursor, is based in the city (illustrative)."View from Salesforce Tower 2" by Mx. Granger, via Wikimedia Commons, CC0

Cursor said on Nov. 13, 2026, that the breach behind a tampered copy of Anthropic's Claude Code extension began with an access key it had itself issued to Fireworks AI, a model-serving vendor, and that Fireworks exposed the key. The post closes a two-week investigation opened when Cursor disclosed the incident Oct. 29, 2026.

The part for users to act on is two version numbers. Cursor puts at no more than 5,000 the users who asked for specific cached versions that day and may have received the tampered build, which was up for approximately 11 hours. How many actually received it is not stated. Anyone who installed Anthropic.claude-code 2.1.312 or 2.1.313 in that window is asked to follow the company's security notice, which warns that uninstalling the extension alone may not be enough.

In Cursor's account, the attacker used the key to copy data from a read-only storage bucket the company shared with Fireworks. The bucket held logs of past coding sessions, mostly from 2025, none of them in Privacy Mode, and a few still carried credentials that had not been stripped out. By the company's own count, fewer than 0.01% of customers had API credentials exposed. Those credentials led to outside cloud services Cursor uses, and from there to archived non-production source code and support data.

Among users not in Privacy Mode, Cursor puts the share whose logs were exposed at under 0.05%, and says it notified each of them. By its account, the editor's official updates, its release signing keys and its production systems were untouched, as was Open VSX, the marketplace's public source. No outside assessment has been published.

What the tampered build did was already known: Microsoft said it planted an SSH backdoor on machines that installed it, which we reported Oct. 31, 2026. The origin, the exposure window and the scope figures are new.

Cursor says it believes the incident is contained, and that the last attacker activity it saw was Nov. 1, 2026. It has moved all inference traffic off Fireworks, deactivated the key and rotated credentials across its internal systems.

Sources

Spot an error?

Spot an error?

Report an error

Spotted a mistake on this page? Tell us what's wrong and our editors will take a look.

What kind of problem?

Only if you'd like us to be able to follow up. We won't use it for anything else.

We correct mistakes openly. Select any text to flag it. Fixes are logged under our Corrections Policy.

Report an error

Reporting on

Cursor Says a Key It Gave a Supplier Led to the Tampered Claude Code Extension

What kind of problem?

Only if you'd like us to be able to follow up. We won't use it for anything else.

We read every report. Corrections are logged publicly.