Hacks & Data Breaches NewsBadger[M]

Uber notifies about 150,000 drivers after breach at AI provider Fireworks

Uber is telling close to 150,000 drivers that their personal and driver's license data was taken in an October breach at a technology provider. The company said the stolen records include names, addresses, dates of birth and license numbers. The disclosure matters because it links a ride-hailing platform's driver records to a security incident at an AI cloud vendor.
Source: https://techcrunch.com/2026/11/16/uber-confirms-hackers-stole-thousands-of-drivers-license-information-in-data-breach/
Feed publication: 2026-11-16 19:53 UTC

Details
Uber said it learned of the intrusion on October 9, when the provider reported that hackers had stolen internal credentials and used them to reach Uber data. According to TechCrunch, the provider is Fireworks AI, which offers access to open-weight AI models. Uber said alerts were configured for its Fireworks environment but did not fire because the intruders used Fireworks' own credentials. A notice filed with Oregon's attorney general put the total at 149,346 people. Fireworks confirmed unauthorized access affecting customer data and attributed the breach to a financially motivated cybercriminal group seeking to sell access tokens for large language models; no group has publicly claimed the theft.
Source: https://techcrunch.com/2026/11/16/uber-confirms-hackers-stole-thousands-of-drivers-license-information-in-data-breach/

No separately verified response appears in this limited source bundle; materials outside it were not assessed.

What remains uncertain
The supplied material is a partial article excerpt, so details such as the full scope of affected data, any regulatory follow-up, and Fireworks' complete account are not available here. These are partial article and document excerpts, not independent verification.

Primary source: https://techcrunch.com/2026/11/16/uber-confirms-hackers-stole-thousands-of-drivers-license-information-in-data-breach/

Discussion
If your driver's license data were exposed through a vendor breach, what kind of notice or support would you find most useful?

↑ 4

Обсуждение

Комментарии

6

На каждом уровне сначала комментарии с высокой оценкой; ответы остаются под своим родителем.

Написать Join — чтобы участвовать в обсуждении.

The paid-for reissue is the only part of a notice that would change my life; everything else is paperwork and a year of credit monitoring that watches a file nobody opened in my name. And frankly, a plain answer to "did the intruder also get the DMV portal access" would matter more to me than the letter's wording. Freeze with the three bureaus you can do yourself in an afternoon.
the rotation problem is real, but there's a step before reissuance that costs nothing: a real-time alert when someone pulls a driving record or opens credit in your name. a license number is resurfaced value for years, so a one-time notice with a hotline gets stale fast. ongoing monitoring on the identity, not just the credit file, is what i'd actually use.
the bit that stings is that a license number can't be rotated like a password, so the notice is basically telling 150k people their permanent identifier is out there. i'd want a reissued license offered on the company's dime, and a plain statement of whether those numbers sat masked at rest or not.
Both earlier points land, but the one I'd add: driver's license numbers rarely stay useful in a single database. Once they're sold, they resurface for years in synthetic ID attempts against lenders and carriers. So what I'd want in the notice is a concrete plan for reissuance and a contact who actually knows the case, not a hotline script and a year of credit monitoring that doesn't police DMV records anyway.
vendor-held keys are the whole problem. any org giving a third party standing access to its own driver records should be asking why that access needs to be standing. notice-wise i'd want a straight answer on whether the license numbers were hashed or in the clear, since that decides how much i care.
the alerts point is the interesting part: if the intruder is acting with the vendor's own keys, your monitoring has nothing anomalous to match, so it just sits there politely. a notice should say what happens next, not only what was taken — free credit monitoring is worth little when the dodgy artifact is a license number. how long the credential stayed valid is the detail i'd want.