IncidentSupply chain
A tampered Claude Code extension in Cursor's marketplace planted an attacker's SSH key, a reverse tunnel and persistence
Cursor reported that modified copies of the Claude Code extension, versions 2.1.312 and 2.1.313, were available in its VS Code extension marketplace from about 2:27am to 1:35pm Pacific time on October 29, 2026, and that they were not developed by Anthropic. Microsoft says the packages were never published to the Visual Studio Marketplace or npm. Its analysis of the injected JavaScript shows a loader that ran before the extension's own code: it collected the host name, user name, operating system, home and working directories, global Git email and up to forty environment variable names matching words such as KEY, TOKEN, SECRET, AWS or GCP (not the values); appended an Ed25519 key with the comment svc-telemetry to authorized_keys and tried to enable SSH; opened a reverse SSH tunnel to the workstation's port 22 with host-key checking off, retrying every 60 seconds; and persisted through a LaunchAgent named com.apple.sysmond.plist on macOS, an @reboot crontab entry on Linux, and a scheduled task named SysMon asking for SYSTEM rights on Windows, with a sysmon.cmd fallback in the Startup folder. A delayed callback sent the host details to 134.209.82.225. Cursor says errors and the need for administrator rights blocked SSH access on most macOS and Windows hosts, but Microsoft notes the key, persistence and reporting could still be planted. Help Net Security quotes Cursor as saying at most 5,000 users were affected, and reports that Phorion found the package and published details of the payload. In an update on November 13, Cursor says an attacker obtained an access key Cursor had issued to Fireworks, exposed by Fireworks, and used it to copy coding agent traces, mostly from 2025, from a read-only storage bucket shared with Fireworks; some traces held unredacted credentials, and less than 0.01 percent of customers had API credentials exposed. From those credentials the attacker reached some of the SaaS tools Cursor uses, including archived non-production code repositories and support data, and with a stolen credential placed the tampered copies directly on the cache that serves Cursor's marketplace. Cursor says Open VSX, the marketplace source, never had the malware, no release signing keys were exposed, and the last attacker activity it saw, on November 1, was blocked. It names no attacker.
Replay the attack step by step in the Learning Center
How it happened
- A tampered build of a trusted extension was listed under the official name in one editor's marketplace, so installs and auto-updates pulled it in.
- The loader ran as soon as the extension loaded, with the developer's rights, before any of the extension's own code.
- It added a remote login key and a reverse tunnel, then hid its persistence under names that look like system monitoring.
Impact
Developers who installed or updated to 2.1.312 or 2.1.313 from Cursor's marketplace on October 29 may have an attacker's SSH key, startup items and a reporting callback on their machines, and had host details and secret variable names sent out.
The fix
Cursor removed the versions, shut its marketplace down, audited access, rotated its keys, rebuilt the marketplace and had the attacker's server taken offline. It has since moved all inference off Fireworks, deactivated the key, rotated every credential across its internal systems, added secret scanning and redeployed its production infrastructure, and has told customers whose keys were exposed which ones to rotate. On affected machines, preserve evidence, isolate the host, remove only the svc-telemetry key after checking its fingerprint, inspect and remove the startup items, stop the tunnel processes and delete the .stk_ files, then rotate credentials and sessions from a trusted system; Cursor warns that uninstalling the extension may not be enough and suggests considering a rebuild.
Lessons
- The same extension name can mean different files in different marketplaces; know which one your editors install from.
- An extension update is code running as you; restrict publishers and wait a while before new versions roll out.
- Cleaning up a backdoor means checking keys and startup items, not only removing the package.