Cursor identified malicious versions 2.1.312 and 2.1.313 of the Anthropic.claude-code extension in its VS Code Extension Marketplace. The packages targeted Windows and macOS and were available for about 11 hours on October 29, 2026. Cursor says the versions were not developed by Anthropic. Cursor’s security notice explains how to check for the payload and remove its remaining artifacts.
Which versions and platforms were affected
Cursor says both versions were available from about 2:27 a.m. to 1:35 p.m. Pacific Time on October 29. It removed them, shut down its marketplace as a precaution, reviewed access, rotated keys, rebuilt the marketplace, and restored it. Cursor’s notice identifies Windows and macOS packages.
What the extension tried to do
The payload attempted to add an attacker-controlled SSH key marked svc-telemetry, create persistence so scripts could run again, open a reverse SSH tunnel, and send information about the computer to an attacker-controlled server. Cursor lists collected details including the hostname, username, operating system, architecture, home-directory path, working directories, configured Git email, public IP address, and environment-variable names. Cursor’s notice says the attacker’s server was taken offline.
Cursor says the SSH activation step generally required administrator privileges that the extension did not have on most Windows and macOS machines. That did not prevent the key, persistence files, or host-detail transmission from occurring. Phorion’s technical analysis describes a macOS logic flaw: an unprivileged check could return an administrator-access error with a successful exit status, so the payload could skip the step that would enable Remote Login. The same analysis describes a Windows setup path that routed a PowerShell command through /bin/sh.
Phorion says the payload selected matching environment-variable names, not their values. Cursor cautions that this does not rule out later access to credentials if a backdoor path worked. The extension’s payload ran when its module loaded, so opening a Claude conversation was not required.
How to check for the SSH key
Search the relevant SSH authorized_keys file for svc-telemetry. Cursor says a match means the machine is affected. On macOS, its check is:
grep -qs svc-telemetry ~/.ssh/authorized_keys
On Windows, Cursor’s PowerShell check covers the user’s SSH authorized_keys file and C:\ProgramData\ssh\administrators_authorized_keys. A check for this key is useful even if the extension has since been updated or removed, because those actions may leave separate persistence scripts behind.
What to do if you find the marker
Follow Cursor’s remediation guidance to remove the unauthorized key, persistence files, and any running tunnel processes. Cursor says its macOS remediation script should be run as the affected user, while its Windows script should be run in PowerShell as Administrator. If there is evidence the payload ran or installed a backdoor, Cursor advises isolating the host, assessing whether it needs to be rebuilt, and rotating credentials and sessions accessible from it using a trusted system. Cursor’s remediation instructions