Tech

Cursor Reveals How a Stolen Vendor Key Led to a Malicious Claude Code Extension

Nouman Bin Tahir
Nouman Bin Tahir
November 16, 20269 min read
Cursor Reveals How a Stolen Vendor Key Led to a Malicious Claude Code Extension

🔑 Key Takeaways

  • 1. Cursor says an exposed vendor key led to a chain of credential access and a malicious extension in its marketplace cache.
  • 2. At most 5,000 users potentially received the tampered build, according to Cursor.
  • 3. Affected users should follow Cursor’s remediation guidance; uninstalling alone may not remove persistence.
📑 Table of Contents

Cursor says an exposed vendor key led to a chain of unauthorized access and a tampered coding extension. Developers who installed the affected builds have specific checks to make.

Conceptual illustration of a compromised software package in a development workflow
AI-generated editorial illustration of a software supply-chain attack; it does not depict the actual malware or a real user's computer.

Cursor has provided a fuller account of a security incident that put malicious versions of Anthropic's Claude Code extension in its own extension marketplace, linking the distribution to an exposed vendor access key and a sequence of stolen credentials.

In an update published November 13, 2026, the company said an attacker used a key issued to the AI infrastructure provider Fireworks to copy data from a shared, read-only storage bucket. Some coding-agent traces in that bucket contained credentials that had not been redacted, Cursor said. The attacker then used credentials to reach selected software-as-a-service tools and, later, the marketplace cache.

The affected extension copies were available for roughly 11 hours on October 29. Cursor says at most 5,000 users who requested the relevant cached versions potentially received them. That figure is an upper bound on potential exposure, not a confirmed count of compromised computers or successful remote logins.

The incident is a reminder that the name on an extension and the route by which it reaches a computer are separate questions. Microsoft, which analyzed the malicious package, says the affected copies were not distributed through Microsoft's Visual Studio Marketplace or the official npm package. Anthropic did not create the altered copies, according to both Cursor and Microsoft.

What changed in Cursor’s new account

When Cursor first disclosed the extension incident, users knew that a malicious build had appeared in its marketplace. The November update explains how Cursor believes the attacker got there, while separating the extension compromise from exposure involving customer traces and company support systems.

Cursor says the initial key had been issued to Fireworks and was exposed on the vendor's side. It provided read-only access to a bucket used to share data. The company says the bucket held limited coding-agent traces, mostly from 2025, from sessions that were not using Privacy Mode and that were permitted to be used for model training.

According to Cursor, a small number of traces included unredacted credentials. The company says fewer than 0.01% of customers had API credentials exposed. It also says traces were exposed for fewer than 0.05% of users not using Privacy Mode. The two percentages describe different categories and should not be added together or treated as estimates of extension infections.

Cursor says the attacker reached selected archived non-production source repositories, limited customer support data and email conversations, product usage metrics and contact details, summaries of some coding-agent conversations, and some credentials users had sent to support. These are the company's findings, not proof that every customer or repository was affected.

The company says it deactivated the vendor key, revoked or rotated credentials as it discovered further access, and notified affected customers and administrators. It says the last attacker activity it observed was blocked on November 1 and that it believes the incident is contained. An investigation can still develop as new evidence emerges.

The malicious extension and the affected window

Cursor identifies the affected builds as Anthropic.claude-code versions 2.1.312 and 2.1.313 for Windows and macOS when obtained from the Cursor VS Code Extension Marketplace during the incident window. Its security notice places that window between approximately 2:27 a.m. and 1:35 p.m. Pacific time on October 29, 2026.

Version numbers alone are not the whole exposure test. The distribution source, operating system and installation or update time matter. The company's notice addresses the tampered copies served through Cursor's marketplace; it does not say that every installation of Claude Code or every copy with those version numbers from another channel was malicious.

Cursor says an attacker used a credential obtained from exposed internal data to put unauthorized copies directly into the cache that served its marketplace. The company says the upstream Open VSX marketplace did not host the malicious package. It removed the copies, temporarily shut down the marketplace and worked with the hosting provider to take the attacker's server offline.

A cache usually helps deliver software quickly by keeping copies closer to the service distributing it. In this case, the account matters because an attacker did not need to change every upstream copy of an extension to affect users receiving a particular cached artifact. The findings do not establish that every cache or extension marketplace has the same weakness.

What the injected code attempted

Microsoft Threat Intelligence's analysis says the inserted JavaScript ran when the extension module loaded. It attempted to add an attacker-controlled Secure Shell key, enable a local SSH service, create reverse SSH forwarding, establish persistence and report information about the host.

SSH keys can authorize remote access to a machine. A reverse tunnel is a way for a connection initiated from that machine to provide a route back to it. Persistence refers to mechanisms intended to keep malicious components available after the original program closes or the computer restarts. Those capabilities explain why deleting the visible extension is not necessarily a complete cleanup.

The distinction between attempted and successful access is important. Microsoft says success depended on host privileges, SSH configuration and the attacker's server setup. Cursor says enabling the local SSH service generally required administrator rights and that, because of errors in the malicious code, the relevant step would fail outside unusual circumstances where Cursor was launched with those privileges.

Even when a tunnel did not provide a usable login, other artifacts could remain. Cursor says the extension added an attacker key, installed persistence and sent host details in affected cases. Microsoft similarly warns that keys and persistence artifacts may be written even if tunnel access fails. The sources do not justify assuming every potentially exposed user was successfully accessed remotely.

