One exposed key opened a chain of access

Chain · As of 15 November 2026

Vendor key leaked
AS OF 15 NOVEMBER 2026 · DATED SOURCES
Transcript

Full transcript

The narration below matches the explainer. Its original reporting dates and qualifications still apply.

Read the companion article

One exposed key opened a chain of access

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

Cursor said an access key it had issued to its inference vendor, Fireworks AI, was exposed. Attackers used it to copy old coding-agent records containing more credentials.

Cyber Security News, How a leaked Fireworks AI key led to a backdoored extension · 2026-11-13

Up to 5,000 users may have got a bad build

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

On October twenty-ninth, tampered builds of the Claude Code extension reached Cursor’s marketplace. Cursor says up to about five thousand users may have received them.

Cyber Security News, How a leaked Fireworks AI key led to a backdoored extension · 2026-11-13

The fake versions were live for about 11 hours

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

The fake versions were removed after about eleven hours. Cursor says it blocked the last attacker activity on November first and published its findings on November thirteenth.

Cyber Security News, How a leaked Fireworks AI key led to a backdoored extension · 2026-11-13

Cursor cut the vendor off and rebuilt its store

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

Cursor revoked the vendor’s access, moved inference traffic away from Fireworks, rotated credentials and rebuilt its extension marketplace.

Business Upturn, Cursor says exposed Fireworks key led to extension attack · 2026-11-13

A supply-chain attack through a vendor

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

Cursor says official app updates, customer code and Privacy Mode data were not affected, and that the incident is contained.

MLQ.ai, Hackers used a key exposed at Fireworks AI · 2026-11-13

SOURCES AND NOTES

Cyber Security News, Business Upturn and MLQ dot A I summarised Cursor’s update. A DEV Community post explained the attack chain.

Cyber Security News, How a leaked Fireworks AI key led to a backdoored extension · 2026-11-13

Source links

All Explainers
[00:00]
Read the full article

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

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.

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.