Uber Drivers' License Data Stolen via AI Vendor Breach
By @sharedot · · 8 pages
- Cybersecurity
- Data Breach
- Uber
- Fireworks AI
- Third Party Risk
Hackers stole Uber drivers' license data via a breach at AI vendor Fireworks AI, affecting at least 7,870 drivers, state filings show.
What happened: a breach inside an AI vendor
Uber filed breach notices with state attorneys general after being told on October 9 that hackers had stolen internal credentials from Fireworks AI, a cloud platform that lets developers run AI models and counts Uber among its customers.
The attackers used those credentials to access Uber-related data, and the stolen information included drivers' license details.
Fireworks confirmed to TechCrunch that it identified unauthorized access affecting customer data, attributing the intrusion to a financially motivated criminal group that sells access tokens for AI models.
State filings count at least 7,870 people notified across three states, a floor that will rise because Uber has disclosed no national total and counts for Illinois and California are still missing.
Why it's surprising: an AI company holding license scans
The striking element is not just that Uber was breached again, but that driver's license data was reachable through an AI inference vendor.
Fireworks' documentation says its zero-data-retention promise covers inference traffic, while its Batch API requires dataset storage that sits outside that default — and datasets were among the data reached in a second intrusion.
Reporting so far does not explain how Uber's records fit within that wording or why driver identity documents sat in the vendor's environment.
It also echoes history: Uber's 2016 breach exposed names and license numbers of around 600,000 US drivers stored on a third-party cloud service, leading to a $148 million settlement.
The evidence: state-by-state counts and two intrusions
TechCrunch's review of regulatory filings, cited by Tech Times and SOFX, counted 3,430 affected South Carolina residents, 2,567 in Massachusetts and 1,873 in Rhode Island — 7,870 in total — with additional notifications in California and Illinois whose counts are undisclosed.
Fireworks says it detected the first activity at 12 p.m. ET on October 6, when the attacker captured environment variables including API keys in evaluation jobs, began notifying customers on October 7, and published a public bulletin on October 10.
A second intrusion followed on October 23–24 via a third-party cloud provider hosting Fireworks research-and-development machines, exposing billing information, resource metadata and incomplete model weights and datasets for some customers.
Fireworks says payment card numbers were not stored and its zero-data-retention products, including Inference, were unaffected.
The stakes: unrotatable identifiers and LLMjacking
Unlike a password, a driver's license number cannot be rotated, so exposed drivers face long-term identity risk. Uber is offering free credit monitoring and fraud assistance through Cyberscout, a TransUnion service, with 90 days from the notification letter to enroll, per SOFX.
The monetization angle is LLMjacking: Fireworks links the intrusion to a group selling tokens to illicit routing gateways, and Tech Times reports that Google Threat Intelligence Group and Mandiant warned on November 2 that single incidents have produced more than $100,000 in fraudulent charges in a day, and up to $1 million cumulatively at some organizations.
No known group has claimed the theft of Uber's data, and Google's research does not name Fireworks. Notion also confirmed exposure of Notion AI chat transcripts tied to fewer than 1% of workspaces.
A pattern of vendor-origin Uber breaches
This is Uber's second publicly reported security breach this year, according to SOFX, after an Uber Freight intrusion in August that a hacking group claimed. It follows a 2022 leak of data on more than 77,000 employees through the vendor Teqtivity.
The wider pattern — stolen vendor credentials as the entry point — recurs across the industry, and security teams buying AI inference or model hosting face pointed questions: what personal identifiers actually reach the vendor and for how long, whether credentials are narrowly scoped and rotated, and whether research-and-development environments are held to production standards, since Fireworks' second intrusion arrived through development machines hosted by a cloud provider.
What comes next: freezes, questions and open counts
For affected drivers, the practical defense is a free credit freeze at Equifax, Experian and TransUnion, plus skepticism toward any message citing Uber account or license details — exactly what a convincing phishing script needs, as Tech Times notes.
Uber has not said how many drivers were affected in total, and Fireworks says its investigation is ongoing with findings that may expand; the 7,870 figure will probably not be the last.
Fireworks disabled self-serve dataset uploads and downloads for batch inference and dataset-based training while it investigates, and is working with Palo Alto Networks' Unit 42.
For companies, the open question is whether a vendor's zero-data-retention promise covers every layer where identity documents might land.