# Fireworks AI Breach Reaches Uber Drivers, Cursor and Notion Users

- URL: https://usa-24.com/fireworks-ai-breach-uber-cursor-notion/
- Publisher: USA 24
- Section: Cybersecurity
- Published: 2026-11-22T13:01:29.026Z
- Updated: 2026-11-22T13:01:29.033Z
- Topics: Fireworks AI, Data Breach, Supply Chain Security, Uber, Cursor, AI Security

> A breach at AI inference vendor Fireworks AI exposed Uber driver license records and Cursor credentials, and Notion AI users may need to rotate secrets.

## Key takeaways

- Uber told an Oregon filing it notified 149,346 people that their information was taken, including driver's license data.
- Fireworks reports two incidents, one from August 3 to October 7 and one from October 23 to 30 that involved a breached third-party cloud provider.
- Cursor says an access key it issued to Fireworks was compromised, and the attacker pushed a malicious Claude Code extension through Cursor's marketplace.
- Notion says fewer than 1% of its workspaces were affected, with exposed Notion AI chat transcripts used for its Insights feature.
- Deleting a secret from Fireworks does not invalidate it, so affected users should rotate credentials at the issuing provider.

Uber drivers, Cursor developers and Notion AI users share little on the surface, yet one vendor connects them all. About 149,000 people are learning that their driver's license information was taken through Fireworks AI, an inference vendor that runs AI models for companies building their own products. The core incidents date to October, but the fallout is only now reaching consumers and developers as affected companies file notices.

