Uber Breach Exposes 149,346 Driver's Licenses via Vendor
Uber says stolen vendor credentials exposed license images and personal data of 149,346 people. Valid logins raised no alerts. Here is what to check in your own vendor access.

Uber told regulators in several U.S. states that a breach at a service provider exposed names and driver’s license data for 149,346 people, The Record reported.
What changed
Per the breach notification letters, the provider told Uber on October 9 that internal credentials had been stolen and used to access Uber’s account. The attackers reached images of driver’s licenses and extracted text: names, addresses, dates of birth and license numbers.
The data sat in a cloud storage environment Uber built specifically for the provider’s work. Uber says it cut its data connections to the provider as soon as it was notified, and it has deleted or rotated the credentials and access information tied to that provider. The investigation is ongoing. Uber did not name the provider when The Record asked.
Why nobody noticed
Uber says the environment fell under its cloud security management processes and was overseen by its Cloud Security team. The team was not alerted “because the unauthorized third party used valid credentials.” Uber also says the stolen credentials did not give access to other Uber systems.
That detail is the lesson. Monitoring tuned to spot broken-in access does nothing when the login is legitimate.
The reported link to Fireworks
TechCrunch, which first reported the breach, tied it to an attack on AI infrastructure company Fireworks, according to The Record. Fireworks said in an advisory that criminals stole billing information and AI-specific data in two breaches last month. It called the attacks part of a wider string of incidents that Google Threat Intelligence Group and Mandiant have written about under the name “LLMJacking,” where attackers hijack an enterprise’s access to large language models. Mandiant says it has responded to multiple such incidents in 2026 across North America, South America and Asia Pacific, in financial services, retail, technology and transportation. Notion and Cursor have also said they were affected. Uber has not confirmed Fireworks as its provider.
What to do
- Inventory vendor access. List every vendor that holds credentials or a storage bucket in your cloud. Anything you cannot list, you cannot rotate.
- Rotate on vendor notice, then rotate on schedule. Uber’s cleanup was rotation plus cutting the connection. Do not wait for a notice to start.
- Alert on behavior, not just failed logins. Valid credentials used from new locations, at odd volumes, or against data the vendor does not routinely touch should page someone.
- Minimize what vendors can reach. Scope each vendor environment to the data the job needs and expire stored copies. License images in a work bucket are a liability once the work is done.
- Check AI provider keys. If you use hosted LLM services, review who holds your API keys and billing access, and rotate if your provider reports an incident.
Priority call: vendor credential hygiene first, AI-key review second. The first is where this breach happened; the second is where the reported trend is heading.
Analysis: the pattern here is stolen credentials at a supplier, not a flaw in Uber’s own systems. Defenders should assume other customers of the same provider are exposed to the same risk until each one hears otherwise.
Found this useful? Share it.


