Skip to content

Technology1 min read

Backdoor discovered in Claude Code VS Code extension

A malicious version of the Claude Code extension on the Cursor Marketplace attempted to install persistent SSH backdoors on multiple operating systems.

by Fini MironFounder @ Balkaris
An abstract composition printed flat in pale cool grey, steel blue, deep navy and bright mustard yellow: one thick line made of four straight segments turning at right angles as it crosses from the left edge down to the lower right, with a small square at each turn.
Drawn for this article on our own machine. It is not a photograph.

Phorion reports that a backdoor has been discovered in the official Claude Code for VS Code extension on the Cursor Marketplace. The compromise affects versions 2.1.312 and 2.1.313 of the extension. According to the security advisory, the malicious bundle attempts to install a persistent SSH backdoor across macOS, Linux, and Windows systems. Cursor has since removed the affected versions from its marketplace following the discovery.

Why it matters

This incident highlights the risks inherent in the software supply chain, particularly when developers integrate third-party extensions into their primary IDEs. Because these tools run with the same permissions as the user, a single compromised package can bypass standard perimeter defences. For Swiss businesses, this means that even trusted development workflows require active monitoring to prevent long-term unauthorised access to source code and internal infrastructure.

  • Security teams must audit all IDE extensions for recent version changes.
  • Automated scans should check for unexpected modifications to SSH configuration files.
  • Developers should avoid using marketplace extensions that lack a clear, verifiable provenance.

What to watch

You should immediately audit your development environments for Claude Code versions 2.1.312 or 2.1.313. Specifically, check your ~/.ssh/authorized_keys files for an unauthorised Ed25519 public key with the comment "svc-telemetry". If you find this key, you must remove it, delete any temporary files in your system's /tmp directory, and rotate all credentials that were accessible to that user account.

Within a year, automated audits will likely become standard. This requires developers to adopt strict identity management protocols that treat every CLI tool as a potential entry point.

Key takeaways

  • Third-party IDE extensions can bypass perimeter defences by running with user permissions.
  • Businesses must audit SSH configuration files for unauthorised public keys.
  • Development workflows require active monitoring to mitigate software supply chain risks.

Frequently asked

How can we verify if our developers are currently affected?

You should check for an Ed25519 public key with the comment 'svc-telemetry' in the ~/.ssh/authorized_keys files of all development machines.

Does this issue only affect macOS users?

No, the security advisory states the malicious bundle targets macOS, Linux, and Windows systems.