Flitz.ai Flitz.ai

November 15, 2026

Cursor's AI Extension Hack: A Stolen Vendor Key Turned a Coding Tool Into a Backdoor

On November 13, Cursor published the full forensic account of a supply-chain attack that quietly compromised its own extension marketplace through a vendor it trusted. The root cause was not a flaw in...

Cursor AI extension supply-chain hack illustration

On November 13, Cursor published the full forensic account of a supply-chain attack that quietly compromised its own extension marketplace through a vendor it trusted. The root cause was not a flaw in Cursor's own code, but a stolen access key belonging to a third-party AI vendor, Fireworks AI, which had earlier suffered its own breach.

As The Hacker News reports, an attacker obtained an access key that Cursor had issued to Fireworks AI, and used it to copy data from a read-only storage bucket the two companies shared. Buried in that exposed data was a further credential, which the attacker then used, on October 29, 2026, to place trojanized versions of Anthropic's official Claude Code extension directly onto the cache serving Cursor's VS Code extension marketplace.

What the malicious extension actually did

According to Sophos' analysis, the trojanized build silently added an attacker-controlled SSH key to the victim's authorized_keys file, attempted to open a reverse SSH tunnel back to a remote server, established persistence on the machine, and sent host details to the attacker. In practice, that means remote access to the developer's machine, potentially including source code, credentials stored locally, and any internal systems reachable from that device.

The scale is what makes this one worth your attention even if you've never heard of Fireworks AI. Up to 5,000 developers who requested specific cached versions of the extension on October 29 may have received the malicious build, according to Cursor's own disclosure. If your developers, contractors or an outsourced dev team use Cursor with the Claude Code extension, this is not a theoretical risk — it is a confirmed incident with a known window.

What to check today

  • Identify the affected versions. Only Anthropic.claude-code versions 2.1.312 and 2.1.313, for Windows and macOS, were affected. The Microsoft Visual Studio Marketplace and the npm package were never touched, per reporting from Online Tech Tips. Check installed extension versions on every developer machine running Cursor.
  • Inspect authorized_keys. On any Mac or Windows developer machine that may have pulled the extension on or around October 29, check the SSH authorized_keys file for unfamiliar entries. Remove anything you can't account for.
  • Look for outbound SSH tunnels. Review firewall and endpoint logs for unexpected outbound SSH connections, especially reverse tunnels to unfamiliar IP addresses.
  • Rotate credentials used on affected machines. If a developer's machine may have been compromised, assume any locally stored API keys, Git tokens or cloud credentials on that device are burned. Rotate them.
  • Update and re-verify. Make sure Cursor and the Claude Code extension are updated to a clean version, and don't rely on the update process alone — verify the extension source matches the official, non-cached release.

Why this matters beyond Cursor

This incident is a textbook AI supply-chain attack: the weakness wasn't in the AI tool itself, but in the trust relationship between vendors sharing data and credentials behind the scenes. Cursor has since moved all inference traffic off Fireworks, deactivated the compromised key, and cut Fireworks' access to all shared data sets — solid remediation, but only after the damage was done.

For Swiss SMEs, the lesson is broader than one extension. AI coding assistants, AI plugins and AI-connected vendor integrations are now a routine part of daily business IT — and so is the risk that comes with them. A stolen key at a vendor you've never directly dealt with can still end up on your developer's laptop. This is exactly the kind of threat we track daily at Flitz.ai: it changes week to week, and staying current is now part of basic IT hygiene, not an optional extra.

If you don't have the internal capacity to monitor extension marketplaces, vendor breaches and credential exposures on top of running your business, that's where outside support helps. The Mejlerö Company (TMC), based in Engelberg, supports SMEs across Obwalden, Nidwalden, Lucerne and Zurich with practical IT support — from endpoint protection and two-factor authentication to Microsoft 365 administration — and offers a free network analysis and a free one-hour consultation to help you find out where you actually stand.

Limited spots available this week

Get a FREE consultation

Get a FREE 1 hour consultation about your current application management setup, development process or any other tech setup problem.