Uber Puts a Number on a Vendor Breach: 150,000 Licenses

The notice went to state attorneys general on Monday, and the number in it was an order of magnitude larger than the one Uber had been using a few weeks earlier.

About 150,000 drivers had their names, home addresses, dates of birth and driver’s license numbers taken in a breach that began at a supplier, according to the notification. Uber said it learned of the incident on Oct. 9, when the vendor told the company that an attacker had obtained internal credentials and used them to move laterally into the systems where driver records were stored.

TechCrunch identified the supplier as Fireworks AI, a company that runs inference for open-source models. Fireworks disclosed last month that customer information had been exposed, including billing data and some private datasets. The company has not said publicly how many records were involved or how the intrusion was carried out.

The 150,000 figure is a correction. Uber had described the exposure earlier in November as affecting several thousand drivers, a characterization that held until the forensic review finished counting records rather than systems.

Driver’s license numbers are the most useful part of what was taken. A name, an address, a date of birth and a license number are enough to pass a large share of the identity checks that financial institutions and employers run, and the combination is a standard input to synthetic identity fraud, in which a real person’s credentials are attached to a fabricated account.

Uber’s notification is the step state laws require. Most states give companies a set window after discovering a breach to tell residents whose data was exposed, and the attorneys general collect the filings. Companies typically offer credit monitoring in these notices, and the filings become the documentary basis for the lawsuits that follow.

The interesting part of this one is where it started. Fireworks is not a payments processor or a payroll provider. It is a company that hosts models for other businesses, which means it holds whatever those customers sent it: prompts, outputs, and in many cases the underlying data those prompts were written about. A vendor that provides inference sits inside a customer’s workflow, and the credentials it holds reach further than its contract suggests.

That is a pattern the security industry has been describing for two years without much effect on procurement. The average large company now works with hundreds of software vendors, each with some level of access, and the question of which of them can be used as a stepping stone is rarely asked until one is.

The mechanics in this case are unremarkable. Credentials were taken, then used, then the attacker moved from the vendor’s environment into adjacent systems. Multi-factor authentication stops some versions of that sequence and not others, particularly when the credential belongs to a service account that was set up to run without a person attached to it.

Fireworks’ disclosure last month covered billing information and some private datasets. The Uber notice covers driver records. The two statements describe the same incident from different ends of the chain, and neither company has published a technical account of how they connect.

For Uber the exposure is mostly legal and reputational. The company was not the entry point, and its contracts with vendors almost certainly require the vendor to carry the cost of a breach it caused. Recovering that cost is a separate exercise from containing the damage, and the drivers whose licenses are circulating will not be affected by which company ends up paying.

For Fireworks the exposure is existential in a way that is hard to overstate. Inference is a low-margin business that competes on price and latency, and its customers are companies that care about where their data sits. A breach in which an attacker reached customer storage is the single fact that purchasing teams weigh most heavily when they choose a provider.

The regulatory response will follow the notification. State attorneys general have used breach filings to open inquiries into security practices, and the Federal Trade Commission has brought cases against companies whose safeguards it judged unreasonable. Both would look at the same questions: what access did the vendor have, what controls governed it, and how long did it take to detect the intrusion.

Uber’s own timeline is the part it will have to explain. The company says it was told on Oct. 9. Notices went out more than five weeks later, which is within most statutory windows and longer than customers usually tolerate.

There is a version of this incident that becomes a case study in vendor risk, taught in the same lectures as the attacks that arrived through heating contractors and payroll bureaus. The elements are all present: a supplier with deep access, a credential that was not protected the way it should have been, and a customer that found out from the supplier rather than from its own monitoring.

There is a duller version, in which the notices are filed, the credit monitoring is offered, a settlement is reached, and the only thing that changes is a line in procurement questionnaires asking inference providers to describe their access controls.

The 150,000 drivers will get a letter either way. What they will not get is an explanation of why a company that runs models for other businesses was holding their license numbers in the first place.

Related Posts

  • November 20, 2026
  • 15 views
A Lawmaker’s Privacy Suit Puts Model Design on Trial

For three years British courts have sidestepped the question of whether the company that builds an AI model answers for what its users produce with it. A written defence filed…

  • November 20, 2026
  • 12 views
Micron Has Sold 75% of Its 2027 Memory Output Before the Plant Opens

Micron Technology has committed 75% of the high bandwidth memory it expects to produce in 2027, a year for which most of that capacity has not been built. The company…