A useful indicator, with limits

Cursor's notice describes an SSH key labelled svc-telemetry as an indicator associated with the identified malware. It provides platform-specific checks and remediation scripts, along with additional indicators for network activity, files and persistence. Finding an indicator is a reason to investigate; a single absent indicator should not replace a complete assessment when installation records or other evidence point to exposure.

The vendor's original notice contains the current technical details and should be checked directly before taking action. Security teams also need to preserve relevant evidence and follow their own incident-response procedures, particularly where a development computer can access production systems or shared credentials.

What was and was not affected

Microsoft says the malicious packages it analyzed were not published through Microsoft Visual Studio Marketplace or the official npm distribution of Claude Code. It also reports that Anthropic told Microsoft its systems had not been compromised and that it did not develop the malicious package. Cursor separately says the unauthorized copies were not a vulnerability in Anthropic's product.

That does not eliminate the need to check Cursor installations. A developer may use more than one editor and may install an extension through a different marketplace than the one they normally use. Installation history and the actual artifact source are more useful here than assumptions based on the editor icon or the extension's publisher name.

Cursor also distinguishes the shared-bucket traces from live traffic and Privacy Mode data in its update. It says Privacy Mode prompts and code were not included in the bucket exposure and that affected users whose traces were exposed were contacted. That statement is Cursor's account of this investigation; it is not a blanket promise that every unrelated system or future incident is immune.

Support data and credentials sent to support form another category. A person might not have installed the malicious extension but still need to pay attention to a direct notice about exposed information. Conversely, installing an affected package is a device-level question that requires checking the machine, not merely the status of a Cursor account.

Steps for developers and administrators

Start by identifying whether Cursor's marketplace installed or updated either named version during the October 29 window on a Windows or macOS computer. Teams should consult endpoint and extension-installation records where available, rather than rely only on a developer's memory. Auto-update behavior may make an installation less obvious.

Cursor advises affected users to follow its security notice, look for the stated indicators, isolate machines showing evidence of execution or backdoor installation, and remove unauthorized keys, persistence mechanisms and tunnel processes. It also advises evaluating whether the host should be rebuilt. These are incident-specific instructions from the vendor, not a substitute for an organization's own response plan.

For credentials that may have been accessible from an affected host, Cursor recommends rotation and session revocation from a trusted system. Teams should identify the actual exposure before declaring that a particular key was stolen: a developer laptop may hold access to source repositories, cloud projects, deployment tools and local databases, but the relevant scope varies by machine.

Uninstalling or updating the extension is an appropriate part of stopping the vulnerable software from running, but Cursor explicitly warns that it may not remove standalone persistence. A clean-looking extension list therefore does not establish that a previously affected computer is clean.

Administrators can use the incident as a reason to review who may install extensions, how quickly new extension versions are deployed and what telemetry is retained. Microsoft's analysis recommends controls such as approved publishers and installation cooldowns. Those measures reduce particular risks, but they cannot guarantee that a trusted publisher's delivery path will never be compromised.

Why the incident matters beyond one editor

Development tools sit close to valuable assets. An editor extension may read local files, run commands and interact with source control or cloud credentials under the user's permissions. That makes its distribution route an attractive target even when the extension's stated purpose is to help write code.

The reported sequence also shows how separate exposures can connect. A vendor key enabled access to one storage bucket; unredacted credentials in some stored traces led to additional services; a later credential was used against a marketplace cache. Each step had its own boundary, and Cursor's report describes the investigation that connected them.

There are still limits to what the public record establishes. Cursor provides its own account of scope, detection and containment; Microsoft analyzes the package and its behavior. Neither source proves that all potentially exposed devices were infected, and the published maximum of 5,000 should not be presented as a count of confirmed victims. Future updates could refine the scope.

For users, the practical takeaway is specific: verify the installation channel and time, follow the vendor's current checks if the affected versions were installed, and treat credential rotation as a separate response when exposure is established. For teams, the broader lesson is to examine the full path from stored data and vendor access to package delivery, not just the final extension shown in a marketplace.

Sources and reporting context

Reported November 16, 2026. This article distinguishes Cursor's incident findings from Microsoft's independent malware analysis. The incident occurred on October 29; Cursor's further account was published November 13.

FAQ

Frequently Asked Questions

Quick answers to the most common questions readers usually have about this topic.

Which Cursor extension versions were affected?

Cursor identified tampered Anthropic.claude-code versions 2.1.312 and 2.1.313 for Windows and macOS served through its marketplace during the October 29 exposure window.

Was the official Claude Code distribution compromised?

Microsoft says the malicious packages were not distributed through Microsoft Visual Studio Marketplace or the official npm package, and Anthropic did not develop the malicious copies.

Were 5,000 users confirmed to be hacked?

No. Cursor says at most 5,000 users potentially received the malicious build; this is not a confirmed count of successful compromises.

Is uninstalling the extension enough?

Cursor warns that standalone persistence may remain. Affected users should follow its current security notice and incident-response guidance.

What should affected organizations do?

Identify the source and timing of installations, follow Cursor’s checks, isolate systems with evidence of execution and assess credential rotation from a trusted system.

What's your reaction?

How spicy is this take? 🌶️

Rate the controversy or spiciness of this article

Be the first to rate!
Share:
🔠

Free Tool

Case Converter

Transform string text between camelCase, snake_case, PascalCase, and more.

Try it free →

Related articles

More stories with shared topics or from this category.

Comments

0