Technology

Uber Says Hackers Stole Driver Records Through Vendor Fireworks AI

Martin HollowayPublished 4m ago3 min readBased on 1 source
Reading level
Uber Says Hackers Stole Driver Records Through Vendor Fireworks AI
Image by freestocks-photos from Pixabay

Uber is notifying close to 150,000 drivers that their names, addresses, dates of birth and driver's license numbers were stolen in an October data breach at one of its technology providers, Fireworks AI.

Uber said Fireworks told it on October 9 that hackers had broken in and stolen internal credentials. Credentials are the usernames, keys or tokens a system uses to prove it is allowed in. Those credentials were then used to access Uber's data. According to TechCrunch, the stolen driver records include names, addresses, dates of birth, and driver's license numbers.

In a notice filed with Oregon's attorney general, Uber put the number of people notified at 149,346. An Uber spokesperson said the notices relate to a security incident affecting third-party vendor Fireworks.ai, which had access to some Uber data.

The intrusion path is the detail security engineers will focus on. The attack began at the vendor, and the credentials taken there were used against Uber's data. The exposure therefore moved along a vendor relationship rather than through a system Uber ran directly. That makes the question of how far a vendor's credentials reach into a customer's environment the central control question.

In my view, the lesson most relevant to practitioners is less about the vendor's name than about the credential itself. Long-lived service credentials held by third parties, with broad scope into a customer's data, turn one compromise into many. Scoped tokens, which grant access only to what a task needs, short credential lifetimes, and monitoring for anomalous cross-tenant access (access that crosses from one customer's data into another's) shrink that blast radius. None of these controls is new, so their absence in any given incident is a question of execution rather than awareness.

The broader context here is the data itself. A leaked password can be reset within minutes. A date of birth and a driver's license number cannot be rotated, which gives exposed records a long useful life for identity fraud and targeted phishing. Drivers who receive notices should treat unsolicited messages that mention their license or birth date with particular caution, and should verify any follow-up through the channels they already use with Uber rather than through links in unexpected messages.

There is a constructive reading as well. The timeline, from the vendor's notice to Uber on October 9 to filed notifications to a state regulator and to drivers, is a dated trail that affected people and regulators can follow. Incidents like this are hard to rule out entirely in a software stack built on many third-party integrations. In my view, they are considerably easier to contain when vendor access is scoped, audited and revocable, and that is a design choice open to every company in this position.