Lead story
Cursor: leaked Fireworks key led to malicious Claude Code extension
Cursor said an attacker used a key issued to Fireworks AI to obtain coding agent traces. Credentials found in them gave the attacker access to Cursor’s internal services and eventually to the extension marketplace cache. On 29 October the marketplace served a backdoored Claude Code extension for about 11 hours.
Cursor, the company behind the Cursor code editor, explained how the October breach unfolded in an update published on 13 November. BleepingComputer, Cyber Security News and ai.info, which reported on the breach, rely on Cursor’s own account.
From a key to credentials and the extension marketplace
Cursor said the attacker obtained a key that the company had issued to Fireworks AI, which provides training and inference for AI models. The key gave read access to storage that Cursor used to share data with Fireworks.
The storage held coding agent traces, mostly from 2025. They came from users who did not have Privacy Mode enabled, whose data Cursor was allowed to use for model training. Some traces still contained credentials.
With these, the attacker reached online services used by Cursor and obtained, among other things, customer support messages, credentials that customers had sent to support, and archived source code repositories that are not used in production.
Fewer than 0.05 per cent of users had traces exposed and fewer than 0.01 per cent of customers had API credentials exposed, Cursor said. The figures do not show how many people received the malware.
Backdoor in the Claude Code extension
On 29 October the attacker used a stolen credential to place modified copies of Anthropic’s Claude Code extension in the cache from which Cursor’s VS Code extension marketplace serves extensions. The affected builds were versions 2.1.312 and 2.1.313 for Windows and macOS. Anthropic’s own extension and Open VSX, the marketplace from which Cursor fetches extensions, were not compromised, Cursor said.
In a security notice published on 29 October, Cursor said the extension sent the attacker information about the machine, including the names of environment variables but not their values. It also added the attacker’s SSH key to the machine and tried to open a reverse SSH tunnel. In such a tunnel the infected machine itself connects to the attacker’s server, which lets the attacker log in to the machine through it. The malicious code tried to persist on the machine using a LaunchAgent on macOS and a scheduled task on Windows.
Up to 5,000 users who requested these versions during a window of about 11 hours may have received a malicious version, Cursor said. The figure is the potential distribution, not the number of backdoors actually installed. Coding errors and missing administrator rights prevented remote login on most machines, the company said. Microsoft’s threat intelligence unit said the code may still have written the key and the startup files, ai.info reported. The attacker’s server has been taken offline.
Cursor said the breach did not reach production systems, official updates, customer repositories or the code of Privacy Mode users. The company moved inference away from Fireworks, rotated credentials and rebuilt the extension marketplace. The attacker’s last observed activity, on 1 November, was blocked, and Cursor believes the breach is contained.
How to check your machine
The guidance applies to users who installed or updated either version from Cursor’s extension marketplace on macOS or Windows on 29 October between 02.27 and 13.35 Pacific Time. An infection shows up as a key named svc-telemetry in the SSH authorized_keys file. Uninstalling the extension may not be enough, Cursor said, because scripts left by the malicious code keep running.
Cursor’s notice includes scripts for checking and cleaning the machine. The company advises using a separate, trusted machine to rotate any credentials that were accessible from the affected machine, because the attacker may have reached them later through the backdoor. It also advises considering reinstalling the machine.
What this is based on
- Cursor confirms security breach led to malicious Claude Code extension
- Cursor Reveals How a Leaked Fireworks AI Key Led to a Backdoored Claude Code Extension
- Cursor traces security incident to exposed Fireworks key
- Cursor Traces Its October Breach to a Leaked Fireworks Key, Closing a Two-Week Investigation — Paktechstan
- Security notice — malicious version of Anthropic.claude-code (2.1.312 and 2.1.313) identified in the Cursor VS Code Extension Marketplace · Cursor