Uber has begun emailing drivers whose data was stolen after hackers breached a third-party vendor's infrastructure. The November 10 notifications don't state how many people were affected in total, but a filing with the Maine Attorney General puts the number at 149,346. The exposed data includes names, driver's license numbers, dates of birth, and addresses — enough to open a line of credit in someone else's name. BleepingComputer has the story.
Here's Uber's own account of the mechanics: on October 9, 2026, the contractor reported that a third party had compromised its internal credentials and used them to get into the contractor's Uber account. Uber immediately cut off data-sharing channels, launched an investigation, and on October 13 confirmed unauthorized access to its information. The company has not named the contractor. TechCrunch was the first to link the incident to Fireworks — an AI training infrastructure provider that was hacked following an attack on its cloud provider. Fireworks attributes the attack to a financially motivated group behind a string of LLMjacking attacks. Cursor and Notion were also hit by the same incident, according to the companies themselves.
The hole wasn't in Uber's code — it opened at the seam with a contractor where Uber kept an account. Our read: this is the nastiest kind of breach, because there's no way to audit it from the outside — a client can't see how a vendor stores its keys or who else has access to them. Uber did exactly what the playbook calls for: severed the connections, counted the records, sent the emails, and reported to regulators. But the notification arrives more than a month after the access was confirmed.
What this means for the people involved: a driver's license number can't be rotated like a password. You can't "reset" your date of birth. Experience shows these data sets circulate in social-engineering databases for years, not weeks. That's why 149,346 isn't just a dry figure in a filing — it's a hundred and fifty thousand people who now need to keep an eye on their credit reports.
Winners and losers: the losers are the drivers and the reputation of the entire chain — Fireworks, Cursor, and Notion are now tangled up in one story for one reason. The winners, cynically, are auditors and insurers: demand for security reviews of AI infrastructure supply chains is about to spike. We think the real lesson here isn't about Uber — it's about concentration: one cloud provider behind one AI platform drags dozens of customer accounts down with it.
There's a date discrepancy in the sources: Uber learned of the compromise on October 9, while TechCrunch dates the Fireworks incident to October 24. Either there was another episode in the chain, or the dates got shifted in the retelling — there's no way to verify from public data. Uber hasn't officially named the contractor, and no comment from its press office was available at the time BleepingComputer published. The big questions remain unanswered: did the data end up in the open, has anyone tried to use it, how many records did Fireworks itself hold, and what exactly was stored there.
Should Uber name the contractor publicly, given that the contractor has already confirmed the breach — or is staying silent legitimate here?
Is the platform obligated to compensate drivers with a year of free credit monitoring, or is a notification email enough?
Should businesses demand security audits from AI vendors before signing contracts — or does that add so much cost to every pilot that projects simply never get off the ground?
Forecast: within the quarter, expect at least one formal demand from a state attorney general or a class-action lawsuit from drivers in which the contractor is named outright.
Disclaimer: Fireworks' involvement is based on TechCrunch's reporting and statements from the affected companies themselves; Uber has not officially confirmed the contractor.
Source: BleepingComputer
Source: www.bleepingcomputer.com · post in Telegram