Home/Blog/Uber driver data breach: 149,346 notified after vendor login theft
blog

Uber driver data breach: 149,346 notified after vendor login theft

November 17, 2026 · Security News

Uber driver data breach: 149,346 drivers' license numbers and addresses exposed through a vendor's stolen login

Uber began notifying 149,346 drivers on November 10, 2026 that attackers accessed their names, driver's license numbers, dates of birth and addresses through a hacked service provider, per its filing with Maine's Attorney General. The Uber driver data breach ran on the provider's stolen internal credentials, and Uber describes no flaw in its own software. Any business storing customer records with a SaaS or AI vendor shares that exposure.

Key takeaways

  • Uber notified 149,346 drivers in letters dated November 10, 2026, per its Maine Attorney General filing.
  • Attackers used a service provider's stolen internal credentials to log in to Uber's account there.
  • Uber confirmed access on October 13 but mailed letters 28 days later, and has not explained the gap.
  • TechCrunch ties the incident to AI provider Fireworks, whose breach also hit Cursor and Notion; Uber has not named the vendor.

What data did the Uber driver data breach expose?

Four fields per driver: name, driver’s license number, date of birth and address. The 149,346 count comes from Uber’s Maine filing; the letters to drivers give no total.

Uber lists no passwords, payment cards or Social Security numbers. The four fields it does list still answer most identity checks a lender, phone carrier or rental desk runs. US credit freezes at Equifax, Experian and TransUnion are free. The process for replacing a license or adding a fraud alert varies by state.

How did a vendor login open Uber's account?

According to Uber’s notice, the provider warned it on October 9, 2026 that an unauthorized party had compromised the provider’s internal credentials and used them to log in to Uber’s account there. Uber says it immediately severed data connections and opened an investigation. On October 13 it confirmed the intruder had accessed Uber data connected to that provider.

There is nothing to patch: the data sat in someone else’s tenant, behind someone else’s login. The cleanup looks more like account takeover recovery than patch management.

Is the Uber breach connected to Fireworks AI?

Possibly, but Uber has not said so. TechCrunch reported that the breach traces to AI training provider Fireworks, itself hacked through a compromised third-party cloud provider. BleepingComputer relayed that report; Uber did not immediately answer its request for comment.

The dates conflict, even inside BleepingComputer’s article: its opening places the Fireworks breach in early October, while a later line cites TechCrunch dating it to October 24. Uber says it was warned on October 9. Our reading, not a sourced fact: October 24 may be when Fireworks disclosed, not when it was breached.

Fireworks blames a financially motivated group linked to LLMjacking, which uses stolen cloud credentials to run hosted AI models at the victim’s expense. No report explains how that access led to Uber’s records. The same breach led to data theft from a limited number of customers at Cursor and Notion, and Cursor found backdoor malware on users’ devices. If your developers use Cursor, follow its guidance and check those laptops for exposed source code, tokens and cloud console access.

What should you do if a supplier stores your customer data?

When a supplier says its logins were stolen, treat that as confirmed access to your tenant until logs prove otherwise. Cut the connection first, as Uber did, then:

  • Ask the provider for the earliest successful login on your account, plus privilege changes, new API keys, queries and exports. Build your timeline from those, not the notification date.
  • Find out which identity was used: a named user, service account, support or delegated admin role, or API key. Each grants different access.
  • Revoke every credential type on the integration. A password reset does not kill API keys, OAuth refresh tokens or live sessions.
  • Preserve logs on both sides before retention runs out, and record separately what was viewed, downloaded or only inferred. That split decides who you must notify.
  • Write into the next contract a notification window in hours, the right to your tenant’s access logs, and a named security contact.

From our engagements: “severed” usually means the main sync stopped. A second API key from a one-off migration, or a forgotten SFTP export job, often stays live. Check for those, plus new OAuth grants and changed MFA settings, before you write “access ended” in any notice. A secrets and credential exposure assessment finds stale keys ahead of time. If a vendor notice has just landed, a structured data breach response keeps evidence and deadlines from slipping.

What is still unknown?

Uber has not named the provider, said whether data was downloaded or only viewed, or explained the 28 days between confirming access on October 13 and mailing letters on November 10. Reporting does not say whether the letters offer credit monitoring. Nobody has explained how the provider’s credentials were stolen or published victim counts for Cursor and Notion.

FAQ

Did Uber confirm that Fireworks was the breached provider?

No. Uber's notice refers only to a third-party service provider; the Fireworks link comes from TechCrunch.

Does Uber's letter offer credit monitoring?

Published reporting does not say. A credit freeze is free in the US either way.

What is LLMjacking?

The use of stolen cloud credentials to run hosted AI models on someone else's account. Fireworks says the group behind its breach is linked to such attacks.

If a supplier has told you its logins were stolen and your customer data sits on its platform, our data breach response team can help you scope access, preserve evidence and plan notices.


← All articles

get in touch

Tell us what you're running

Scoping is free. We reply within one business day, and under 30 minutes for active incidents.