Uber breach exposes driver licenses via Fireworks AI key
Uber is notifying US drivers that license images and ID data were stolen after attackers used credentials compromised at third-party AI provider Fireworks. One Texas filing lists 149,346 people.
Uber is notifying US drivers that their personal and driver's-license data was stolen after attackers used compromised credentials for a third-party service provider — identified as Fireworks AI — to reach Uber data held by that provider. Per TechCrunch, Uber did not state a total; a figure of 149,346 people appears in the count Uber gave the Texas attorney general's office, cataloged by BreachTally and reported by SecurityWeek. If you drive for Uber in the US, watch for a mailed notice and treat your license details as exposed.
What was taken
By Uber's account, the stolen data includes images of driver's licenses, along with names, addresses, dates of birth, driver's-license numbers and other government-issued ID numbers — the raw material for identity fraud, not just credential-stuffing. Uber says the compromised provider credentials gave the attacker no access to Uber's other systems.
Timeline
Per SecurityWeek and TechCrunch:
- 7 October — attacker uses the compromised third-party credentials to access the data.
- 9 October — the provider notifies Uber of the intrusion.
- 13 October — Uber's investigation concludes that Uber data connected to the provider was accessed.
- 10 November — Uber's notice letter is dated.
- Mid-November — filings land with state regulators including California, Iowa, Massachusetts, South Carolina, Texas and Vermont.
Uber says the attacker used valid credentials, so its own alerts did not fire — the detection gap that makes third-party key theft so effective. No group has claimed responsibility, and neither outlet names an actor.
The Fireworks thread
The root cause sits with Fireworks AI, which disclosed its own breach — attackers stole customer information including billing data and some private AI datasets. Uber is not the first customer to surface downstream of it. Hacker Posts has already covered the same Fireworks exposure cascading into Cursor, whose post-mortem tied a malicious Claude Code extension and exposed customer data to a stolen Fireworks key, and into Notion, where chat transcripts were caught up in a second Fireworks breach. Security firm Wiz groups the surrounding activity under a "Black October" wave against AI developer platforms.
Action checklist
- Uber drivers: watch for the notice and take any offered credit monitoring. Assume your license number and license image are compromised.
- Place a fraud alert or credit freeze if your license and ID data were in scope — the exposed fields support new-account fraud, not just account takeover.
- Be alert to targeted phishing that cites real details (name, license number) to look legitimate. Uber will not ask you to "verify" via a link in an unsolicited message.
- For teams running AI vendors: inventory every credential handed to a model provider or data pipeline, scope keys to least privilege, and rotate anything shared with a provider that has disclosed an incident.
Context
The mechanism is now familiar: a key or credential issued to a third-party AI provider becomes the entry point, and the data the provider holds on your behalf becomes the breach. The lesson Hacker Posts flagged after Cursor holds here too — the keys you hand a vendor are keys into you, and this autumn's run of incidents shows one exposed provider credential can surface at Uber, Cursor and Notion alike.