The Library

Cursor Claude Code Extension: Malicious Versions 2.1.312 and 2.1.313, the Fireworks Key Breach, and What to Check This Week

Cursor says Claude Code extension versions 2.1.312 and 2.1.313 were malicious and added an attacker's SSH key. Separately, an attacker got an access key Cursor had issued to Fireworks. Here is what Cursor confirms and what to check this week.

Elite Performance Exclusive LLC 6 min read

Where Worldwide

Cursor Claude Code Extension: Malicious Versions 2.1.312 and 2.1.313, the Fireworks Key Breach, and What to Check This Week
On this page 7 sections

Cursor has disclosed two security problems that matter to any business whose developers use it. An attacker obtained an access key Cursor had issued to Fireworks, and in a separate notice Cursor warned that versions 2.1.312 and 2.1.313 of the Anthropic.claude-code extension were malicious builds that added the attacker's SSH key to Windows and Mac computers. If those versions ever ran on a company laptop, Cursor says removing the extension may not be enough to clean it up.

Below is what Cursor itself has confirmed, what is still unknown, and a checklist for this week.

What happened in the Cursor security incident

Cursor's own update, titled "An update on our recent security incident", lays out the incident as Cursor tells it:

  • October 29: Cursor said publicly that it was investigating a security incident.
  • Where it began: Cursor says "It started at Fireworks." An attacker obtained an access key Cursor had issued to Fireworks.
  • What was reached: Cursor says that from tools the attacker got into, they accessed select archived, non-production Cursor source code repositories. We could not confirm which tools those were.
  • Customer exposure: Cursor says "less than 0.01% of customers had API credentials exposed."
  • Response: Cursor moved all inference traffic off Fireworks and deactivated the key it had issued to it.
  • Latest activity: In Cursor's words, "The last attacker activity we have seen was on November 1, and it was blocked."

The malicious Claude Code extension versions

In a separate security notice, Cursor warned about two builds of the Claude Code extension:

  • Affected versions: Anthropic.claude-code version 2.1.312 and 2.1.313, for Windows and MacOS.
  • Exposure window: Cursor gives it as between about 2:27am PT and 1:35pm PT on the day the notice was published.
  • What the builds did: Cursor says the extension added the attacker's SSH key, installed persistence, and sent host details to the attacker.
  • Who made them: Cursor states: "These malicious versions of the extension were not developed by Anthropic."

In plain terms, an SSH key lets someone log in to a computer remotely, and persistence means the attacker set something up to keep their access. Host details are information about the computer itself. Together, that adds up to a possible way back into the machine.

What is confirmed and what is not

Confirmed by Cursor on its own pages:

  • An attacker obtained an access key Cursor had issued to Fireworks.
  • Select archived, non-production source code repositories were accessed.
  • Less than 0.01% of customers had API credentials exposed.
  • The last attacker activity Cursor has seen was on November 1, and it was blocked.
  • Anthropic.claude-code versions 2.1.312 and 2.1.313 for Windows and MacOS were malicious, and Anthropic did not develop them.
  • Uninstalling the extension may not be sufficient.

Not known from the sources we checked:

  • Whether the two incidents are connected. We could not confirm a link between the two from Cursor's own pages, so treat it as unconfirmed.
  • How the malicious builds were published and how many people installed them.
  • The exact number of customers whose API credentials were exposed, beyond Cursor's figure of less than 0.01%.
  • Which tools the attacker reached, and what they did with the host details they collected.
  • A safe version to move to. Our sources do not name one, so we don't either.

Is my Cursor Claude Code extension malicious? How to check

On every Windows and Mac machine where someone uses Cursor:

  1. Open Cursor's Extensions panel and find the Claude Code extension (Anthropic.claude-code).
  2. Look at the installed version. If it is 2.1.312 or 2.1.313, treat that machine as compromised.
  3. Ask the developer whether either version was installed at any point, even if it has since updated or been removed. Cursor's warning that uninstalling may not be sufficient means the current version on screen does not tell you the whole story.
  4. On any affected machine, look through each user account's SSH authorized keys for entries nobody recognises.

What to do this week

Step What to do Why
1 List every machine where staff or contractors use Cursor You can't check what you don't know about
2 Check the installed Claude Code extension version on each Versions 2.1.312 and 2.1.313 are the malicious builds
3 Isolate any machine that ran those versions Cursor says the builds installed persistence
4 Don't rely on uninstalling alone Cursor says "Uninstalling the extension may not be sufficient"
5 Remove unknown SSH keys and review remote logins on affected machines The builds added the attacker's SSH key
6 Rotate API keys and credentials stored on, or used by, affected machines Host details were sent to the attacker
7 Rotate any Cursor-related API credentials Cursor confirms some customers had API credentials exposed
8 Rebuild compromised machines from a known-good state if you can't be sure they are clean Persistence can survive the obvious fixes

Why this matters for a business network

A developer's laptop is rarely just a laptop. It often holds access to source code, cloud accounts, servers and customer systems. An editor extension runs with the developer's own permissions, so a malicious one can reach whatever the developer can reach. When an extension plants an SSH key and installs persistence, the attacker may have a lasting way in that does not depend on the extension staying installed.

That makes developer tools part of your software supply chain, just like the libraries in your app or the plugins on your website. Most businesses track their servers and firewalls. Far fewer track which extensions are running in their developers' editors.

Cursor Claude Code extension questions people are asking

Which Claude Code extension versions are malicious?

Cursor names Anthropic.claude-code version 2.1.312 and 2.1.313 for Windows and MacOS.

Did Anthropic make the malicious extension?

No. Cursor says: "These malicious versions of the extension were not developed by Anthropic."

Is uninstalling the Claude Code extension enough?

Not necessarily. Cursor warns that uninstalling may not be sufficient, because the builds installed persistence and added the attacker's SSH key. Treat any affected machine as compromised.

Was my Cursor API key exposed?

Cursor says less than 0.01% of customers had API credentials exposed. Our sources don't say how affected customers were told. Rotating your keys is a reasonable precaution either way.

Is the Cursor breach over?

Cursor says the last attacker activity it has seen was on November 1, and that it was blocked. It has also moved all inference traffic off Fireworks and deactivated the exposed key.

Is the Cursor breach connected to the malicious extension?

Not confirmed. We could not confirm a connection between the two from Cursor's own pages.

What source code was accessed in the Cursor breach?

Cursor says select archived, non-production Cursor source code repositories.

The bigger lesson

The tools your developers install are part of your attack surface. An extension can carry the same risk as any other software you run, and a single bad build that was only available for part of a day can leave a lasting way in. Keep a list of the developer tools and extensions in use, check them when a vendor warns about a bad version, and treat any machine that ran a bad version as compromised until you have proven it is clean.

To get your development machines and servers locked down, see security hardening or request a quote.

Get security alerts like this by email, plus our free checklist, at /security-alerts.

Sources: Cursor: An update on our recent security incident; Cursor: Claude Code extension security notice.

Share X LinkedIn Facebook

Was this article helpful?

We only keep the note with this article. No name, no email.

Protected by reCAPTCHA - Privacy and Terms.

Have a question about this article?

Ask it here and we will answer you directly by email. Questions are private, never posted.

Protected by reCAPTCHA - Privacy and Terms.

Security alerts by email

Hear about the next one first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.

Want a result like this?

Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.

Get a Tech Quote

Security alerts by email

The next security hole is already out there. Hear about it from us first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.