Cursor, the AI-powered code editor built on top of Visual Studio Code, confirmed this week that a breach let attackers plant a tampered copy of Anthropic's Claude Code extension in its marketplace. The trail started one step removed from Cursor itself: an access key Cursor had issued to Fireworks AI, a third-party AI infrastructure provider it used, was exposed. Whoever got hold of it used it to read archived 2025 coding-agent trace logs sitting in a storage bucket — and some of those logs still contained unredacted credentials. With those, the attacker reached further into Cursor's internal systems and ultimately got the ability to tamper with its extension marketplace.
On 29 October, two modified versions of the Claude Code extension (labelled 2.1.312 and 2.1.313) went live in Cursor's marketplace and stayed up for roughly 11 hours before being pulled. Cursor estimates around 5,000 developer systems may have downloaded one of the tampered builds. The payload collected basic host details — hostname, username, operating system, working directory, and the Git-configured email — then tried to drop an attacker-controlled SSH key and open a reverse SSH tunnel for persistent remote access. Researchers found coding errors in the payload that meant enabling SSH generally required admin privileges it didn't have, so the backdoor likely failed to take hold on most Windows and Mac machines. Anthropic's Felix Rieseberg confirmed the official extension and the separate Open VSX marketplace were never affected; this was isolated to a tampered copy sitting inside Cursor's own store.
What this means for your business
If anyone on your team uses Cursor, check whether Claude Code extension version 2.1.312 or 2.1.313 was ever installed on a work machine — your IT provider or developer can see this in the extension's version history inside Cursor. If it was, treat that machine as potentially exposed: review `~/.ssh/authorized_keys` for anything unfamiliar, rotate any SSH keys and credentials that were active on it between 29 October and now, and have someone who knows what to look for check for an unexpected reverse-tunnel connection before assuming it's clean.
The wider lesson travels further than Cursor. The actual point of failure here was a vendor's vendor — a credential at an AI infrastructure provider most Cursor customers had never heard of. If your business relies on developer tools, AI coding assistants, or any software with an auto-updating extension marketplace, it's worth asking your provider or IT team two things: do they pin extension versions rather than accept silent auto-updates, and do they know which third-party infrastructure providers sit behind the tools they trust. A breach three steps removed from the tool on your screen can still end up on your screen.