CSTI · Global News繁體中文
2026-11-14

Cursor Breach: Fireworks Key Leak Led to Malicious Extension Potentially Reaching up to 5,000 Users

Cursor Breach: Fireworks Key Leak Led to Malicious Extension Potentially Reaching up to 5,000 Users

Cursor on November 13 publicly connected the dots of its October security incident for the first time. It started at Fireworks AI, one of its model-hosting suppliers. An access key Cursor had issued to Fireworks was exposed, and an attacker used it to copy a read-only storage bucket holding coding agent traces, mostly from 2025, from sessions not in Privacy Mode. A small number of traces contained unredacted credentials; less than 0.01% of customers had API credentials exposed.

Starting from those credentials, the attacker reached some of Cursor's SaaS tools, accessing select archived non-production source code repositories, limited customer support data and email conversations, product usage metrics, and some credentials users had sent to support. On October 29, the attacker placed malicious copies of Anthropic's Claude Code extension (versions 2.1.312 and 2.1.313) on the cache serving Cursor's VS Code extension marketplace. The upstream marketplace, Open VSX, was never touched.

The malicious extension tried to install a persistent SSH backdoor. It collected host and user information (hostname, username, operating system, home directory path, Git email and public IP address) and tried to add an attacker-controlled SSH key, labelled svc-telemetry, to enable the local SSH service and open a reverse SSH tunnel. At most 5,000 users potentially received the malicious build during the roughly 11-hour window (2:27 a.m. to 1:35 p.m. Pacific Time on October 29). Cursor said enabling the local SSH service needs administrator rights, which the extension did not have on most macOS and Windows machines.

Cursor says the incident is contained, with the last attacker activity seen on November 1, now blocked. It moved all inference traffic off Fireworks and deactivated the key. Privacy Mode prompts and code, customer code repositories, production systems and the Cursor app itself were not affected. Cursor warned that uninstalling the extension alone may not be enough for anyone who installed the affected versions, and told them to follow five remediation steps in its security notice, including checking SSH authorized keys, isolating affected machines and rotating credentials.

Source · Cursor