Cursor has detailed how a stolen vendor access key led to customer-data exposure and tampered copies of the Claude Code extension in its VS Code extension marketplace. In a November 13 update, the company said at most 5,000 users potentially received the malicious build during an approximately 11-hour window on October 29.
The distinction is important: this was an unauthorised copy distributed through Cursor’s marketplace cache, not an extension published by Anthropic. Cursor says Anthropic’s product had no vulnerability involved in this incident, and the Open VSX marketplace source never hosted the malware.
Which users need to check?
Cursor’s original security notice identifies versions 2.1.312 and 2.1.313 of Anthropic.claude-code for macOS and Windows, installed or updated from the Cursor VS Code Extension Marketplace during the October 29 exposure window. Simply using Cursor or Claude Code does not establish that a person received one of those tampered builds.
Cursor says it has contacted affected customers directly. People who installed the specified versions in that window should follow the official notice and involve their IT or security team where applicable. The notice includes checks and remediation steps; Cursor warns that uninstalling the extension alone may not be enough because the payload could leave separate persistence scripts behind.
How the incident spread
According to Cursor’s investigation update, an attacker obtained an access key exposed by its vendor Fireworks and used it to copy historical coding-agent traces from a read-only storage bucket. Some traces contained credentials that had not been removed. Cursor says those credentials became a route into selected internal services and, later, the extension marketplace cache.
The company says coding-agent traces were exposed for fewer than 0.05% of users, while fewer than 0.01% of customers had API credentials exposed. Those are separate measures of data exposure, not the same figure as the maximum 5,000 users who potentially received the malicious extension.
What Cursor says was not affected
Cursor says prompts and code from Privacy Mode sessions, current live traffic, customer code repositories, its production systems and its official app updates were not affected. The company says it removed the malicious extension, rotated credentials, rebuilt the marketplace and moved inference traffic away from Fireworks.
Cursor believes the incident is contained and says the last attacker activity it observed was blocked on November 1. That remains the company’s assessment. The practical step for users is to check the affected versions and installation window against the official notice, rather than assume that either every installation is compromised or an uninstall settles the matter.
Image: Cursor official brand artwork.