An Oregon filing shows Uber notified 149,346 people, and [TechCrunch](https://techcrunch.com/2026/11/16/uber-confirms-hackers-stole-thousands-of-drivers-license-information-in-data-breach/) described the exposed records as close to 150,000 driver's licenses. Uber's notices were reported on November 16. Cursor published its disclosure on November 13, and Fireworks updated its security bulletin on November 9. This is a developing story, and several basic facts remain unsettled.

## What Fireworks AI disclosed

Fireworks reports two separate incidents. The first, which it identified on October 6, involved misuse of internal credentials that reached secrets and datasets for some customers. Its [security bulletins](https://fireworks.ai/security/bulletins) place that activity between August 3 and October 7. The second ran from October 23 to 30 and involved a third-party cloud provider that had been breached, giving the attacker access to parts of Fireworks' production systems. Fireworks has not named that provider in the sources reviewed.

Fireworks says a financially motivated group that sells stolen tokens for accessing large language models is behind the breach. [Security Affairs](https://securityaffairs.com/203339/data-breach/fireworks-ai-breach-exposes-uber-data-and-highlights-supply-chain-risks.html) reports that no group has claimed the Uber data theft, so it is not clear who took the Uber records.

The reach is broad. [Forbes](https://www.forbes.com/sites/annatong/2026/11/09/fireworks-cyberattack-exposes-customer-data-and-ai-models-as-fallout-widens/) reports that Fireworks has roughly 10,000 enterprise customers, including Uber, Shopify, Upwork, DoorDash, Cursor and Cognition. Forbes also reported that Fireworks CEO Qiao said in a post on X that the attacker's behavior appeared to involve AI agents. Forbes paraphrased the post, so that detail is reported, not a direct quote.

## Timeline of the Fireworks AI breach

- August 3 to October 7: the first Fireworks incident window, according to its bulletin.
- October 6: Fireworks identifies the first incident.
- October 7: Uber's access date, according to [Panorays](https://panorays.com/blog/uber-data-breach/). This conflicts with Uber's own timeline.
- October 9: Uber's notice says the vendor was notified.
- October 13: Uber's notice says the access was determined.
- October 23 to 30: the second Fireworks incident, involving a breached cloud provider.
- November 9: Fireworks updates its security bulletin.
- November 12: Notion says fewer than 1% of its workspaces were affected.
- November 13: Cursor discloses the compromised access key and the malicious extension.
- November 16: Uber's notices are reported.

## Which Uber drivers are affected and what Uber knew

Uber told California and Oregon regulators that a vendor had its credentials misused to reach Uber data stored with Fireworks. An Uber spokesperson described the notices as concerning "a security incident impacting one of our third-party vendors, Fireworks.ai," according to TechCrunch.

Uber says it had alerts covering its Fireworks environment. Because the attacker used Fireworks' own internal credentials, none of those alerts fired. The attacker looked like a trusted insider, so the monitoring Uber relied on saw nothing.

For drivers, the main risk is phishing and identity fraud. A driver's license record paired with a name and address gives scammers enough detail to make a text message or a fake support call more convincing. Anyone who receives an Uber notice should read which data elements the letter lists, since that is the most reliable guide to what was taken.

## How the malicious Claude Code extension spread through Cursor

Cursor said an access key it had issued to Fireworks was compromised. The attacker used that key to copy a read-only storage bucket, which contained unredacted credentials that opened the door to SaaS tools Cursor uses. Through those tools, the attacker reached archived non-production source repositories, limited support data and email, product usage metrics, summaries of some coding-agent conversations, and some credentials users had sent to Cursor support. [SecurityWeek](https://www.securityweek.com/cursor-supply-chain-attack-started-at-fireworks/) laid out the chain.

The most immediate risk for developers is the extension. Using stolen access, the attacker pushed malicious copies of a Claude Code extension through Cursor's marketplace, according to [Kaseya's weekly breach roundup](https://www.kaseya.com/blog/the-week-in-breach-news-11-18-26/). Cursor's warning is direct: "Uninstalling the extension alone may not be enough."

[Prophet Security's summary](https://www.prophetsecurity.ai/blog/fireworks-ai-breach) of Cursor's disclosure puts the exposure of API credentials at fewer than 0.01% of customers. That is a small share, but each affected developer still needs to check installs and rotate keys.

## What Notion AI users need to do

Notion said on November 12 that the incident affected fewer than 1% of its workspaces. The exposed data included Notion AI chat transcripts used for its Insights feature. Notion says Fireworks had committed to zero data retention for that data. That promise limits how long the vendor should have held the data, though it does not undo exposure during the intrusion.

Notion advised users to treat exposed data as compromised and to rotate any credentials pasted into Notion AI, according to [Halborn](https://www.halborn.com/blog/post/explained-the-fireworks-ai-hack-october-2026). Neither Notion nor Cursor has said which Fireworks incident exposed its data.

## A wider pattern in AI vendor supply chains

This is not a one-off. The [Cloud Security Alliance](https://labs.cloudsecurityalliance.org/research/csa-research-note-fireworks-ai-inference-provider-breach-202/) cites a Wiz Research count of at least nine AI developer platforms reporting incidents in October 2026. It describes attackers going after environment variables and especially AI provider keys. A separate [CSA research note](https://labs.cloudsecurityalliance.org/research/csa-research-note-fireworks-cursor-extension-chain-20261116/) shows how a vendor's stolen key can become an endpoint compromise through a developer tool's own distribution channel.

Uber's case shows a shared dependency. Several large companies lost data through one AI vendor they each chose, so that vendor's security now sets risk for all of its customers. Forbes' report of AI agents in the attack, if it holds up, would fit a broader pattern of automated intrusion. [China-linked hackers used AI agents to find a zero-day](https://usa-24.com/monai-label-zero-day-ai-agents/), which shows that pattern in another case.

## Practical steps for drivers, developers and companies

- Rotate credentials at the company that issued them. Deleting a secret from Fireworks does not invalidate it.
- Check Cursor for the malicious Claude Code extension, remove it, and rotate any credentials that were on that machine. Cursor warns that uninstalling may not be enough.
- Rotate any credential you typed or pasted into Notion AI, and treat those chats as compromised.
- If you drive for Uber, watch for messages that mention Uber, your driver's license or your account. Verify any request through official channels instead of links in the message.
- Companies using AI inference vendors should list which keys, datasets and records they store with each vendor, and limit what each key can reach. [Save Your Company Before It's Hacked by an AI Agent](https://usa-24.com/save-your-company-ai-agent-hack/) covers the basics of that review.

## What to watch next

Several questions remain open. Neither Notion nor Cursor has said which Fireworks incident exposed its data. Fireworks has not published a total count of affected customers in the sources reviewed, and the cloud provider in the October 23 to 30 incident is unnamed. No group has claimed the Uber theft, and Uber's 149,346 figure could change as its investigation continues. The sources reviewed show no lawsuits, penalties or enforcement actions against Fireworks, Uber, Notion or Cursor so far.

The next signals will come from Fireworks' bulletin updates, state breach filings and disclosures from other customers. Drivers should expect follow-up scam attempts that use the Uber name, and developers should expect more vendor disclosures as the investigation widens.

## Frequently asked questions

### Was my data exposed in the Fireworks AI breach?

If you are an Uber driver who received a notice, your driver's license data may have been taken. Uber's filing with Oregon's attorney general covers 149,346 people. Notion said fewer than 1% of its workspaces were affected, and Prophet Security reports fewer than 0.01% of Cursor customers had API credentials exposed.

### What should I do if I used the malicious Claude Code extension in Cursor?

Check your installed extensions and remove the malicious Claude Code extension. Cursor warns that uninstalling the extension alone may not be enough, so rotate any credentials that were on that machine. Also rotate any credentials you sent to Cursor support.

### Does deleting a key from Fireworks AI protect me?

No. Deleting a secret from Fireworks does not invalidate it, so you need to rotate the credential at the company that issued it. Affected users should treat any exposed key as compromised until it has been replaced.

### Which Fireworks AI incident exposed the Cursor and Notion data?

Neither Notion nor Cursor has said which of the two Fireworks incidents exposed its data. Fireworks reports one incident from August 3 to October 7 and a second from October 23 to 30. The second involved a third-party cloud provider that had been breached.

### Has anyone claimed responsibility for the Uber data theft?

No group has claimed the Uber data theft in the sources reviewed. Fireworks says it attributes the breach to a financially motivated group that sells stolen tokens for accessing large language models.

## Sources

1. [Uber says hackers stole information on close to 150,000 driver's licenses during data breach (TechCrunch)](https://techcrunch.com/2026/11/16/uber-confirms-hackers-stole-thousands-of-drivers-license-information-in-data-breach/)
2. [Fireworks AI Breach Exposes Uber Data and Highlights Supply Chain Risks (Security Affairs)](https://securityaffairs.com/203339/data-breach/fireworks-ai-breach-exposes-uber-data-and-highlights-supply-chain-risks.html)
3. [Cursor Supply Chain Attack Started at Fireworks AI (SecurityWeek)](https://www.securityweek.com/cursor-supply-chain-attack-started-at-fireworks/)
4. [Fireworks Cyberattack Exposes Customer Data And AI Models As Fallout Widens (Forbes)](https://www.forbes.com/sites/annatong/2026/11/09/fireworks-cyberattack-exposes-customer-data-and-ai-models-as-fallout-widens/)
5. [Security bulletins (Fireworks AI)](https://fireworks.ai/security/bulletins)
6. [Uber Data Breach via Fireworks AI: What Happened and What It Means for AI Vendor Risk (Panorays)](https://panorays.com/blog/uber-data-breach/)
7. [Fireworks AI Breach: How to Check Keys, Cursor and Notion AI (Prophet Security)](https://www.prophetsecurity.ai/blog/fireworks-ai-breach)
8. [Explained: The Fireworks AI Hack (October 2026) (Halborn)](https://www.halborn.com/blog/post/explained-the-fireworks-ai-hack-october-2026)
9. [From Inference Vendor to IDE Backdoor: The Fireworks–Cursor Chain (Cloud Security Alliance)](https://labs.cloudsecurityalliance.org/research/csa-research-note-fireworks-cursor-extension-chain-20261116/)
10. [Fireworks AI Breach: Inference Providers as Supply-Chain Chokepoints (Cloud Security Alliance)](https://labs.cloudsecurityalliance.org/research/csa-research-note-fireworks-ai-inference-provider-breach-202/)
11. [The Week In Breach News: November 18, 2026 (Kaseya)](https://www.kaseya.com/blog/the-week-in-breach-news-11-18-26/)
