Cursor breach led to a malicious Claude Code extension

Credentials stolen from Fireworks AI let attackers push a malicious Claude Code extension via Cursor's marketplace. What to remove and rotate.

Cursor extension breach: Stolen vendor keys poisoned a marketplace

TL;DR: Cursor says attackers used credentials stolen from Fireworks AI to push a malicious Claude Code extension through its extension marketplace. If anyone on your team installed that extension, treat their machine and any keys on it as exposed.

What happened

BleepingComputer reported that Cursor, the AI code editor, confirmed a breach on its side. Attackers got hold of credentials taken from Fireworks AI, an AI infrastructure provider, and used them to publish a rogue Claude Code add-on. The Hacker News and Help Net Security are covering the same incident, so details may still change. We covered the earlier Fireworks AI breach in Fireworks AI breach leaked Notion AI chat transcripts.

The pattern matters more than the names. A secret leaked at one supplier became a way to ship code to developers at another, through a marketplace they already trust.

Am I affected?

You are in scope if anyone on your team uses Cursor and installed a Claude Code extension from its marketplace. Check Cursor's own notice for which builds were affected and when. Until you know, do the following on any developer machine that might have installed it:

  • Remove the extension and any other extension you do not recognise.
  • Rotate API keys, tokens and cloud credentials that were stored on that machine or in its environment.
  • Review recent repository and cloud activity for access you cannot explain.

How to check with Stackurity

Be clear about the limits: Stackurity does not inventory editor extensions or detect a poisoned marketplace listing. It helps with the part you control, which is the blast radius. Stackurity finds keys, tokens and passwords written in files on your servers and repositories, and lists where they are (the file, the line and a masked preview, never the value). It gives each leak an owner and a rotate-by date, then confirms with a later scan that the old key is gone. See the remediation documentation for how fixes are tracked. Stackurity Cloud has a 14-day trial: start a free trial.