Cursor Confirms a Stolen Fireworks AI Key Led to Its Breach: Leaked Agent Traces Held Credentials That Let Attackers Push a Backdoored Claude Code Extension to Up to 5,000 Users

AI · 2026-11-15 · By H.A

Cursor Confirms a Stolen Fireworks AI Key Led to Its Breach: Leaked Agent Traces Held Credentials That Let Attackers Push a Backdoored Claude Code Extension to Up to 5,000 Users

Cursor says attackers used a stolen Fireworks AI key to copy coding-agent traces containing unredacted credentials, then used those credentials to plant backdoored Claude Code extension versions 2.1.312 and 2.1.313 in its marketplace.

Cursor, the AI code editor, has confirmed that the backdoored copies of Anthropic's Claude Code extension pushed to its users on 29 October were the result of a wider breach of its own systems. In an incident report published on Friday 14 November 2026, the company said attackers first got in with an access key stolen from its AI model provider, Fireworks AI. They then copied historical coding-agent traces containing unredacted credentials and used those credentials to reach more internal systems, including the extension marketplace.

What's New

When the malicious extension builds appeared at the start of November, the obvious question was how attackers had managed to publish them through Cursor's marketplace. Cursor's report answers that. It also shows the incident was bigger than one poisoned extension:

The Malicious Extension

On 29 October, attackers used a stolen credential to place modified versions 2.1.312 and 2.1.313 of the Claude Code extension on the cache that serves Cursor's VS Code-compatible extension marketplace. The builds were available for about 11 hours before removal.

According to Cursor and researchers who analysed the builds, the injected JavaScript:

Coding errors in the payload probably stopped the backdoor from working on many Windows and macOS machines where SSH wasn't already enabled. Linux machines, and any machine with SSH already running, face more risk.

Cursor estimates that up to 5,000 users requested the affected versions during that window. Anthropic's own extension and the Open VSX registry Cursor uses were not compromised. The tampering happened inside Cursor's cache layer.

Scale of the Data Exposure

Cursor says fewer than 0.05% of users had coding-agent traces exposed, and fewer than 0.01% of customers had API credentials compromised. It says production infrastructure, official application releases, customer code repositories, and code and prompts from Privacy Mode users were not affected.

What Cursor Did

Who Is Affected

What To Do Now

# Linux / macOS: review authorised keys and SSH service state
cat ~/.ssh/authorized_keys
systemctl status ssh sshd 2>/dev/null   # Linux
sudo systemsetup -getremotelogin         # macOS
# Windows: is the OpenSSH server installed or running?
Get-Service sshd -ErrorAction SilentlyContinue
Get-Content $env:ProgramData\ssh\administrators_authorized_keys -ErrorAction SilentlyContinue

Why It Matters

This is a clear example of a supply-chain chain reaction in the AI tooling stack. A breach at a cloud provider led to a breach at a model host. That breach exposed agent traces at an AI editor, and the secrets in those traces opened the editor's marketplace, which pushed a backdoor to thousands of developers. Coding-agent logs are full of pasted API keys, environment variables and tokens, and they often sit with third-party inference providers. They have become one of the most valuable things an attacker can steal. Anyone using AI coding tools should treat agent transcripts as sensitive data, keep secrets out of prompts, and rotate anything that has passed through a provider that has now disclosed a breach.

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.