top of page
Search

Bastion Cyber Threat Brief | November 16, 2026: Cursor Traces Extension Tampering to Stolen Keys

Writer: Bastion Cyber
Bastion Cyber
6 days ago
2 min read

Executive takeaway

If your developers use Cursor, check where and when they installed Claude Code. The affected version number is a starting point, not proof that a machine received the tampered build. Cursor’s security notice.


What Cursor disclosed

On November 13, Cursor said an attacker used a key it had issued to Fireworks AI to copy historical coding-agent traces from shared, read-only storage. Cursor says some traces contained credentials that had not been removed. The attacker used those credentials to reach some of Cursor’s SaaS tools, then used a stolen credential to place tampered copies of the Claude Code extension in Cursor’s marketplace cache on October 29. Cursor’s November 13 investigation.


Who should check

Cursor’s notice covers macOS and Windows users who installed or updated to Claude Code extension versions 2.1.312 or 2.1.313 from the Cursor VS Code Extension Marketplace on October 29, from about 5:27 a.m. to 4:35 p.m. Eastern. Cursor says Anthropic did not publish the tampered copies and Open VSX did not serve them. StepSecurity independently analyzed a tampered sample. Affected versions and install window. Cursor’s distribution findings. StepSecurity’s independent sample analysis.


What to do

Review extension installation records and compare endpoint and network activity with Cursor’s indicators. Isolate machines with evidence that the malicious code ran or that a backdoor was installed. Follow Cursor’s cleanup guidance and rotate credentials and sessions accessible from affected machines using a trusted device. Uninstalling the extension may leave parts of the payload behind. If Cursor notified your team about exposed keys, rotate the specific keys it identified. Cursor’s detection and remediation steps. Cursor’s customer notification and key guidance.


What remains unknown

A matching install record identifies a machine to investigate; it does not establish that someone gained remote access. Cursor says it blocked the last attacker activity it observed on November 1. Cursor’s investigation and containment update.


Bastion analysis

For SaaS teams in Hampton Roads and elsewhere, put developer extensions into the same inventory as other privileged software. Record the marketplace as well as the version, and keep API keys out of any coding-agent traces you share with vendors.


Verified as of November 16, 2026, 8:36 a.m. EST. Cursor’s security notice displays October 29, 2026; its investigation update is dated November 13, 2026. Neither page shows a publication time.

 
 
 

Recent Posts

See All

Comments


bottom of page