ORBITRUM← Back to Signals

Cursor · security

Cursor Says Malicious Extension May Have Reached 5,000 Users

By Orbitrum

Cursor's marketplace distributed a maliciously modified Claude Code extension for approximately 11 hours, potentially affecting up to 5,000 users and exposing developer systems to data collection and attempted SSH backdoor installation; the incident creates a platform-security and customer-trust risk, although Cursor says it removed the package, rebuilt its marketplace and found no other altered extensions.

Illustration of a software development environment displaying a security warning over a code editor extension, representing the malicious extension discovered and removed from Cursor's marketplace.

What happened in Cursor's extension marketplace?

On October 29, 2026, Cursor distributed a maliciously modified version of Anthropic.claude-code 2.1.313 through its VS Code extension marketplace for approximately 11 hours, potentially affecting up to 5,000 users; the malicious version was not developed by Anthropic.

Orbitrum Investor Impact

Why does the security incident matter to Cursor's business?

The incident exposed a supply-chain security weakness in Cursor's extension distribution system, potentially undermining developer and enterprise customer confidence in the platform's security controls, although Cursor says its investigation found no other compromised marketplace extensions.

Did attackers successfully gain remote access to affected computers?

The malicious extension attempted to install a persistent SSH backdoor, but Cursor says the critical remote-access step required administrator privileges and would fail on most macOS and Windows machines; the company has not disclosed how many machines, if any, successfully established the remote connection.

What information could the malicious extension collect?

The extension collected host and user information, including hostnames, usernames, operating-system details, working directories, configured Git email addresses, public IP addresses and environment-variable names, and transmitted host details to an attacker-controlled server that Cursor says has since been taken offline.

What has Cursor done to contain the incident?

Cursor removed the malicious version, blocked further distribution, audited its marketplace, rotated its keys, worked with the hosting provider to disable the attacker's server and rebuilt and restored the marketplace; it says no other extensions were altered.

What happens next for potentially affected users?

Cursor says it will contact potentially affected users directly and recommends checking machines that installed version 2.1.313 during the October 29 exposure window, because uninstalling the extension alone may not remove installed persistence mechanisms.

Sources

Original signal: Reuters ↗

Continue researching

Open Cursor in the Orbitrum app

Review its expert coverage and continue your research in Orbitrum. Access to full expert research depends on each expert's offer.

Open Cursor in the Orbitrum app

Prefer a public overview? View Cursor's public project profile

See more Orbitrum in Google

Add Orbitrum as a Preferred Source to make our research more likely to appear for you in Google Search.