SecurityOnlineDo Son
Cursor says exposed Fireworks key enabled extension backdoor
Cursor has revealed that a supply-chain style breach in October led to tampered Claude Code extensions being cached in its VS Code marketplace, with attackers using a stolen internal credential obtained via an exposed Fireworks key. The modified Anthropic[.]claude-code extensions, versions 2.1.312 and 2.1.313, included a persistent reverse SSH backdoor and a telemetry script.
Cursor states that the intrusion originated outside its network, and that the attacker copied data from a read-only storage bucket used for sharing model training traces from 2025 sessions that were not in Privacy Mode. Cursor notes that less than 0.01% of customers had API credentials exposed, and that the historical trace exposure affected fewer than 0.05% of users, with at most 5,000 developers receiving the cached package during an 11‑hour window.
The attack is of uncertain attribution, though external bulletins from Aviatrix and Fireworks link the initial vendor compromise to financially motivated cloud credential thieves. Cursor emphasised that Anthropic did not publish this copy and that the marketplace Open VSX was not compromised.
The infection chain began with unredacted keys harvested from the shared trace bucket, enabling the intruder to pivot into Cursor’s SaaS tools, access archived internal Cursor sources, customer support emails, and credentials. Using an exposed internal credential, the attacker trojanised Claude Code packages and placed them directly into the marketplace cache on 29 October.
When installed or updated, the bundled JavaScript executed at startup to plant an unauthorized SSH public key and to register background persistence tasks on Windows and macOS. In response, Cursor coordinated with its cloud host to take the attacker’s command server offline and rotated internal credentials; live inference traffic was moved away from Fireworks, and vendor keys were revoked.
Cursor recommends affected developers run remediation scripts and rotate any API keys exposed in non-Privacy Mode sessions, while enabling Privacy Mode for sensitive workflows.