CYBER ATTACK / TECHNOLOGY

CURSOR.
DATA BREACH

Cursor (technology, the United States) was hit by a data breach first reported on 14 November 2026. No group has been publicly named as behind it in these reports. 7 news reports in the last 14 days, 2 in the last 24 hours; the latest, from Le Monde Informatique: “Cursor: a key stolen from Fireworks AI behind a cyberattack”. See every attack on the live map.

THE STORY

What happened in the Cursor data breach

Cursor, the AI code editor company in the United States, disclosed a security breach that ended with a tampered copy of Anthropic's Claude Code extension on its VS Code extension marketplace. The malicious builds, versions 2.1.312 and 2.1.313, were live for about 11 hours on 29 October 2026, according to Cursor's security notice and reporting by BleepingComputer. Cursor says at most 5,000 users who requested those cached versions may have received them.

The breach traces back to an access key that Cursor had issued to Fireworks AI, an inference provider. Cursor said in an incident update published on 13 November 2026 that the key was exposed on Fireworks' side. The attacker used it to copy a read-only storage bucket holding coding-agent traces, mostly from 2025 and from sessions outside Privacy Mode. Some of those traces contained credentials that had not been removed, and the attacker used them to reach selected software tools that Cursor uses. Cursor's SaaS tools exposed archived non-production repositories, limited support data, usage metrics, some conversation summaries and credentials that users had sent to support, according to Network Security Magazine.

Cursor said the malicious build tried to install a persistent SSH backdoor on developers' computers. Security researchers at The Hacker News and Dark Reading described the code as a loader that could also send host details. Cursor says it found no evidence that Privacy Mode users, customer code repositories, its production environment, the Cursor app and official updates, or other marketplace extensions were affected. Cursor detected the last malicious activity on 1 November, and it says that activity was blocked.

Nobody has been named as the attacker. Fireworks AI's own security bulletin links its incident to a financially motivated group and to criminals selling unauthorised model access, according to a DEV Community analysis, but that attribution concerns the Fireworks incident rather than a named individual or group behind the Cursor intrusion.

Cursor removed the tampered extension, took the marketplace offline, worked with the hosting provider to take down the attacker's server, rotated keys, deactivated the Fireworks key and moved inference traffic off Fireworks. Anthropic separately published its legitimate Claude Code extension as version 2.1.314, according to SecurityWeek. Cursor says it is still monitoring its systems.

WHAT TO DO

Was my data taken in the Cursor data breach?

For this data breach: Cursor says uninstalling the extension alone may not be enough. Check your computer for unexpected SSH keys and persistence, and update to the legitimate Claude Code version 2.1.314 or later. If you sent credentials to Cursor support or used Cursor without Privacy Mode, rotate any API keys or secrets you shared.

Only Cursor can confirm whose data was involved. If you are a customer, these five steps cover you either way:

01 / WHAT WE KNOW

Cursor data breach: the details

Reports on the Cursor data breach each day3 Nov to 16 Nov · today is lighter, still counting
See the numbers
DayReports
3 Nov0
4 Nov0
5 Nov0
6 Nov0
7 Nov0
8 Nov0
9 Nov0
10 Nov0
11 Nov0
12 Nov0
13 Nov0
14 Nov3
15 Nov2
16 Nov (so far)2

More cyber attacks in the United States

02 / LATEST

Latest Cursor news

TIMELINE

Cursor data breach: timeline

SOURCES

Sources for the story

Cursor data breach: common questions

What happened to Cursor?

Cursor (technology, the United States) was hit by a data breach first reported on 14 November 2026. No group has been publicly named as behind it in these reports.

Was my Cursor account affected by the Claude Code extension breach?

Cursor says at most 5,000 users who requested the affected cached versions on 29 October may have received the malicious build.

Did the attack reach Cursor's customer code repositories?

Cursor says it has found no evidence that customer code repositories, Privacy Mode users, its production environment, the Cursor app or its official updates were affected. The attacker did reach archived non-production repositories through its SaaS tools, according to Network Security Magazine.

Is this the same as the Fireworks AI breach?

DEV Community describes the Cursor incident as a follow-up to the Fireworks AI breach rather than the same event. Fireworks exposed the key, and the attacker then used it to copy data and plant the malicious extension at Cursor.

Who carried out the attack?

No attacker has been named by Cursor. Fireworks AI links its own incident to a financially motivated group, but that is its assessment and not a confirmed attribution of the Cursor intrusion.

Is the malicious Claude Code extension still available?

Cursor removed the modified extension from the store after identifying it and took the marketplace offline to investigate. Anthropic published its legitimate Claude Code extension as version 2.1.314, according to SecurityWeek.

Who is behind the Cursor data breach?

No group has been publicly named in the reports collected here. Attribution can take weeks and is often disputed.

Was my data affected?

Only Cursor can say whose data was involved; its own statement is usually linked from the latest reports below. If you are a customer, watch for emails or texts that mention the breach, change your password there and anywhere you reuse it, and turn on two-step sign-in.