Cursor Says a Fireworks Key Exposed Customer Data and a Malicious Extension
Cursor said on November 13 that an attacker obtained an access key the company had issued to Fireworks, and that Fireworks exposed the key. The attacker copied data from a read-only storage bucket and, on October 29, placed unauthorized copies of Anthropic's Claude Code extension on the cache that serves Cursor's VS Code marketplace. Cursor says at most 5,000 users who requested specific cached versions that day may have received the build, and that it stayed up for about 11 hours. BleepingComputer and The Hacker News reported those figures from Cursor's update.
The numbers
- At most 5,000 users. Cursor says that is the count of people who requested specific cached versions of the extension on October 29 and may have received the malicious build.
- About 11 hours. Cursor says the build stayed on the marketplace cache until the company took it down and took the marketplace offline.
- Versions 2.1.312 and 2.1.313. Cursor names those Anthropic.claude-code builds. BleepingComputer reports the same pair.
- Under 0.01% of customers had API credentials in the copied traces, Cursor says, and coding-agent traces were exposed for fewer than 0.05% of users.
What the attacker reached
Cursor's November 13 post says the bucket held limited coding-agent traces, mostly from 2025, from sessions that were not in Privacy Mode. The company says it was allowed to use those sessions for model training. A small share of the traces still contained credentials that had not been redacted. From those credentials, Cursor says, the attacker reached a set of SaaS tools the company uses, then archived non-production source repositories, some with business contact information, limited support data and email, product usage metrics and contact details, summaries of some coding-agent conversations, and credentials users had sent to support.
On October 29 the attacker used a stolen credential from that internal data to write the extension onto the marketplace cache. Cursor says Anthropic did not publish the copy, that this was not a flaw in Anthropic's product, and that Open VSX, the marketplace source, never held the malware. BleepingComputer reports the same boundary. The Hacker News quotes Cursor on the Fireworks key, the read-only bucket, the 5,000-user figure, and the 11-hour window.
BleepingComputer adds a detail from its earlier reporting. The tampered extension tried to install a persistent SSH backdoor, and researchers found coding errors that likely stopped that backdoor on many Windows and macOS machines where SSH was not already enabled. The November 13 Cursor post does not restate that finding. It does tell anyone who installed or updated to 2.1.312 or 2.1.313 from the Cursor marketplace during the window to follow the October 30 security notice, and it says uninstalling the extension alone may not be enough.
Cursor says it contacted each affected customer with the details that apply to that customer. On October 30 it published a security notice with indicators of compromise and scripts to check a machine, and it began notifying users and team admins in the app and by email. Where credentials were exposed, it says it emailed team admins the specific keys to rotate and asked the services that issued those keys to revoke them.
What we are watching
Cursor says the last attacker activity it has seen was on November 1, and that the attempt was blocked. The company says it moved inference off Fireworks, deactivated the vendor key, rotated exposed credentials, rebuilt the VS Code extension marketplace, and redeployed production infrastructure as a precaution. It also says Privacy Mode prompts and code, customer code repositories, the production systems that run Cursor, the Cursor app and its official updates, and release signing keys were not in the exposed set. BleepingComputer and The Hacker News repeat that exclusion list from Cursor. None of the three accounts gives an outside count of machines that ran the extension, separate from Cursor's figure of at most 5,000 users who may have received the cached build.
Quick answers
- What happened with Cursor?
- Cursor said on November 13 that an attacker obtained an access key the company had issued to Fireworks, and that Fireworks exposed the key. The attacker copied data from a read-only storage bucket and, on October 29, placed unauthorized copies of Anthropic's Claude Code extension on the cache that serves Cursor's VS Code marketplace.
- What are the key numbers?
- At most 5,000 users. Cursor says that is the count of people who requested specific cached versions of the extension on October 29 and may have received the malicious build.
- What happens next?
- Cursor says the last attacker activity it has seen was on November 1, and that the attempt was blocked. The company says it moved inference off Fireworks, deactivated the vendor key, rotated exposed credentials, rebuilt the VS Code extension marketplace, and redeployed production infrastructure as a precaution.
This article was ultrathought.