Uber Driver License Data Stolen in Fireworks AI Breach

Uber says an unauthorized party used compromised credentials at a service provider to reach Uber data, and TechCrunch reports the provider is Fireworks AI and that drivers' license information was taken. State filings so far list 7,870 people in three states. What is confirmed, the timeline, and what engineering teams should check.

A dark car with red tail lights driving along a wet city road at night, with the background streaked by motion blur
Photo by Atul Pandey on Unsplash

What happened: Uber says an unauthorized party used compromised credentials at one of its service providers to access Uber data. TechCrunch reports that the provider is Fireworks AI, the AI inference company whose breach exposed Notion AI chat transcripts, and that drivers’ personal and driver’s license information was stolen. State filings reported so far list 7,870 people across three states; Uber has not given a total.

Uber is the second well-known company this week to say its data was taken through Fireworks. That makes it a useful case for any team that sends data or credentials to an AI vendor.

What Uber has confirmed

The core facts come from Uber’s own breach notice, as reported by Reuters and TechCrunch on November 13, 2026:

  • Cause. Per the notice on the California attorney general’s website, an “unauthorized party used compromised credentials at a service provider to access its data” (Reuters’ paraphrase of the filing).
  • Vendor. Uber, in a statement reported by TechCrunch, described “a security incident impacting one of our third-party vendors, Fireworks.ai.” Reuters says the filing itself did not name the provider.
  • Data. TechCrunch reports driver notices say personal and driver’s license information was stolen. Reuters notes the California filing did not list the data types.
  • Response. Uber severed its data connections with the provider and opened an investigation, and is offering credit monitoring and fraud assistance through Cyberscout, a TransUnion company (Reuters).
  • Misuse. Uber said it “had not identified any misuse of the data to date” (Reuters).

Timeline

Date (2026)EventSource
Oct 6Fireworks identifies unauthorized use of internal Fireworks credentialsFireworks bulletin (see our Notion report)
Oct 9Provider tells Uber its credentials were compromisedReuters, TechCrunch
Oct 13Uber’s investigation determines the credentials were used to access Uber dataReuters
Oct 23-24Separate incident at a cloud provider hosting Fireworks R&D machines; unauthorized workload runFireworks update
Nov 10Date on Uber’s noticeReuters
Nov 13Uber’s notices and state filings reportedTechCrunch, Reuters

How many people: what the filings show

StatePeopleSource
Massachusetts2,567TechCrunch
South Carolina3,430TechCrunch
Rhode Island1,873TechCrunch, Reuters
Illinoisaffected, count pendingTechCrunch
Californiadrivers notified, no number givenTechCrunch

The three numbered states add up to 7,870. That is a floor for those states, not a total: TechCrunch says the figure is expected to rise, and Reuters reports the notice also carried instructions for residents of the District of Columbia, Maryland, North Carolina, New York and Pennsylvania.

Confirmed vs not confirmed

ClaimStatus
Unauthorized access to Uber data using credentials compromised at a service providerConfirmed by Uber’s notice (via Reuters)
The provider is Fireworks AIConfirmed by Uber, as reported by TechCrunch
Driver’s license and personal information stolenReported by TechCrunch from driver notices
Total number of people affectedNot disclosed
Which Fireworks incident path (October 6 credentials or October 23 cloud provider) reached Uber dataNot stated by Uber or Fireworks
What Uber data Fireworks held, and whyNot stated
Who did itFireworks links its incidents to a financially motivated group selling stolen LLM access; it has not named the group, and TechCrunch says no group has claimed the Uber data theft

The dates line up with Fireworks’ first incident (identified October 6, with Uber told on October 9), but neither company has said so. Treat that link as unconfirmed.

What this means for engineering teams

Uber’s notice describes the failure in one phrase: credentials at a service provider. Fireworks’ own bulletin, covered in our Notion report, said it believes API keys and tokens stored as secrets in some customer accounts’ evaluation jobs were captured. Whatever the exact path here, the pattern to check in your own environment is the same.

  1. List what you have handed to AI vendors. API keys, cloud storage tokens, database or data-warehouse connectors, webhook secrets and service-account keys placed in vendor job settings, eval configs or “bring your own bucket” integrations. Most teams track the vendor; few track the secrets inside it.
  2. Scope those credentials to one job. Read-only, single bucket or dataset, short expiry where the vendor supports it. A key that can read the whole driver table should not sit in an evaluation job.
  3. Rotate at the issuer. Deleting a secret from the vendor’s store does not revoke it. Revoke and reissue in your own cloud or identity provider; our guide on detecting and rotating leaked API keys covers the order of operations.
  4. Cut the data path, then investigate. Uber says it severed its data connections with the provider. Know in advance which network paths, connectors and OAuth grants you would disable, and who owns each.
  5. Watch access logs for the vendor’s credentials. If a vendor-held key was used from unfamiliar infrastructure, your own cloud audit logs are the fastest place to see it.
  6. Ask vendors per-feature questions. Which features store your data or credentials, where, and for how long. Our third-party SaaS vetting guide has a question list to start from.

Limits of this article

We could not retrieve the California attorney general filing or the state notices directly in this run; the filing details are as reported by Reuters (via finwire.io syndication) and TechCrunch on November 13, 2026. Fireworks did not respond to either outlet. We will add a dated update if Uber or Fireworks publishes more detail.

Sources and verification

Important claimSourceStatus
Notice says compromised credentials at a service provider used to access Uber data; notice dated Nov 10; Oct 9 and Oct 13 dates; Cyberscout; no misuse identified; RI 1,873; DC, MD, NC, NY, PA instructionsReuters via finwire.io, Nov 13, 2026Verified (press report of the filing)
Uber names Fireworks.ai; driver’s license data; MA, SC, RI counts; Illinois and California status; no group has claimed itTechCrunch, Nov 13, 2026Verified (press report)
Fireworks’ October 6 and October 23-24 incidents, LLMJacking descriptionFireworks bulletins, as cited in our Notion reportVerified (Nov 13 run)
7,870 combined across three statesSum of the state counts aboveComputed

Frequently asked questions

What data was stolen in the Uber breach?

TechCrunch reports that Uber's notices to drivers say personal information and driver's license information were stolen. Reuters reports that the California filing itself did not list the data involved. Uber says it has not identified any misuse of the data.

Was Uber itself hacked?

Uber's notice says an unauthorized party used compromised credentials at a service provider to access Uber data. TechCrunch identifies the provider as Fireworks AI and reports Uber described it as a security incident impacting one of its third-party vendors. Uber has not said its own systems were breached by other means.

How many Uber drivers were affected?

Uber has not given a total. Reported state filings list 2,567 people in Massachusetts, 3,430 in South Carolina and 1,873 in Rhode Island. TechCrunch reports Illinois residents are affected with a count pending and California drivers were notified without a number.

Is this the same Fireworks AI breach that affected Notion?

TechCrunch and Reuters link it to Fireworks AI, which has disclosed two October 2026 incidents: unauthorized use of internal credentials identified on October 6, and an October 23 incident at a cloud provider hosting its R&D machines. Neither Uber nor Fireworks has said publicly which path reached Uber's data.

Hacking NewsUberFireworks AiData BreachAi VendorsThird-Party RiskCredentials