AI Catchup

Cursor Details Security Incident Involving Claude Code Extension

By 3 min read

Cursor says an unauthorized copy of Anthropic's Claude Code extension was available in the Cursor VS Code extension marketplace cache for about 11 hours on October 29, 2026. Up to 5,000 users who requested specific cached versions that day potentially received it. Cursor says it believes the incident is contained and tells affected users to follow its security notice; uninstalling the extension alone may not be enough.

Cursor has published a follow-up on a security incident involving unauthorized copies of Anthropic's Claude Code extension in the Cursor VS Code extension marketplace cache. The company says the build was available for about 11 hours on October 29, 2026, and that it believes the incident is contained. (Cursor's incident update)

Cursor says at most 5,000 users who requested specific cached versions that day potentially received the malicious build. Its security notice identifies Anthropic.claude-code versions 2.1.312 and 2.1.313 for macOS and Windows. (Cursor's incident update; Cursor's security notice)

What Cursor Says Happened

Cursor's November 13 update follows an investigation it says lasted about two weeks. It reports that a malicious copy of the Claude Code extension was served from the Cursor marketplace cache for roughly 11 hours on October 29, then removed. Cursor says the last attacker activity it observed was blocked on November 1 and that it believes the incident is contained. (Cursor's incident update)

Cursor says Anthropic did not publish the copies, that the incident was not a vulnerability in Anthropic's product, and that the Open VSX marketplace was not affected. The report describes the incident as involving Cursor's marketplace cache. These details are Cursor's account of its investigation. (Cursor's incident update)

Who May Need to Act

Cursor identifies users who installed or updated to Anthropic.claude-code versions 2.1.312 or 2.1.313 from the Cursor VS Code extension marketplace during the October 29 exposure window. Its security notice gives the window as 2:27am PT to 1:35pm PT and says the affected platforms were macOS and Windows. (Cursor's security notice)

The company says up to 5,000 users who requested specific cached versions that day could have received the affected build. It also says it identified and contacted affected customers directly, including team administrators when it found credentials that should be rotated. (Cursor's incident update)

Cursor says coding-agent traces were exposed for fewer than 0.05% of users, and API credentials were exposed for fewer than 0.01% of customers. It says prompts and code for Privacy Mode users, live traffic, production systems, and customer code repositories were not affected. (Cursor's incident update)

Steps for Potentially Affected Users

If you installed or updated to either listed version from the Cursor marketplace during the exposure window, follow Cursor's security notice for its platform-specific validation and remediation guidance. Cursor explicitly warns that uninstalling the extension alone may not be enough. This article does not reproduce the notice's scripts or system-level indicators. (Cursor's security notice)

Cursor says it emailed team administrators with lists of specific exposed keys when it found credentials that should be rotated. If your organization received that notice, use the issuing service's controls to revoke or rotate the named credentials, following Cursor's instructions. Cursor says it will contact customers directly if it identifies additional information that affects them. (Cursor's incident update)

Sources

Related coverage

Frequently Asked Questions

Which Claude Code extension versions did Cursor identify?

Cursor's security notice identifies Anthropic.claude-code versions 2.1.312 and 2.1.313 for macOS and Windows, if installed or updated from the Cursor VS Code extension marketplace during the October 29, 2026 exposure window.

What should potentially affected users do?

Cursor asks people who installed or updated to either affected version from its marketplace during the exposure window to follow the steps in its security notice. Cursor warns that uninstalling the extension alone may not be enough.

Does Cursor say every user was affected?

No. Cursor says at most 5,000 users who requested specific cached versions on October 29 potentially received the malicious build, and that it contacted customers it identified as affected.

Get an email when Cursor changes its plans, prices or limits

We check every change against Cursor's own pages before we send. You also get the weekly AI Catchup; one click unsubscribes.