Skip to the content
AI and Cybersecurity Learning and Practice Center Test automation Open the Learning Center

NewsIncident

A tampered Claude Code extension in Cursor's marketplace planted an attacker's SSH key and a reverse tunnel on developers' machines

Cursor reported that modified copies of the Claude Code extension, anthropic.claude-code versions 2.1.312 and 2.1.313 for Windows and macOS, were available in its own VS Code extension marketplace from about 2:27am to 1:35pm Pacific time on October 29, and that they were not developed by Anthropic. Microsoft, which analyzed the injected JavaScript, says the packages were never on the Visual Studio Marketplace or npm. The loader ran as the extension loaded: it collected the host name, user name, system details, Git email and up to forty names of environment variables that looked like keys or tokens (not their values), added an attacker SSH key with the comment svc-telemetry to authorized_keys, tried to turn on the SSH service and open a reverse tunnel to the workstation's port 22, and set up persistence (a LaunchAgent named com.apple.sysmond.plist on macOS, a crontab entry on Linux, a scheduled task named SysMon on Windows). Cursor says the tunnel usually failed without administrator rights, but the key, persistence and reporting could still be planted. Cursor pulled the versions, shut its marketplace down, audited access, found no other tampered extensions, rotated its keys, rebuilt the marketplace and had the attacker's server taken offline. Help Net Security quotes Cursor as saying at most 5,000 users were affected. On November 13 Cursor said how it happened: an access key it had issued to Fireworks, exposed by Fireworks, let an attacker copy coding agent traces that held some unredacted credentials, and from those the attacker reached some of Cursor's SaaS tools and, with a stolen credential, put the tampered copies straight onto the cache that serves its marketplace. Cursor says less than 0.01 percent of customers had API credentials exposed, the last attacker activity it saw was blocked on November 1, and it has moved its inference off Fireworks.

Why it matters

An editor's extension runs with the developer's rights, and an update arrives without anyone reading it. Uninstalling is not enough here: check authorized_keys and startup items, and treat the machine's credentials as exposed if the loader ran.

Sources

Read it with the rest of the news in the Learning Center