Threat

Uber notifies drivers of data breach affecting nearly 150,000 people

Page published · Page updated

Dossier

Earliest dated coverage: 17 Nov 2026 · First observed: 17 Nov 2026 · Latest dated coverage: 17 Nov 2026

Coverage timeline

17 Nov 2026bleepingcomputer.com

Single-source incident — one report is available.

Why it matters

The Fireworks compromise demonstrates how a breach of shared AI infrastructure can expose downstream customer data and affect multiple connected services.

Uber is notifying 149,346 drivers after attackers used compromised service-provider credentials to access names, driver's license numbers, birth dates, and addresses. The report identifies AI infrastructure provider Fireworks as the breached provider and links its compromise to additional incidents affecting Cursor and Notion.

exploited-vuln

Summary

Uber notified drivers of a third-party data breach affecting 149,346 people, according to BleepingComputer's account of a Maine regulatory filing. The reported exposed information includes names, driver's license numbers, dates of birth, and addresses. Notification letters were sent on November 10, 2026.[0]

Uber's quoted account describes an attacker compromising a service provider's internal credentials and using them to access Uber's account with that provider. The provider notified Uber on October 9, 2026; Uber said it immediately disconnected data connections and began investigating. On October 13, Uber determined that the credentials had been used to access its connected data.[0]

The article identifies the provider as Fireworks through reporting attributed to TechCrunch, rather than through Uber's quoted notice. It also reports an upstream cloud-provider compromise and Fireworks' attribution to an unnamed financially motivated group associated with LLMjacking. These details remain single-source reporting in the supplied evidence. The chronology is unresolved: the article refers to an October 24 Fireworks incident despite Uber's earlier October 9 notification and October 13 finding.[0]

Attack chain

  1. Provider credential compromise: An unauthorized party compromised the service provider's internal credentials, according to Uber's notification quoted in the report. The method used to obtain those credentials is not specified in Uber's account.[0]
  2. Access to Uber's provider-hosted account: The unauthorized party used the compromised provider credentials to access Uber's account with that service provider. This is the explicitly reported transition from provider compromise to customer-account access.[0]
  3. Access to driver information: Uber's investigation established that the credentials were used to access its connected data. The article reports data theft affecting 149,346 drivers and identifies names, driver's license numbers, dates of birth, and addresses among the exposed information; it does not describe the extraction mechanism.[0]

Disclosure timeline

DateEvent
2026-10-09According to Uber's quoted notification, the service provider informed Uber that an unauthorized party had compromised internal credentials and accessed Uber's account. Uber said it immediately severed data connections and launched an investigation.[0]
2026-10-13Uber said its investigation determined that the unauthorized party had used the compromised credentials to access Uber data connected to the provider.[0]
2026-10-24The article separately associates the Uber breach with a Fireworks security incident dated October 24. This date conflicts with the earlier notification and investigation dates quoted from Uber; it should not be treated as a reconciled initial-compromise date.[0]
2026-11-10Uber sent breach-notification letters to affected individuals.[0]
2026-11-17BleepingComputer published its report, including the 149,346-driver impact figure attributed to Uber's Maine regulatory filing.[0]

How it works

The concrete access mechanism is abuse of compromised service-provider credentials. Uber's quoted notice says the attacker used those credentials to enter Uber's account with the provider, and the subsequent investigation confirmed access to Uber's connected data. The evidence does not explain how the credentials were obtained or what permissions enabled the access.[0]

At the broader provider level, the article reports that Fireworks was hacked after a third-party cloud-provider compromise. It does not supply the technical mechanism connecting that compromise to the credentials used against Uber. No software flaw, CVE, exploit payload, or patch is identified, so the incident cannot be characterized more specifically as exploitation of a particular software vulnerability.[0]

Key takeaways

  • The supported incident narrative is a third-party credential compromise leading to access to Uber data. The evidence does not establish a software exploit or provide a version-specific remediation path.[0]
  • Fireworks' reported association with an unnamed LLMjacking-linked group is not a named attribution for the Uber incident and does not establish that LLMjacking was the technique used to obtain driver information.[0]
  • Keep downstream impacts separate: the article links Fireworks to incidents at Uber, Cursor, and Notion, but its report of backdoor infections concerns Cursor, not Uber.[0]
  • All substantive findings here depend on one supplied news report. The linked regulatory filing, notification letters, and additional reporting were not supplied as separate source texts, and the conflicting October dates remain unresolved.[0]

Defensive actions

  • Sever the affected provider's data connections as an incident-containment measure.: Uber reported taking this action immediately after notification to block further malicious access to its data. It directly addresses the provider-connected access path described in the incident; the article does not independently establish the completeness of containment.[0]
  • Investigate access to Uber's provider-hosted account and the data reachable through the compromised credentials.: Uber's investigation determined that the credentials had actually been used to access connected data. Establishing this distinction between credential compromise and confirmed data access was central to assessing the incident's scope.[0]
  • Notify the affected drivers using the established exposure scope and data categories.: Uber sent notification letters on November 10. The reported scope encompasses 149,346 drivers and sensitive identity information, including driver's license numbers, dates of birth, names, and addresses.[0]