Executive Summary
In October–November 2026, attackers leveraged a stolen API key exposed during a breach of Fireworks AI, a third-party model-inference provider, to infiltrate Cursor's development platform in a cascading supply-chain attack. The threat actor accessed a read-only storage bucket shared with Fireworks AI, harvested credentials embedded in unredacted coding-agent session traces, and used those credentials to place a trojanized version of Anthropic's Claude Code VS Code extension directly into Cursor's extension marketplace cache. Approximately 5,000 users received the malicious build—versions 2.1.312 and 2.1.313—during an 11-hour exposure window on October 29, 2026, with the payload attempting to install a persistent SSH backdoor. The same Fireworks AI breach was separately confirmed to have impacted Uber (thousands of driver license records) and Notion.
This incident illustrates the compounding risk of AI-era supply chains, where third-party inference providers now sit in the critical path between developer credentials, proprietary code, and end-user software distribution. As enterprises accelerate AI coding-tool adoption, the attack surface for credential harvesting through agentic session traces and marketplace poisoning is growing rapidly, drawing increased regulatory and board-level scrutiny.
Why This Matters Now
AI coding assistants and their extension marketplaces have become high-value supply-chain targets because they aggregate developer credentials, source code, and broad software distribution reach in a single platform. The Fireworks AI breach demonstrates that a single compromised inference-provider key can cascade into marketplace-level software tampering affecting thousands of developers simultaneously—a threat vector most enterprise security programs have not yet assessed or controlled.
Attack Path Analysis
The attack began when a threat actor exploited a Fireworks AI breach to obtain a Cursor-issued access key, which exposed a read-only storage bucket containing coding agent traces and embedded credentials. Using those stolen credentials, the attacker escalated access into Cursor's internal SaaS tools and source code repositories, then laterally pivoted to the extension marketplace cache infrastructure to stage a trojanized Claude Code extension. The malicious extension was served to up to 5,000 users over an 11-hour window, deploying a persistent SSH backdoor, while downstream victims including Uber and Notion suffered credential theft and data loss through the same Fireworks AI supply chain compromise.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
The attacker breached Fireworks AI and exfiltrated a Cursor-issued API access key stored in Fireworks' environment. This key granted read access to a Cursor-managed storage bucket containing coding agent session traces, some of which included unredacted API credentials and authentication tokens belonging to Cursor customers and internal systems. The supply chain compromise of a trusted AI inference vendor served as the initial foothold.
MITRE ATT&CK® Techniques
Compromise Software Supply Chain
Valid Accounts: Default Accounts
Unsecured Credentials: Credentials In Files
Create or Modify System Process
Remote Services: SSH
Data from Cloud Storage Object
Data Manipulation: Stored Data Manipulation
Automated Collection
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST SP 800-53 Rev. 5 – Supplier Assessments and Reviews
Control ID: SR-6
PCI DSS 4.0 – Management of All Application and System Accounts
Control ID: Requirement 8.6.1
NYDFS 23 NYCRR 500 – Third-Party Service Provider Security Policy
Control ID: Section 500.11
DORA (EU) 2022/2554 – Third-Party ICT Dependency and Concentration Risk
Control ID: Article 28 — ICT Third-Party Risk Management
NIS2 Directive (EU) 2022/0383 – Security of Supply Chain and Third-Party Relationships
Control ID: Article 21(2)(d) — Supply Chain Security
CISA Zero Trust Maturity Model 2.0 – Continuous Validation of Third-Party Credentials and Access
Control ID: Identity Pillar — Advanced: Credential Hygiene and Continuous Validation
ISO/IEC 27001:2022 – Supplier Security Requirements and Oversight
Control ID: Annex A 5.19 — Information Security in Supplier Relationships
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
Trojanized Claude Code extension via Cursor's marketplace demonstrates critical supply-chain attack risk, exposing developers to SSH backdoors, stolen API credentials, and compromised coding agent traces across SaaS pipelines.
Information Technology/IT
Fireworks AI breach cascaded into multi-tenant credential theft, lateral movement across SaaS tools, and malicious extension distribution, demanding Zero Trust segmentation and egress policy enforcement per NIST.800-53.SC-7.
Transportation
Uber's confirmed driver license exposure via stolen Fireworks AI credentials illustrates how supply-chain attacks exfiltrate PII from transportation platforms, triggering PCI.4.0 and HIPAA.164.312(e)(1) compliance obligations.
Internet
Online platforms like Cursor and Notion suffered stolen credentials, compromised extension marketplaces, and exfiltrated customer data, underscoring the need for Cloud Native Security Fabric and multicloud visibility controls.
Sources
- Cursor Says Stolen Fireworks AI Key Led to Trojanized Claude Code Extension Incidenthttps://thehackernews.com/2026/11/stolen-fireworks-ai-key-led-to-cursor.htmlVerified
- Cursor Security Incident Update - Official Bloghttps://cursor.com/blog/security-incident-updateVerified
- Fireworks AI Security Bulletinshttps://fireworks.ai/security/bulletinsVerified
- Cursor Says Stolen Fireworks AI Key Led to Trojanized Claude Code Extension Incidenthttps://thehackernews.com/2026/11/stolen-fireworks-ai-key-Led-to-cursor.htmlVerified
- Official Claude Code VS Code Extension Compromised - The Hacker Newshttps://thehackernews.com/2026/10/official-claude-code-vs-code-extension.htmlVerified
- Fireworks AI Breach Widens to Expose Multiple Customershttps://thehackernews.com/2026/11/fireworks-ai-breach-widens-to-expose.htmlVerified
- Uber Confirms Hackers Stole Thousands of Drivers License Information in Data Breachhttps://techcrunch.com/2026/11/13/uber-confirms-hackers-stole-thousands-of-drivers-license-information-in-data-breach/Verified
- Uber California Data Breach Filing SB24-632751https://oag.ca.gov/ecrime/databreach/reports/sb24-632751?7194ef805fa2d04b0f7e8c9521f97343Verified
- Cursor Data Use and Privacy Modehttps://cursor.com/data-useVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant to this incident because the attacker's ability to move from a compromised third-party AI vendor into Cursor's internal storage, SaaS tooling, and extension distribution infrastructure depended entirely on flat, permissive trust boundaries between integrated systems. By enforcing workload-level segmentation and identity-scoped routing across the vendor integration zone and internal operational layers, Aviatrix would likely have reduced the attacker's reachability and contained the blast radius before lateral pivoting became viable.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: A fabric-enforced trust boundary around the vendor integration zone could likely limit the reachability of Cursor's internal storage bucket from the Fireworks AI environment, reducing what a compromised third-party API key could actually touch or enumerate within Cursor's cloud workloads.
Control: Zero Trust Segmentation
Mitigation: Zero Trust segmentation would likely constrain the attacker's ability to use harvested credentials to reach internal SaaS tooling and elevated systems, since identity alone would not be sufficient to cross segment boundaries without matching workload-level policy, reducing the scope of privilege escalation paths available.
Control: East-West Traffic Security
Mitigation: East-west traffic enforcement would likely reduce the attacker's ability to traverse freely between Cursor's data-sharing storage zone and internal operational systems, constraining the pivot paths available across the SaaS application layer and limiting which repositories and data stores could be reached from compromised credentials.
Control: Multicloud Visibility & Control
Mitigation: Multicloud visibility and policy control across Cursor's internal distribution infrastructure could likely surface anomalous access to the extension cache layer and may reduce the attacker's ability to push unauthorized builds without triggering policy-based alerting or enforcement on cross-environment traffic flows.
Control: Egress Security & Policy Enforcement
Mitigation: Controlled egress enforcement would likely reduce the attacker's ability to exfiltrate data from Cursor's cloud storage to external destinations and may constrain outbound SSH sessions initiated by backdoored developer endpoints to attacker-controlled infrastructure, limiting the volume and reach of data leaving the environment.
Had segmentation and egress controls been in place, the blast radius of this incident would likely have remained constrained to the Fireworks AI vendor boundary, reducing the probability that the attacker could have reached Cursor's internal extension cache infrastructure or staged a trojanized build affecting thousands of downstream users and third-party organizations.
Impact at a Glance
Affected Business Functions
- AI-Powered IDE Extension Marketplace Distribution
- Coding Agent Session Data and Customer Credential Storage
- Customer Support and SaaS Tooling Infrastructure
- Third-Party Vendor Data Sharing and Model Training Pipelines
Estimated downtime: 11 days
Estimated loss: N/A
Credentials (API keys and support-submitted secrets) belonging to less than 0.01% of Cursor customers were exposed via coding agent session traces stored in a read-only bucket shared with Fireworks AI. Additionally, select archived non-production Cursor source code repositories containing business contact information were accessed, along with limited customer support data, email conversations, product usage metrics, summaries of coding agent sessions, and credentials users had sent to the Cursor support team. Up to 5,000 users who downloaded trojanized versions 2.1.312 or 2.1.313 of the Claude Code VS Code extension on October 29, 2026 were exposed to a persistent SSH backdoor payload. Uber separately confirmed thousands of driver license records were stolen via the same Fireworks AI breach vector. Notion also confirmed data theft via the same underlying compromise.
Recommended Actions
Key Takeaways & Next Steps
- • Apply Zero Trust Segmentation (CNSF) to enforce identity-based, least-privilege access policies between vendor integration zones and internal SaaS tooling — a properly segmented trust boundary would have prevented the Fireworks-issued key from reaching internal source code repositories or marketplace cache infrastructure even after credential theft.
- • Deploy Egress Security & Policy Enforcement (CNSF) with FQDN-based outbound filtering on all extension distribution and build pipeline infrastructure to detect and block unauthorized data copies to attacker-controlled external storage buckets and C2 servers hosting trojanized payloads.
- • Enable Multicloud Visibility & Control (CNSF) with anomaly detection on control plane API activity to surface abnormal cross-service credential usage patterns — repeated use of a vendor-scoped key to access internal SaaS tools should trigger automated alerting and session termination.
- • Enforce East-West Traffic Security (CNSF) across cloud workload boundaries to prevent lateral movement from vendor-shared data buckets into internal operational systems; workload-to-workload policies must require explicit authorization rather than relying on shared credential inheritance across trust zones.
- • Leverage the Cloud Native Security Fabric (CNSF) for real-time inline enforcement across AI agent and coding pipeline traffic flows, ensuring that agentic session traces stored for model training are stripped of credentials at capture time and that any shadow AI or third-party inference vendor integrations are subject to the same distributed policy enforcement as production workloads.



