Cursor Removes Malicious Claude Code Extension

The platform removed a compromised extension that exposed user data and granted unauthorized remote access.

Updated on Oct. 30, 2026 in Cybersecurity

Isometric editorial illustration of an abstract geometric structure, representing the structural security and marketplace architecture of a digital platform.
Cursor recently removed a malicious version of the Claude Code extension from its platform after discovering it targeted approximately 5,000 user systems. AI Illustration. Upload story photo >

Live Poll

Do you trust the security protocols of third-party software marketplaces you use?

Cursor recently removed a malicious version of the Claude Code extension from its marketplace after discovering it targeted up to 5,000 users. The compromised software attempted to exfiltrate system data and establish unauthorized remote access.

Why it matters

The incident highlights vulnerabilities within developer tool marketplaces where third-party extensions can be used to compromise user systems. By quickly rebuilding its marketplace, Cursor aims to contain the threat and prevent further unauthorized access.

The malicious extension was active for approximately 11 hours and targeted hostnames, usernames, operating systems, and public IP addresses. Cursor confirmed that no other extensions on the marketplace were impacted by this specific breach.

The players

Cursor

Cursor is a popular AI-powered code editor that provides an integrated marketplace for developers to find and install various productivity extensions.

The details

The malicious extension operated by attempting to harvest sensitive environment details while establishing a back-door for external remote access. In response, the platform provider shut down the entire marketplace to perform a full system rebuild and block the distribution of the tampered code.

Timeline

  1. The malicious extension was active on the marketplace from 2:27 a.m. PT to 1:35 p.m. PT on Thursday, October 29, 2026.

The Tech Race

This breach highlights the security challenges inherent in maintaining trusted developer marketplaces within the broader Visual Studio Code (VS Code) extension marketplace ecosystem. It emphasizes how platforms must evolve their defensive measures to combat sophisticated supply chain attacks.

Developers who installed the affected extension may need to audit their system logs for unauthorized remote connections or leaked IP addresses. Users should practice caution by verifying the source and reputation of any third-party code before integrating it into their workflow.

The takeaway

Developers should treat all third-party marketplace extensions as potential vectors for system compromise and maintain strict access controls. Regularly auditing installed extensions and monitoring for anomalous network activity are essential practices for modern software engineering.

Further reading

Learn more about securing your development environment in the Cybersecurity section.

Live Poll

Do you trust the security protocols of third-party software marketplaces you use?