Research

Uber Says Its Driver Data Breach Came Through Fireworks AI, a Third Downstream Victim. Drivers: Enroll in the Free Monitoring and Freeze Your Credit. Companies: List What You Send to AI Vendors

Uber Says Its Driver Data Breach Came Through Fireworks AI, a Third Downstream Victim. Drivers: Enroll in the Free Monitoring and Freeze Your Credit. Companies: List What You Send to AI Vendors

If you drive for Uber and received a letter dated November 10, 2026 titled "Notice of Security Incident," enroll in the free credit monitoring it offers within 90 days of the letter date, using the activation code printed on it at mytrueidentity.com. Then place a free security freeze with Equifax, Experian and TransUnion. Uber's filings and the press reports say the stolen data includes names, addresses, dates of birth and driver's license numbers. That set is enough to open credit in your name, so a freeze is the step that actually stops it. If you run a company that sends data to an AI vendor, make a list today of exactly what you send, and rotate every key that vendor holds.

What Uber's letter says, word for word

We read Uber's sample notification letter as filed with the California Attorney General, dated November 10, 2026 and sent through Cyberscout, a TransUnion company. Its account of what happened, in full:

"On October 9, 2026, a service provider notified Uber that an unauthorized third party had compromised the service provider's internal credentials and used them to access Uber's account with the service provider. After being notified of this incident, Uber immediately severed data connections with the service provider and launched an investigation. On October 13, 2026, our investigation determined that the unauthorized party had used the compromised credentials to access Uber data connected to the service provider."

  • How the vendor is named in the letter: it is not. The letter says only "a service provider."
  • What data: the filed template reads "the personal information involved in the incident included" followed by a blank placeholder, so the letter on file does not list the fields. The fields (names, driver's license numbers, dates of birth and addresses) come from Uber's Maine filing as reported by BleepingComputer, and from TechCrunch's reporting.
  • How many: Oregon's Department of Justice breach list shows 149,346 people notified by Uber, which TechCrunch reports as Uber's total across all states, not Oregon residents alone. The letter itself says the incident affected "approximately 1,873 Rhode Island residents."
  • When: Oregon's list gives October 1, 2026 as the date of breach; California's listing gives October 7, 2026. Uber was notified October 9, confirmed its own data was accessed October 13, and mailed letters November 10.
  • Misuse: "we have not identified any misuse of your data to date."

Where Fireworks comes in, and on whose word

The name comes from Uber, not from the letter. An Uber spokesperson told TechCrunch: "The notices to drivers are in relation to a security incident impacting one of our third-party vendors, Fireworks.ai, which had access to some Uber data." TechCrunch says Uber referred further questions to Fireworks, and that a Fireworks spokesperson confirmed unauthorized access to some of its systems that affected customer data without addressing Uber specifically. We are treating the link as Uber's own statement, made to a reporter, and not yet as part of any regulatory filing.

One detail does not line up in the press. BleepingComputer ties Uber to Fireworks' October 24 incident. Uber's letter says the provider told Uber on October 9, and the state listings put the breach on October 1 or October 7. Those dates fit Fireworks' first bulletin, published October 9, which described "unauthorized use of internal Fireworks credentials," better than the October 23 and 24 cloud-provider incident. Neither Uber nor Fireworks has said which of the two it was.

Three downstream victims, one vendor

Fireworks is an AI infrastructure provider that serves open-weight models and runs training and evaluation jobs. Each of its customers now telling the story says it lost something different:

  1. Notion says Notion AI chat transcripts sent to Fireworks for its Insights feature were retained there despite a zero-data-retention contract, affecting fewer than 1% of Notion workspaces.
  2. Cursor wrote on November 13: "It started at Fireworks. An attacker obtained an access key we had issued to Fireworks." Cursor says the attacker used that key to copy data from a storage bucket Cursor shared with Fireworks, worked from there into Cursor's internal tools, and on October 29 used "a stolen credential from the exposed data" to publish a malicious copy of the Claude Code extension in Cursor's marketplace.
  3. Uber says its drivers' identity data, held by Fireworks for Uber, is the third.

The common thread is not a model weakness. In each case the customer handed the vendor something durable (transcripts, a standing access key, a dataset of real people) and the vendor's own credentials were the way in.

What drivers should do

  1. Enroll in the Cyberscout monitoring from the letter before the 90-day deadline. Monitoring tells you after the fact; it does not stop anything.
  2. Freeze your credit at all three bureaus. It is free, it stops new accounts opened in your name, and you can lift it for a day when you apply for something. Equifax is 1-800-525-6285, Experian 1-888-397-3742, TransUnion 1-800-680-7289, the same numbers printed in the letter.
  3. Watch for anything that uses a license number: car loans and leases, rental accounts, insurance quotes, and phone carrier accounts. If you see one you did not open, report it at IdentityTheft.gov and to your state's motor vehicle agency, and ask whether your state will issue a new license number.
  4. Expect phishing that knows your name and address and claims to be from Uber, Cyberscout or a bureau. Use only the phone number in the letter, 1-866-317-7961, or the bureaus' own websites.
  5. If you did not get a letter and want to know, call that same number rather than trusting an email.

What companies should do

  1. Inventory every dataset, transcript and credential you have ever sent to an AI vendor, including for training, evaluation and analytics. If you cannot list it, you cannot notify anyone about it.
  2. Rotate every key a vendor holds for you, and replace standing keys with short-lived, narrowly scoped credentials you can revoke in minutes. Cursor's damage came from one key it had issued to Fireworks.
  3. Strip what the vendor does not need. A driver's license number is rarely something a model has to see.
  4. Ask each AI vendor in writing who hosts its engineering machines, how it stores credentials you give it, and how fast it will tell you. Uber's letter says the provider told it on October 9; its drivers were told November 10.

What we could not verify

The Maine filing itself; we could only read it as described by BleepingComputer. Which Fireworks incident affected Uber. How many of the 149,346 people are drivers rather than other individuals; Uber did not tell TechCrunch. Whether Fireworks has notified other customers. No attacker indicators have been published by Uber, Fireworks or Cursor for this chain, so there is nothing for us to add to our feed.

Sources

Uber Technologies, Inc., "Notice of Security Incident," sample letter dated November 10, 2026, filed with the California Attorney General. Oregon Department of Justice data breach list, Uber Technologies, Inc. entry reported November 10, 2026. TechCrunch, "Uber confirms hackers stole thousands of drivers' license information in data breach," updated November 16, 2026. BleepingComputer, "Uber notifies drivers of data breach affecting nearly 150,000 people," November 17, 2026. Cursor, "An update on our recent security incident," November 13, 2026. Fireworks AI, "October 2026 security incident update," updated November 9, 2026.

Our earlier coverage: Fireworks AI's second breach (https://www.dugganusa.com/post/fireworks-ai-second-breach-cloud-provider-llmjacking), Notion's exposed chat transcripts (https://www.dugganusa.com/post/notion-fireworks-ai-chat-transcripts-exposed), and the trojanized Claude Code extension in Cursor's marketplace (https://www.dugganusa.com/post/cursor-claude-code-extension-ssh-backdoor-iocs).


Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.

Get your free key → analytics.dugganusa.com/stix/register