Prompt & Done · BACKDOOR

Poisoned Claude Code extension on Cursor: the exact steps

On 29 Oct 2026 a tampered copy of the Claude Code extension (2.1.312 and 2.1.313) was on Cursor's extension marketplace from about 2:27am to 1:35pm PT. Cursor says up to 5,000 developers could have received it.

Checked 5 Nov 2026 against Cursor's notice and BleepingComputer. Scope: Cursor's marketplace only; Cursor has no evidence that other versions or the official distribution are affected.

1 Check for the key

macOS / Linux, in a terminal:

grep -qs svc-telemetry ~/.ssh/authorized_keys && echo "svc-telemetry key found" || echo "No key found; machine not impacted"

Windows: Cursor publishes a PowerShell check that also looks at the administrator key file.

cursor.com: Claude Code extension security notice

2 If it says found

Isolate the machine, remove the unauthorized key and the persistence, then rotate. Uninstalling the extension may not be enough: the payload can leave a key, a LaunchAgent (macOS) or a scheduled task / Startup script (Windows) and a tunnel retrying about every minute.

Cursor's remediation scripts: bash remediate-macos.sh (run as the affected user, not root) or powershell -ExecutionPolicy Bypass -File .\remediate-windows.ps1 (as Administrator), both on the notice page.

3 Rotate secrets

"Rotate credentials and sessions accessible from affected hosts, from a trusted system." Cursor notes its limited env-var collection does not rule out later credential access over the backdoor.

Good to know

BleepingComputer reports coding errors likely stopped SSH from being enabled on many machines, but the key was still written. Not affected per Cursor's notice: other extensions on the Cursor marketplace.

bleepingcomputer.com · Voice: Built with Fish Audio