Uber is notifying 149,346 people after an attacker used a service provider’s internal credentials to access driver information. Uber’s November 10 filing with Iowa identifies images of driver’s licenses and extracted text, including names, addresses, dates of birth and license numbers.

Sergiu Gatlan’s November 17 report describes the notification. Zack Whittaker’s reporting for TechCrunch includes Uber’s confirmation that the provider was Fireworks AI. The regulatory letters themselves leave the provider unnamed.

Valid credentials crossed a trusted boundary

Uber’s Iowa filing gives the clearest timeline:

  • October 7: the attacker used the compromised provider credentials to access Uber data.
  • October 9: the provider notified Uber. Uber severed data connections and began investigating.
  • October 13: Uber’s investigation determined that personal information was involved.
  • November 10: notification to affected individuals began.

The information was in cloud storage Uber created for the provider’s work. Uber says its Cloud Security team oversaw that environment and alerting was enabled. No alerts fired because the attacker used valid credentials and the existing data flows.

Uber says the compromised credentials did not grant access to its other systems. It deleted or rotated the associated credentials and access information. The provider also reported revoking compromised credentials.

Evidence status: company-confirmed unauthorized access to personal information, documented in regulatory filings. TechCrunch reports data theft and confirms the vendor identity through Uber. The sources do not establish that every affected driver’s identity has been misused.

Keep the October events separate

Fireworks’s November 17 update now separates two incidents, spanning August 3–October 7 and October 23–30. Uber’s filing dates its data access to October 7. The later incident should not replace that documented date.

Update — November 17, 2026, 17:43 EST

Fireworks now says stolen credentials and a service vulnerability enabled the first incident. For a small number of customers, attackers accessed secrets, model files and datasets. It says Unit 42 completed that investigation and the incident is contained and remediated.

For the second incident, Fireworks says access through a breached third-party development host reached production systems. It reports exposed account and billing information for all accounts created before October 30, plus datasets, models or secrets for a smaller subset. It says payment card numbers were excluded because it does not store them. A separate forensic investigation continues.

This updates the earlier account of October activity, which did not clearly distinguish the two incidents. These are Fireworks-wide findings, not a revised count of Uber drivers or proof that Uber’s data was accessed twice. Uber’s documented October 7 timeline and driver-license response remain unchanged.

The same provider’s incidents also affected Notion AI chats and Cursor’s extension marketplace. Those pages cover different downstream exposure and response. Their impact should not be assumed for Uber drivers.

Respond to copied identity data

Affected drivers should use their own notification to confirm the information involved and the offered monitoring and fraud-assistance services. Uber’s notice recommends reviewing account statements and credit reports, promptly reporting suspicious activity, and considering a fraud alert or credit freeze.

A credit freeze helps restrict new credit accounts. It does not prevent every misuse of a copied driver’s license. Reach Uber and credit-reporting agencies through independently verified channels, rather than unexpected messages requesting more identity documents.

For operators, the incident supports reviewing what a vendor credential can read and how that access is monitored. Removing the connection and revoking its credentials stops future authorized use of that path; it cannot recall copied records. Alerting needs to account for misuse of trusted access, not only invalid logins.

Caveat: Uber’s investigation remains ongoing. Its notice says no misuse had been identified at that time; that is not a guarantee against later identity fraud.