Skip to page content

AEGLIX MIND

Connected intelligence.Security research, connected

AEGLIX news · Global

Cursor confirms breach via Fireworks AI led to malicious Claude Code extension in marketplace

Based on reporting from BleepingComputer

Published by the source: Sat, 14 Nov 2026 12:27:25 -0500

AEGLIX News

Cursor acknowledged a security incident in which threat actors circulated a tainted Claude Code add-on via its marketplace after pilfering credentials from AI infrastructure vendor Fireworks AI. The intruders penetrated internal environments and exfiltrated customer information, notably historic AI coding-agent traces that held unredacted secrets later leveraged to breach further services. The compromise originated when the attackers acquired an access key residing on Fireworks AI, a third-party platform employed for model training and inference, and exploited that exposed key to duplicate data from a read-only storage bucket Cursor used for sharing information with Fireworks.

The bucket held historic AI coding-agent traces, predominantly from 2025, gathered from users who had not activated Privacy Mode. Less than 0.05% of users saw their coding-agent traces exposed, while under 0.01% of customers had API credentials compromised. Leveraging the exposed credentials, the hackers extracted data from multiple Cursor SaaS tools, including archived non-production source-code repositories, customer-support records, product-usage metrics, and credentials shared with support.

The poisoned add-on versions 2.1.312 and 2.1.313 remained accessible for roughly 11 hours before Cursor pulled them. The malicious code tried to plant persistent SSH backdoors, harvest system details, implant an attacker-controlled SSH key, attempt to activate SSH access, and establish persistence mechanisms. Cursor estimates that as many as 5,000 users who requested the affected extension versions during the exposure window may have received the tainted builds.

Cursor shifted all inference traffic off Fireworks, revoked and rotated the compromised credentials, rebuilt its extension marketplace, and redeployed its production infrastructure as a precautionary measure.

Report prepared 2026-11-14 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.

Sources

Read original source · BleepingComputer (opens in a new tab)

Privacy policy

Explore the story

Consult the cited publisher for the original reporting, updates and supporting evidence. Check the publication date and source before acting on a headline.

These are research tools; no CVE, indicator, or campaign relationship is inferred from this article.

More from BleepingComputer

← Back to security news