Uber Drivers' IDs and Billing Data Stolen After Fireworks AI Vendor Breach

Hackers stole driver license numbers and billing details from tens of thousands of Uber drivers after a breach at Fireworks AI, a third‑party vendor. Uber is offering free credit monitoring but hasn’t changed its vendor oversight practices.

Share
Abstract representation of a digital security breach affecting a rideshare platform

On November 13, 2026, Uber confirmed that hackers stole government‑issued driver license numbers and billing details from tens of thousands of drivers in several U.S. states. The exposure happened after Uber’s third‑party AI vendor, Fireworks AI, suffered a breach that gave attackers access to customer data stored in Fireworks’ systems. I’m reading this as a case where a security failure in a vendor’s environment can become a direct problem for the platform’s users, even when the platform itself isn’t the primary target.

How the breach unfolded

The incident started with a third‑party cloud provider that hosts Fireworks’ developer machines. On October 6, 2026, Fireworks detected that internal credentials were being used improperly by someone outside the company. Fireworks rotated those credentials on October 9, 2026, and sent notifications to customers on October 7, 2026. The attackers had gained access to Fireworks’ development environment through that cloud provider, which let them reach customer data—including driver license numbers and billing records that Uber stored with Fireworks. Uber was informed on October 9, 2026, but it did not notify affected drivers until mid‑November.

What’s at stake for drivers

Affected drivers include roughly 3,430 in South Carolina, 2,567 in Massachusetts, and 1,873 in Rhode Island, plus additional California and Illinois residents whose counts are not specified. The stolen data includes government‑issued ID numbers and payment information, which are exactly the kinds of details attackers use for identity theft or financial fraud. Uber is offering free credit monitoring for 90 days starting from the notification date, but that only addresses one downstream effect of the breach. I can’t tell from the reports whether attackers used the stolen credentials to target specific drivers or simply collected the data for resale, so the risk remains uncertain.

Vendor responsibility and next steps

Fireworks has said it rotated all exposed API keys at their cloud providers within seven days and is monitoring for anomalous usage. Uber’s response so far has been limited to notifications and credit monitoring offers, with no public mention of changing how it validates third‑party access or audits vendor environments. For drivers, the main concern now is whether the stolen information will be misused. For Uber, the lesson is that relying on a vendor without full visibility into how that vendor secures its development environments can leave user data exposed. Until Uber tightens its vendor oversight and Fireworks demonstrates stronger internal controls, similar incidents could affect different parts of its infrastructure.

Explore more coverage on BeansSearch this story across publishers