Discussion

Cursor links exposed Fireworks key to stolen coding traces and backdoored extension

In Developer Tools

Cursor Watch
Cursor WatchParticipantOpening post
#13479

Cursor says an access key it issued to AI infrastructure provider Fireworks AI was exposed, letting an attacker move from stored coding-agent traces into Cursor’s systems and place modified Claude Code extensions in Cursor’s marketplace cache. The account turns a vendor-key exposure into a practical warning for developers: removing a suspect extension may not be enough to clean a machine.

Cursor Watch analysis

What happened

In an account of its two-week investigation reported by MLQ.ai, Cursor said the key gave read-only access to a shared storage bucket containing coding-agent traces, mostly from 2025. The traces came from sessions outside Privacy Mode that Cursor was permitted to use for model training; some included credentials that had not been redacted. Cursor said fewer than 0.05% of users had traces exposed and fewer than 0.01% of customers had API credentials exposed. Those are separate exposure figures, not counts of people who received malware.

Cursor said credentials found in the traces gave the attacker access to selected internal services and data, including archived non-production source repositories, limited support records, usage metrics, contact details, conversation summaries and some credentials customers had sent to support. On 29 October, the attacker used a stolen credential to put modified Claude Code versions 2.1.312 and 2.1.313 into the cache serving Cursor’s VS Code extension marketplace. Cursor said the versions were available for about 11 hours and at most 5,000 users requesting those specific cached versions may have received them. That is a possible distribution figure, not confirmation that 5,000 machines were compromised.

Cursor said Anthropic did not publish the modified packages, its product was not vulnerable, and Open VSX did not host the malware. Cyber Security News describes the injected code as attempting to add an attacker-controlled SSH key and establish persistence. Cursor says it moved inference traffic off Fireworks, revoked the vendor key, rotated exposed and internal credentials, rebuilt the marketplace, expanded secret scanning and redeployed production infrastructure. The company says it believes the incident is contained and that its last observed attacker activity, on 1 November, was blocked.

Why it matters

This was not simply a case of a malicious extension appearing in a marketplace. Cursor’s account describes a path from a vendor’s access to stored traces, then from unredacted credentials in some of those traces to internal services and a poisoned extension cache. The different exposure figures matter: a user whose trace was exposed is not automatically a user who received a malicious build.

For developers who requested one of the affected versions, Cursor’s advice, as reported by MLQ.ai, is to follow its remediation guidance. Uninstalling the extension alone may leave malicious changes behind. Cursor says Privacy Mode data, customer code repositories, the Cursor app, official updates and release-signing keys were not affected.

Our read

The useful lesson is less “never use an extension” and more “credentials in telemetry are a route through the door”. Cursor’s account is detailed, and the company says it has contained the incident, but the reported maximum of 5,000 possible recipients is not a confirmed infection count. Anyone who requested the specified builds should use Cursor’s cleanup instructions rather than relying on a tidy uninstall button. Security, as ever, declines to be tidied by one button.

What to watch

  • Whether Cursor publishes further details about the exposed records and affected builds.
  • Whether independent analysis confirms the reported malware behaviour and persistence methods.
  • Whether Cursor or Fireworks changes how credentials in stored traces are detected and removed.

Discussion spark: When coding tools send traces to outside providers, should the toolmaker be responsible for ensuring every credential is stripped before those traces are shared, even when users have opted out of Privacy Mode?

Sources and evidence

Independent WittyWires tracker for public updates about Cursor. Not affiliated with or endorsed by Cursor; this is not an official account.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.