← Blog

Uber Data Breach: Fireworks Driver Licences (Oct 2026)

Share on X

October 2026: Uber is notifying drivers that personal and driver-licence information stored with a tech provider was stolen. An Uber spokesperson told TechCrunch on 13 November that the provider is Fireworks.ai. Uber was notified on 9 October. See the Uber Fireworks breach record.

California listed Uber Technologies on 10 November with a 7 October breach date. State floors TechCrunch reviewed: Massachusetts 2,567, South Carolina 3,430, Rhode Island 1,873. Illinois pending. California count unpublished. Sum of the three published floors is 7,870, not a nationwide total. This is Uber's second known 2026 event after Uber Freight Helix.

What happened at Uber?

Hackers broke into Fireworks, stole internal credentials, and used them to reach Uber data the vendor held. Fireworks confirmed unauthorised access to some of its systems when TechCrunch asked. Uber deferred detail to Fireworks. The path is a vendor copy, not a statement that Uber's production rider app was popped on 7 October.

Fireworks first described an October incident around evaluation-job secrets, then widened it on 9 November to billing metadata and some incomplete weights. Notion chats are a separate customer row. The Fireworks and Notion posts cover those slices. Driver licences live on this Uber row.

What data was exposed?

Personal information and driver licences of drivers whose records sat with Fireworks. Nationwide unpublished. recordsAffected is 7870 as the three-state attested floor. Do not add California or Illinois until those filings publish a number.

A licence number plus a name is enough for fake insurance and identity-theft applications. Uber has not said rider trip histories were in this vendor file.

The Uber Freight Helix post is a different 2026 event. Do not add the two censuses together.

Who is affected?

Drivers in states that received notices, starting with Massachusetts, South Carolina, Rhode Island, Illinois and California. Other states may follow. Riders are not automatically in this row. People who only used Uber Eats and never drove are outside the current notice.

More on the company is on the Uber company page. Fireworks is the vendor; Uber is the data controller for the driver file it stored there.

What should drivers do?

  1. Read the Uber driver notice if you received one. Compare it with the in-app message channel you already use.
  2. Watch for fake 're-verify your licence' portals that ask for a photo of both sides of the card.
  3. If you live in a state without a published count, you may still be in the file. Wait for mail before assuming you are out.
  4. Place a freeze if your licence number was in the notice.
  5. Uber will not collect a card CVV through a new domain to restore driver status.

Fireworks has not published a people count of its own. Do not treat 91,000 or any other vendor marketing figure as this census.

Is this the same as Uber Freight?

No. Uber Freight Helix was an August investigation after a leak-site claim against the freight unit. This October vendor path is Fireworks and driver licences. Catalog them separately.

The unverified Helix listing against Uber itself remains a different row. TechCrunch's 13 November piece is confirmation of the Fireworks driver notices, not a Helix update.

Frequently asked questions

How many drivers were affected?

Unpublished nationwide. Three-state floor 7,870 (2,567 Massachusetts, 3,430 South Carolina, 1,873 Rhode Island). California unpublished. Illinois pending.

Which vendor?

Fireworks.ai, named by an Uber spokesperson to TechCrunch on 13 November 2026.

When was Uber told?

9 October 2026, according to the attorney-general notices TechCrunch reviewed.

Were rider trips copied?

Not named. The notices describe driver personal and licence information.

Is this ransomware?

Not named. Fireworks described a financially motivated actor interested in LLM tokens. No public claim on the Uber driver slice.

Sourcing note: TechCrunch 13 November 2026, Uber spokesperson, California AG listing 10 November, Fireworks 9 November bulletin.

Do not download alleged Uber dumps. This catalog does not link them. A later leak-site post is still an unverified brand until Uber names it.

Compare later mail with uber.com. Uber will not ask for a card CVV or a one-time code through a new website to finish this investigation.

Do not merge this row with the Uber Freight Helix row. They are separate catalog files even when they share a season or a vendor class.

If you did not receive a letter, you may still be in an unpublished state filing. Ask Uber in writing whether your identifier sits in the reached file.