A fake Claude Code update in Cursor tried to plant an SSH key on developer machines. Run the one-line check

By George Bailey   Published: 11/02/26   4 min read

For about eleven hours on Thursday, developers who installed or auto-updated the Claude Code extension inside the Cursor editor got a copy Anthropic never built. Versions 2.1.312 and 2.1.313 tried to plant an SSH key and a reverse tunnel on the machine.

Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.

Cursor pulled it and took the attacker’s server offline, but the extension writes files outside its own folder. Removing or updating it leaves those behind, and checking takes one command.

Uninstalling the extension does not remove what it planted. Check authorized_keys for svc-telemetry.

A tampered Claude Code extension sat in Cursor’s marketplace for 11 hours

Cursor says the malicious Anthropic.claude-code 2.1.312 and 2.1.313 builds for Windows and macOS were served from its VS Code extension marketplace from about 2:27 a.m. to 1:35 p.m. Pacific time on October 29. Cursor removed them, shut the marketplace down, rotated its keys, rebuilt it and brought it back.

Microsoft Threat Intelligence analyzed the injected loader on October 30. It collects the hostname, username, OS, Git email and the names (not values) of environment variables containing words like KEY, TOKEN or SECRET. It appends an Ed25519 key labeled svc-telemetry to authorized_keys, tries to turn on the local SSH service and opens a reverse tunnel to 134.209.82[.]225, retrying every 60 seconds. Microsoft says the Visual Studio Marketplace and the npm @anthropic-ai/claude-code package were not affected, and Anthropic told Microsoft its systems were not compromised.

Cursor users on macOS and Windows who updated on October 29

The exposure is narrow: Cursor on macOS or Windows, with the Claude Code extension installed or updated from Cursor’s marketplace during that window. Cursor says turning on SSH needs admin rights the extension usually lacks, so on most machines the tunnel step failed and the attacker could not log in.

The rest still ran. The key, the startup entries and the host report were written, and the startup entries keep retrying. Developer laptops hold cloud credentials, Git tokens and SSH keys, so a planted key on one of them is worth an hour of checking.

Grep for one key name, then clean up and rotate

Forward this

For whoever manages developer laptops: a fake Claude Code extension was served in the Cursor editor’s marketplace on October 29 and tried to add a hidden SSH key. Can we check every Mac and Windows machine with Cursor for an SSH key named svc-telemetry, clean any hits with Cursor’s script, and rotate the credentials on those machines?

Details

Hunt / verify

Source: Cursor security notice; Microsoft analysis

Sources

George Bailey

George Bailey is the byline of the CyberExperts editorial desk, the team behind the CyberExperts Daily Brief. The desk covers vulnerabilities, breaches and security news from vendor advisories, CISA alerts and other primary sources, and links those sources in every story. Questions or corrections: [email protected].