AEGLIX News
Uber has begun notifying nearly 150,000 drivers that their personal information was stolen after attackers breached AI infrastructure provider Fireworks in early October, according to breach notification letters sent on November 10 and a filing with Maine's Office of the Attorney General. The filing revealed the incident exposed data belonging to 149,346 drivers, including names, driver's license numbers, dates of birth, and addresses. Uber severed data connections with the service provider and launched an investigation after being notified of the compromise.
The breach originated from a security incident at Fireworks, an AI training provider, which TechCrunch reported was hacked on October 24 following a compromise of a third-party cloud provider. Fireworks attributed the attack to a financially motivated cybercriminal threat actor group linked to a series of large language model hijacking attacks. The same Fireworks breach also triggered security incidents at AI coding platform Cursor and digital workspace platform Notion, indicating a broader supply chain impact across multiple technology companies.
Uber's investigation determined on October 13 that the unauthorized party used compromised credentials to access Uber data connected to the service provider. The exposed information consisted of sensitive personal identifiers for drivers, creating risks for identity theft and fraud. This incident marks Uber's third known major data breach involving third-party providers, following a December 2022 breach tied to Teqtivity that leaked IT asset information and employee emails, and an October 2016 breach that compromised data from 50 million users and 7 million drivers.
Uber severed data connections with the service provider and launched an investigation after being notified of the breach. The company sent breach notification letters to affected individuals on November 10 and filed details with Maine's Office of the Attorney General documenting the scope of 149,346 affected drivers.
Report prepared 2026-11-17 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.
Sources
Read original source · BleepingComputer (opens in a new tab)