Cursor breach exposes risks in AI developer supply chains

Avatar photo

ByRyan Mitchell

November 15, 2026

Cursor says a stolen key issued to Fireworks AI exposed limited customer data and helped attackers distribute a tampered Claude Code extension; it urges affected users to follow specific remediation guidance.

A stolen credential at AI infrastructure provider Fireworks AI helped an attacker reach Cursor data and distribute tampered copies of Anthropic’s Claude Code extension through Cursor’s marketplace cache, according to Cursor’s Nov. 13 incident disclosure and reporting by The Hacker News. The episode shows how a breach at a service provider can create risk farther down the software supply chain—even when the software publisher itself is not compromised.

Cursor says the attacker obtained an access key it had issued to Fireworks. Using the key, the attacker copied data from a read-only Cursor storage bucket. The stolen data then included credentials that were used to place malicious copies of the extension in Cursor’s VS Code marketplace cache on Oct. 29.

The affected extension versions were 2.1.312 and 2.1.313, which were available for about 11 hours. Cursor says at most 5,000 users who requested the cached versions may have received them. The tampered extension reportedly collected system information, added an attacker-controlled SSH key and attempted to enable SSH access, creating a path for persistence on developers’ machines.

Cursor’s disclosure also describes what the incident did not involve. Anthropic did not publish the tampered extension, Cursor says, and the official Open VSX marketplace never contained the malware. Cursor’s app, official updates and release-signing keys were not affected, nor were customer repositories or active inference requests. The company moved inference away from Fireworks as a precaution.

The data exposure was limited but extended beyond the marketplace incident. Cursor says historical coding-agent traces from outside Privacy Mode were involved for fewer than 0.05% of users. API credentials were exposed for less than 0.01% of customers. The company also reported access to some archived non-production source code, support information, usage metrics, contact details and credentials sent to support.

For small IT teams, the immediate step is to identify whether developers installed Claude Code versions 2.1.312 or 2.1.313 from Cursor’s cache. Cursor warns that uninstalling the extension alone may not be enough and points affected users to its Oct. 30 indicators-of-compromise and remediation guidance. Teams should follow that guidance, review endpoint and marketplace logs around Oct. 29, and rotate SSH keys and other credentials that may have been exposed or used on affected machines. Developers should also check for unfamiliar SSH keys and access, rather than assuming a clean reinstall resolves the problem.

Cursor says the last attacker activity it observed was on Nov. 1, was blocked, and the incident is believed contained. It says it rotated exposed credentials, redeployed production infrastructure, rebuilt the marketplace, and added broader secret scanning and restrictions on provider network access. Those steps reduce ongoing risk, but do not replace checks on potentially affected developer machines.

A separate vulnerability warning concerns Windows. The reported SignDrop zero-day allows local users to gain System-level privileges. That is a local privilege-escalation issue, not evidence of remote access by itself: an attacker would need a way to run code on the machine first. Administrators should track Microsoft’s security guidance and patches, restrict local access where practical, and prioritize systems used by developers or administrators, where elevated access could expose credentials and build environments.

The practical lesson from the Cursor incident is not that every AI coding tool is compromised. It is that developer services depend on chains of providers, credentials and cached software. Teams should treat those dependencies as part of their security boundary, inventory extensions and versions, and make sure credentials can be rotated quickly when a supplier reports a breach.

Leave a Reply

Your email address will not be published. Required fields are marked *