
On November 13, Cursor published the full investigation into a security incident it first disclosed...
On November 13, Cursor published the full investigation into a security incident it first disclosed on October 29: a malicious, unauthorized copy of Anthropic's Claude Code extension had appeared in the Cursor VS Code extension marketplace. The post is worth reading in full, because the attack chain is a case study in how a single leaked vendor key can cascade through a supply chain. Here is what actually happened, what was and wasn't affected, and what to do if you were in the exposure window.
1. It started at Fireworks. An attacker obtained an access key that Cursor had issued to Fireworks, an inference vendor. The key was exposed by Fireworks, and the attacker used it to copy data from a read-only storage bucket Cursor used to share data with the vendor.
That bucket held limited coding agent traces, mostly from 2025, from sessions that were not in Privacy Mode — data Cursor was permitted to use for model training. A small number of those traces contained credentials that had not been redacted. Cursor says less than 0.01% of customers had API credentials exposed.
2. Stolen credentials opened more doors. Starting with those credentials, the attacker reached select SaaS tools used by Cursor. From there they accessed archived, non-production Cursor source code repositories (some containing business contact information), 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 the Cursor support team.
3. The attacker poisoned the extension marketplace. On October 29, using a credential stolen from the exposed internal data, the attacker placed malicious, unauthorized copies of Anthropic's Claude Code extension directly on the cache used to serve the Cursor VS Code extension marketplace.
Two points Cursor stresses: Anthropic did not publish this copy, and this was not a vulnerability in Anthropic's product. The marketplace source, Open VSX, never had the malware. The poisoned build lived only in Cursor's serving cache.
At most 5,000 users who requested specific cached versions of the extension on October 29 potentially received the malicious build. It was available for approximately 11 hours before Cursor removed it. Cursor took the extension marketplace offline and worked with the cloud provider hosting the attacker's server to take that down too.
4. Notification. On October 30, Cursor published a security notice on its blog and on X, with indicators of compromise, remediation steps, and scripts to check your system, and began notifying affected users and team admins through in-app notices and email. Team admins whose credentials were exposed received a list of the specific keys to rotate, and Cursor asked the third-party services that issued those credentials to revoke them.
5. Containment. Cursor says the last attacker activity it has seen was on November 1, and it was blocked. The incident is believed contained, with monitoring continuing.
The list of what stayed safe matters as much as the breach itself:
If you installed or updated to the tampered versions — Anthropic.claude-code 2.1.312 or 2.1.313 — from the Cursor VS Code extension marketplace during the exposure window, follow the steps in Cursor's security notice. Uninstalling the extension alone may not be enough; the notice includes indicators of compromise and scripts to check your system.
If you received no notification from Cursor, your data was not in the exposed traces.
Three things stand out from this incident:
Vendor keys are blast-radius decisions. The breach did not start with Cursor's own infrastructure. It started with a key issued to a third party, for a read-only bucket, that turned out to contain unredacted credentials in training traces. Every API key you hand to a vendor is a trust boundary — scope it, monitor it, and assume the data behind it can leak.
The cache is part of the supply chain. The malicious extension never touched Open VSX, the marketplace source. It was injected into the cache that serves the marketplace. If you run any distribution layer — a CDN, a mirror, a cache — that layer is as much a target as the origin, and it needs the same integrity checks.
Privacy Mode is not just a preference. The single clearest dividing line in this incident was whether sessions were in Privacy Mode. Traces from Privacy Mode sessions were not in the exposed data at all. For tools that train on your usage by default, the privacy toggle is a security control, not a setting to leave for later.
Cursor apologized to those impacted and said it will update the post if anything important changes. For a tool that sits between your code and the models that read it, that follow-through is the part worth watching.
Source: Cursor, "An update on our recent security incident," November 13, 2026 — https://cursor.com/blog/security-incident-update
aiThe Dynatrace Cursor plugin brings an MCP server and around thirty skills to your editor to investigate production, and shows how to roll it out to a team.
securityCursor has confirmed a security breach that allowed attackers to distribute a malicious Claude Code...
mcpSeven web search APIs ship an official MCP server you can add to Claude, Claude Code or Cursor:...
aiAgent commands failing with DNS, 403 or read-only errors? Allow the right hosts, cache folders and localhost in Claude Code, Cursor and Codex sandboxes.
securityIf you use Cursor and had the Claude Code extension installed on 29 October 2026, there is a real...
How aggressive context compression in Cursor taught me to verify what my AI actually sees—and why mksglu/context-mode became non-negotiable in my workflow.
Workflows from the Neura Market marketplace related to this Cursor resource