Uber driver data stolen after Fireworks AI breach; full scope remains unknown

The November 13 report, citing breach notices it reviewed, identifies stolen driver’s license information for these populations:

The three counts sum to about 7,870 people; Uber’s notice labels the Rhode Island figure approximate. South Carolina’s Department of Consumer Affairs, which receives businesses’ breach notices, independently lists Uber’s report with 3,430 affected residents and a November 10 reporting date.

This is a partial count, not a nationwide total or a measure of the share of Uber drivers affected. The report also identifies notifications in California without a count and an Illinois filing with the number pending. Uber did not disclose how many drivers it was notifying or how many customers were affected overall.

Company-reported chronology: Uber confirmed access to connected data on October 13; Fireworks describes further activity on October 23–24. The disclosures do not establish that the later activity caused Uber’s exposure. Chart: Magica. Source: Fireworks.

Fireworks’ initial account has been expanded

In its initial incident bulletin, Fireworks says it detected unauthorized use of internal credentials on October 6 and began containment that day. It began notifying affected customers on October 7 and says it had notified identified affected customers by October 9.

The company says an attacker accessed environment variables used in evaluation jobs in a limited number of customer accounts. It believes those variables included API keys and tokens stored as secrets—credentials that authorize access to services.

That bulletin says Fireworks had found no evidence of unauthorized access to customer models, datasets, training data, personal information or inference traffic, including prompts and outputs, within its security perimeter or control. It nevertheless instructs customers to investigate data accessible through exposed third-party credentials. Its assurance about its own systems therefore does not rule out access to connected data elsewhere.

Fireworks subsequently broadened its account in a security update dated November 9. It says investigators found impacts to account and billing information and, for a limited set of accounts, secrets, datasets and incomplete models.

The update also describes further activity: a cloud provider hosting Fireworks research and development machines suffered an incident on October 23. Fireworks says an attacker used that access on October 24 to reach its development machines and run an unauthorized workload, causing additional customer data exposure. It says it detected that activity the same day and, as of October 25, had found no further evidence of successful unauthorized access on its customer platform.

That later account provides context missing from the original bulletin’s assurances. It does not establish that the October 24 activity caused Uber’s exposure: Uber says it had already confirmed access to its data on October 13. The disclosures also do not establish that Uber driver’s licenses were used to train or evaluate a model.

A Fireworks spokesperson told the November 13 report that unauthorized access to some systems affected customer data, without answering further questions. The same report says workspace software provider Notion confirmed that its data was also stolen in the Fireworks hack. Uber is therefore not the only customer publicly acknowledging an impact.

The report says Fireworks attributed its breach to a financially motivated cybercriminal group seeking to sell stolen tokens for access to large language models. No known group had claimed responsibility. That account does not establish how Uber’s stolen records have been used.

An established AI supplier, and Uber’s security record

Fireworks was already publicly identifying Uber as a production AI customer in its October 28, 2025 funding announcement. The company described a service combining model inference—running models to generate responses—with customization, continuous evaluation and reinforcement learning using enterprise and application data. That explains the supplier’s general role, but not Uber’s specific use or why driver records were reachable.

In that announcement, Fireworks said it served more than 10,000 customers and announced a $250 million Series C at a $4 billion valuation, led by Lightspeed Venture Partners, Index Ventures and Evantic. The round included primary and secondary financing, so the headline amount should not be read as entirely new operating capital. Fireworks said funding would support global expansion, algorithms, software infrastructure, developer tools and hiring. These are company statements about its scale and investment plans, not evidence of the security controls protecting Uber’s data.

Uber also brings a relevant history. In its April 2018 announcement of an expanded proposed privacy settlement, the Federal Trade Commission, the federal consumer-protection agency, alleged that attackers in Uber’s 2016 breach used an access key posted by an engineer to download unencrypted files from third-party cloud storage. Those files included 600,000 names and driver’s license numbers of U.S. drivers and riders.

The FTC said Uber paid the intruders $100,000 through its bug bounty program and did not disclose the breach to consumers or the commission until November 2017. That history concerns both credential security and disclosure; it does not establish the cause of the current breach or a violation of any settlement. The November 13 report also identifies an earlier 2026 security incident at Uber Freight, the company’s truck-shipping unit, in which an extortion gang claimed data theft.

What drivers and customers still need to know

Uber’s notice says it had identified no misuse of recipients’ data to date. It offers free credit monitoring and fraud assistance through Cyberscout, a TransUnion company, with enrollment required within 90 days of the letter. The public template leaves the monitoring duration unspecified. Uber recommends reviewing account statements and credit reports and considering a fraud alert or security freeze.

For affected business customers, Fireworks’ initial bulletin describes revoking identified internal credentials, affected API keys and attacker-created keys, adding access restrictions and reviewing how evaluation jobs receive secrets. It warns that deleting a stored secret does not invalidate the underlying credential: third-party credentials must be rotated or revoked with their issuers, and associated access logs reviewed.

The next consequential disclosure is an account of Uber’s specific exposure: the complete affected population, the information taken, the credential and permissions used, and why those permissions reached driver records. Fireworks’ wider investigation makes the chronology essential. Separating the early credential compromise from the later activity is necessary to determine which protections failed for Uber and what changes address that failure.