Security News

Uber Driver Licence Data Exposed After Third-Party Provider's Credentials Were Stolen

The Record · 17 Nov 2026
Key Takeaway Treat every supplier with access to your data as part of your own attack surface by limiting what they can reach and rotating the credentials you give them.

Uber has told regulators in multiple US states that a data breach exposed the personal information of 149,346 people. In its notification letters, the company said a third-party service provider told it on October 9 that internal credentials had been stolen and used to access Uber's account.

Uber's investigation found the attackers accessed images of driver's licences and extracted text from them, including names, addresses, dates of birth and licence numbers. The data sat in a cloud storage environment Uber had created specifically so the provider could do its work. Uber did not name the provider when asked, but TechCrunch reported the incident is tied to a cyberattack on AI infrastructure company Fireworks.

Uber said it cut its data connections to the provider as soon as it was notified, and has since deleted or rotated credentials and access information linked to the provider. The investigation is ongoing. Uber said the environment was covered by its cloud security management processes and monitored by its Cloud Security team, but no alerts fired because the attacker used valid credentials. It added that the stolen credentials did not give access to any other Uber systems.

Fireworks said cybercriminals stole billing information and AI-specific data in two breaches last month, and that these form part of a wider string of attacks. Google Threat Intelligence Group and Mandiant have described a tactic called "LLMJacking", where attackers hijack an organisation's access to large language models. Mandiant said it has responded to multiple such incidents in 2026, affecting organisations in North America, South America and Asia Pacific across financial services, retail, technology and transportation. Notion and Cursor have also said they were affected by the Fireworks incident.

Why it matters

Uber's monitoring was in place and still failed, because activity using valid credentials looked like normal supplier work. Any business that shares data with vendors through dedicated cloud storage is exposed in the same way, since the weak point is the vendor's credential hygiene, not your own perimeter. It forces a decision on what supplier-held data really needs to exist, and whether supplier logins are monitored for unusual behaviour rather than just for failed access.

What to do

  • Inventory every third-party provider that holds credentials or data storage access to your systems.
  • Rotate or delete supplier credentials immediately when a provider reports a breach.
  • Limit supplier access to a separate, narrowly scoped storage environment and remove identity documents once work is complete.
  • Ask providers, especially AI and LLM services, whether they were affected by the Fireworks breaches.
Answering to more than one framework? Run them as one security and AI governance programme ->

Summarised by CISO AI from The Record, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.