4 Nov 2026, Wed

Supply Chain Attack Targets Developers via Malicious Claude Code Extension on Cursor Marketplace

In a sophisticated supply chain attack that highlights the growing vulnerabilities within developer ecosystems, users of the Cursor code editor were recently targeted by malicious versions of Anthropic’s Claude Code extension. The incident, which unfolded on October 29, saw unauthorized versions of the popular tool distributed through the Cursor VS Code Extension Marketplace, potentially exposing thousands of developer environments to remote access threats.

The malicious activity involved versions 2.1.312 and 2.1.313 of the extension, which were made available to the public for approximately 11 hours before the breach was identified and mitigated. Security researcher Kevin Beaumont, who closely monitored the incident, noted that roughly 5,000 developer systems may have downloaded the compromised versions during that window. The attack was specifically engineered to compromise both macOS and Windows platforms, utilizing embedded JavaScript code designed to execute automatically upon the loading of extension modules.

Understanding the Nature of the Compromise

It is critical to distinguish that these tampered versions were not the product of Anthropic, nor were they distributed through standard, reputable channels such as the Microsoft Visual Studio Marketplace, Open VSX, or the NPM registry. The threat actor, leveraging unauthorized access to the Cursor marketplace, successfully published a malicious, masquerading copy of the Claude Code tool.

Felix Rieseberg, representing Anthropic, clarified the scope of the incident in a public statement, emphasizing that the company’s official channels remained untarnished. "A malicious actor used access to Cursor’s marketplace to publish a tampered copy of the Claude Code extension, which we didn’t build or publish. The versions on our official channels are not affected, and this only impacts Cursor users," Rieseberg confirmed.

In a move to preempt further confusion and ensure the integrity of its toolset, Anthropic moved quickly to update its legitimate Claude Code extension to version 2.1.314, effectively overriding the compromised versions and providing a clean, verified update for its user base.

Cursor’s Response and Forensic Findings

Cursor moved swiftly to address the security breach once the malicious activity was identified. The company immediately removed the rogue extension from its marketplace and suspended its operations entirely to conduct a thorough forensic investigation. During this period of downtime, Cursor’s security team performed a comprehensive audit of the marketplace to ensure no other extensions had been similarly compromised.

As part of their remediation efforts, the platform operators rotated all internal security keys and completely rebuilt the marketplace infrastructure before reopening it to the public. Furthermore, Cursor collaborated with the cloud service provider hosting the attacker’s command-and-control server to force it offline, effectively severing the connection between the infected machines and the malicious operators. Cursor has stated unequivocally that there is no evidence suggesting other extensions or the official distribution channels were impacted by this specific campaign.

Technical Analysis of the Malicious Payload

Detailed technical analysis, including insights provided by Microsoft, revealed that the malicious extension was designed to perform a series of invasive operations. When the extension was loaded, a JavaScript function would execute to perform host reconnaissance, gathering sensitive environmental data. The payload was programmed to collect information such as the hostname, username, operating system details, system architecture, the current working directory, and even the user’s global Git email address.

Beyond simple reconnaissance, the malware attempted to establish a persistent presence on the host machine. Microsoft reported that the loader attempted to install a malicious SSH key, enable the local SSH service, and configure a reverse SSH tunnel to allow the attacker persistent remote access. A secondary, delayed callback was also observed, which functioned to transmit the gathered host data back to the attacker’s infrastructure.

Despite the ambitious nature of the attack, the impact was partially mitigated by the limitations of the environment. Because the deployment of an SSH service on most macOS and Windows systems requires elevated administrative privileges, the malware often failed to execute its primary goal of establishing an active backdoor. On systems where the extension lacked these permissions, the attacker’s ability to log in through the reverse tunnel was effectively neutralized, though the attempt to gain access itself remained a significant security event.

Remediation Steps for Affected Developers

Cursor has issued clear guidance for developers who may have installed the compromised versions. While simply uninstalling the extension is a necessary first step, it is not considered sufficient for full remediation, as the payload may have already dropped standalone persistence scripts that continue to run in the background even after the extension is removed.

Users are advised to isolate any hosts that show signs of payload execution. The remediation process requires a manual, thorough cleaning of the environment: developers must locate and remove any unauthorized SSH keys, disable the persistence mechanisms installed by the script, and terminate any active tunnel processes. Given the nature of the intrusion, Cursor has strongly encouraged developers to evaluate whether the affected hosts should be completely rebuilt to ensure no residual backdoors remain.

To aid in this process, Cursor has released a detection script that helps users identify if their machines were exposed to the malicious code. The company has also provided a comprehensive list of Indicators of Compromise (IoCs), which security teams can use to scan their environments for evidence of unauthorized activity.

The Broader Context of Supply Chain Risks

The incident serves as a stark reminder of the inherent risks within modern software supply chains. As developers increasingly rely on third-party extensions and plugins to streamline their workflows, these tools become high-value targets for attackers. A successful breach of a developer’s local environment can provide a gateway into sensitive source code repositories, cloud infrastructure credentials, and proprietary intellectual property.

This event is not an isolated occurrence in the current threat landscape. Recent history has seen similar supply chain compromises affecting widely used tools, including LiteLLM, the AOMEI Backupper, and the Rank Math PRO WordPress plugin. In each case, attackers have exploited the trust that developers place in legitimate distribution channels, turning essential productivity tools into vectors for malware delivery.

The focus on the Cursor marketplace underscores the fact that even niche or specialized platforms are not immune to these threats. As artificial intelligence and automation tools like Claude Code continue to gain traction, the pressure on marketplace operators to implement rigorous security checks and validation processes for third-party submissions will only increase.

For the developer community, the incident highlights the importance of maintaining a "zero-trust" mindset, even toward trusted development environments. Regularly auditing installed extensions, monitoring for unusual network traffic, and maintaining a robust, up-to-date backup strategy are essential practices. As security researchers and platform providers continue to evolve their defenses, the responsibility for securing the software development lifecycle remains a shared effort between the platforms that host the code and the developers who utilize it.

As the situation stabilizes, the industry will likely see a renewed emphasis on cryptographically signing extensions and implementing more stringent automated security scans for marketplace submissions. For now, those who may have interacted with the compromised Claude Code versions on Cursor are urged to follow the official remediation guidance immediately to safeguard their development environments from further risk.