Backdoor in Claude Code for VS Code extension on the Cursor Marketplace
Source Entity
Hacker News
A malicious backdoor has been discovered in the Claude Code extension for VS Code hosted on the Cursor Marketplace. The compromised version, 2.1.313, installs persistent SSH access across major operating systems, prompting immediate removal and security audits.
Security Alert: Compromised Claude Code Extension
A severe supply chain security incident has been identified involving the 'Claude Code' extension for Visual Studio Code, specifically targeting users of the Cursor Marketplace. Security researchers at Phorion detected a malicious backdoor embedded within version 2.1.313 of the extension bundle. This vulnerability is particularly dangerous as it facilitates the installation of a persistent Secure Shell (SSH) backdoor, granting unauthorized remote access to compromised systems running macOS, Linux, or Windows.
The Mechanics of the Backdoor
The attack represents a sophisticated supply chain compromise where a trusted development tool was weaponized to deliver a remote access trojan. Upon execution, the backdoored extension attempts to configure SSH credentials and establish persistence mechanisms on the host machine. By embedding itself within the extension's update or installation lifecycle, the malicious payload effectively bypasses standard perimeter defenses, operating with the privileges of the user running the IDE.
Implications for Developers and Organizations
For software development organizations, this incident highlights the inherent risks of relying on third-party marketplaces for IDE extensions. The Cursor Marketplace, which mirrors many VS Code extensions, inadvertently served as a distribution vector for this threat. When a developer installs a malicious extension, they essentially grant the code permission to interact with local files, environment variables, and SSH keys, which are critical assets for any engineering team. Organizations that utilize Claude Code are urged to immediately audit their environments for version 2.1.313 and initiate incident response protocols if the artifact is found.
Response and Mitigation
In response to the discovery by Phorion, the Cursor team has taken swift action to remove the malicious release from their marketplace. Furthermore, related NPM and VS Code versions associated with the compromised bundle have been pulled to prevent further propagation. While these reactive measures are necessary, the event serves as a stark reminder that even 'official' extensions can be compromised if the upstream supply chain or marketplace ingestion process is not sufficiently hardened.
Broader Cybersecurity Context
This incident is part of a growing trend of 'malicious dependency' and 'extension poisoning' attacks targeting software developers. By targeting the tools that developers use daily, threat actors gain high-value access to source code repositories, cloud infrastructure credentials, and private keys. As AI-powered coding assistants like Claude Code gain traction, they become primary targets for attackers seeking to leverage the high level of trust developers place in these productivity tools.
Future Outlook and Conclusion
Moving forward, the industry must prioritize 'Zero Trust' principles for IDE extensions. Developers and security teams should implement stricter sandboxing for extensions, perform regular integrity checks on installed packages, and monitor outbound network traffic for suspicious SSH activity. While the removal of the malicious version mitigates the immediate threat, the discovery underscores the need for continuous vigilance in the software supply chain to prevent similar future compromises.
Multiple Citing Sources