Cursor Breach: Fireworks Key Led to Backdoored Extension
Most Cursor users are untouched, but anyone who pulled Claude Code 2.1.312 or 2.1.313 from Cursor's marketplace on October 29, or who got a credential notice from Cursor, has real cleanup to do; uninstalling the extension is not enough.
Must act: Cursor users who installed or updated the Claude Code extension from the Cursor marketplace on October 29, 2026 (about 2:27am to 1:35pm PT), and customers or team admins Cursor notified about exposed keys or support data.
Can relax: Users of Anthropic's official Claude Code extension from other marketplaces or Open VSX, Cursor users with Privacy Mode enabled who received no notice, and anyone with no svc-telemetry key on their machines.
- Check every developer machine for the svc-telemetry key in ~/.ssh/authorized_keys (and C:\ProgramData\ssh\administrators_authorized_keys on Windows).
- On any hit, isolate the machine and run Cursor's remediation script, or remove the key, persistence and tunnel processes by hand; uninstalling the extension does not remove them.
- From a clean machine, rotate every credential and session the affected user could reach: cloud, Git, SSH, registry, AI provider and SaaS tokens.