Technology · Checked 15 November 2026

A leaked vendor key let attackers plant a fake extension in Cursor

Cursor said on 13 November 2026 that an access key exposed by its inference vendor Fireworks AI let attackers plant tampered Claude Code extension builds in its marketplace on 29 October, reaching up to about 5,000 users.

Explore the six-scene explainer

Key takeaways

Sourced figures and status

PeriodFigure or statusSource
Entry pointAn access key Cursor had issued to its inference vendor Fireworks AI was exposed. It gave read access to a shared storage bucket, from which the attacker copied historical coding-agent records containing further credentials.Cyber Security News, How a leaked Fireworks AI key led to a backdoored extension · 2026-11-13
29 OctoberTampered builds of the Claude Code extension, versions 2.1.312 and 2.1.313 for Windows and macOS, were placed in the cache serving Cursor’s marketplace and removed after about 11 hours.Cyber Security News, How a leaked Fireworks AI key led to a backdoored extension · 2026-11-13
UsersCursor says up to about 5,000 users may have received a tampered build; one outlet reported about 1,200 installations.Cyber Security News, How a leaked Fireworks AI key led to a backdoored extension · 2026-11-13
ResponseCursor revoked the vendor’s access, moved inference traffic away from Fireworks, rotated internal credentials and rebuilt the extension marketplace. It says it blocked the last attacker activity on 1 November.Business Upturn, Cursor says exposed Fireworks key led to extension attack · 2026-11-13

What was not affected

Cursor says official app releases, customer code repositories and Privacy Mode data were not affected. The hidden code collected host and user details and tried to install a persistent remote-access backdoor. Source and context.

What is still unknown

Fireworks has not published a detailed account of how the key was exposed, and outside counts of affected users differ from Cursor’s estimate. Source and context.

Charts, maps and diagrams from the explainer

Flow diagram: One exposed key opened a chain of access — Vendor key leaked. Cursor said an access key it had issued to its inference vendor, Fireworks AI, was exposed.
One exposed key opened a chain of access — Vendor key leaked Cyber Security News, How a leaked Fireworks AI key led to a backdoored extension · 2026-11-13
Bar chart: Up to 5,000 users may have got a bad build. On October twenty-ninth, tampered builds of the Claude Code extension reached Cursor’s marketplace.
Up to 5,000 users may have got a bad build Cyber Security News, How a leaked Fireworks AI key led to a backdoored extension · 2026-11-13
Timeline: The fake versions were live for about 11 hours — ≈11 hours live. The fake versions were removed after about eleven hours.
The fake versions were live for about 11 hours — ≈11 hours live Cyber Security News, How a leaked Fireworks AI key led to a backdoored extension · 2026-11-13
Flow diagram: Cursor cut the vendor off and rebuilt its store — Marketplace rebuilt. Cursor revoked the vendor’s access, moved inference traffic away from Fireworks, rotated credentials and rebuilt its extension marketplace.
Cursor cut the vendor off and rebuilt its store — Marketplace rebuilt Business Upturn, Cursor says exposed Fireworks key led to extension attack · 2026-11-13
3D graphic: A supply-chain attack through a vendor — Contained, says Cursor. Cursor says official app updates, customer code and Privacy Mode data were not affected, and that the incident is contained.
A supply-chain attack through a vendor — Contained, says Cursor MLQ.ai, Hackers used a key exposed at Fireworks AI · 2026-11-13

Watch them animate in the narrated explainer

Frequently asked questions

How did attackers get into Cursor’s marketplace?

An access key Cursor had issued to its inference vendor Fireworks AI was exposed. It gave read access to a shared storage bucket, from which the attacker copied historical coding-agent records containing further credentials.

How many Cursor users were affected?

Cursor says up to about 5,000 users may have received a tampered build; one outlet reported about 1,200 installations.

Sources and reporting scope

Cyber Security News, How a leaked Fireworks AI key led to a backdoored extension. 2026-11-13. Summary of Cursor’s 13 November investigation update: entry point, tampered versions, user count and exposure window. In English.

Business Upturn, Cursor says exposed Fireworks key led to extension attack. 2026-11-13. Cursor’s response: vendor access revoked, inference moved, credentials rotated and marketplace rebuilt. In English.

MLQ.ai, Hackers used a key exposed at Fireworks AI. 2026-11-13. What the hidden code did and what Cursor says was not affected. In English.

DEV Community, Cursor’s security incident explained. 2026-11-14. Developer explainer on the attack chain; secondary analysis of Cursor’s report. In English.

As of 15 November 2026. Figures come from Cursor’s investigation update as reported by the outlets listed; the user count is Cursor’s upper estimate and other reports differ. Fireworks has not published a detailed account. The attack chain is schematic.