Uber Driver Data Breach: How a Stolen AI Supplier Login Exposed Identity Records

Uber did not lose its drivers' data through a hole in its own network. It lost it through a key held by someone else. Attackers used stolen login credentials belonging to a technology supplier to reach personal records, including driving licence details.

Today is November 15, 2026, and Uber is sending breach letters to affected drivers. The supplier, Fireworks AI, is an AI service provider, which is why this case matters well beyond Uber. Many companies now connect their data to outside AI services, and few have checked what those services can reach if their own logins are stolen.

What happened, step by step

According to Uber's notification filed with California's attorney general, the timeline runs like this:

1. October 6: Fireworks detected unauthorised use of its internal credentials.
2. October 7: the breach date recorded in California's breach register.
3. October 9: Fireworks told Uber that an unauthorised party had used those credentials to access Uber's account with the provider.
4. Uber says it immediately cut its data connections with the supplier and started investigating.
5. October 13: investigators confirmed the credentials had been used to access Uber information, including personal records of the people now being notified.
6. November 10: the date on Uber's notification letter.

The key point is where the attackers got in: through the supplier's access, not through Uber's own front door. The disclosures do not show that attackers got into Uber's wider corporate network or had unrestricted access to its services.

How many people were affected?

The numbers are still moving, so read them carefully.

• Early state filings listed 2,567 people in Massachusetts, 3,430 in South Carolina and 1,873 in Rhode Island. That is 7,870 people across three states, not a national total.
• A newer record on the breach tracker BreachTally, citing a Texas attorney general filing dated November 13, lists 149,346 affected people overall, including 4,296 in Texas. Another tracker, DisclosureLens, shows the same figures.

Both trackers list names, addresses, dates of birth, driving licence numbers and government ID numbers among the data involved. However, the original Uber entry could not be independently retrieved from the Texas portal, so treat the larger number as reported by trackers, not as a confirmed statement from Uber. Also, a list of data types in a filing does not mean every person lost every type.

Stolen secrets versus stolen data

Fireworks' first security bulletin said the attackers exposed environment variables in evaluation jobs for a limited number of customer accounts. Environment variables are settings a program reads when it starts, and they often hold secrets such as API keys and tokens, which act like passwords for other systems.

At that stage Fireworks said it had not seen unauthorised access to customer personal information, models, datasets or inference traffic inside its own security boundary. That sounds reassuring, but it misses a point. A stolen key is not just data. It is a way into whatever the key unlocks. So an investigation has to ask two questions: what did the attacker take, and what did those keys then let them reach?

Fireworks told affected customers to rotate the exposed credentials with whoever issued them, and to check recent activity. It also warned that deleting a stored secret does not cancel it. The key keeps working until the issuer revokes it.

A second, separate intrusion

Fireworks' November 9 update widened the picture. It reported impacts on account and billing information, secrets, datasets and incomplete models for a limited set of accounts.

It also described a different episode. On October 23, a cloud provider hosting Fireworks research and development machines had its own security incident. The next day attackers reached those machines and ran an unauthorised workload, causing more customer-data impact.

That happened after Uber had already been told and had confirmed exposure, so it cannot explain Uber's original timeline. The public disclosures also do not show that every Fireworks customer was hit the same way. Fireworks said it was working with Palo Alto Networks Unit 42, had tightened credential controls, restricted network access, improved monitoring and temporarily turned off some self-service dataset uploads and downloads.

The money behind it: LLMjacking

Fireworks linked the activity to criminals trying to profit from stolen access to large language models, a practice called LLMjacking. Think of it as stealing someone's electricity, except the electricity is expensive AI computing.

A November 2 report from Google Threat Intelligence Group and Mandiant describes the market. Criminals collect valid credentials or find exposed model services, then resell that computing power through illegal gateways that spread requests across many stolen accounts. The real account owner gets the bill. Mandiant reported cases of more than $100,000 in fraudulent charges in a single day, and up to $1 million in total at some organisations before access was cut. Those figures come from other investigations, not from Uber.

The same research says attackers, once inside, search code repositories, cloud environments and data stores for more credentials. That is why an attack aimed at free AI computing can still end with personal data exposed. It does not prove which methods were used against Uber; the notification only names compromised supplier credentials.

What drivers should do now

Rohit drives for a ride-hailing service and receives a breach letter. A notification is not proof of identity theft, but it is a good reason to act. Here is a sensible plan.

Step 1: Read your own letter closely

Check which data types the letter says were involved for you. Your steps depend on that.

Step 2: Enrol in the free monitoring

Uber offers free credit monitoring and fraud help through Cyberscout, a TransUnion company. You must enrol within 90 days of the letter. The published template does not say how long monitoring lasts, so check your own notice.

Step 3: Know what monitoring cannot do

California's guidance points out that credit monitoring spots some changes to your credit file. It does not catch every kind of fraud, such as misuse of an existing payment account. Keep checking your bank and card statements yourself.

Step 4: Protect your licence and ID details

California residents who suspect misuse of their licence details are directed to the state's driving licence fraud unit. Elsewhere, contact your licensing authority.

Step 5: Use official help if something goes wrong

The Federal Trade Commission points people to IdentityTheft.gov for steps matched to the exposed data, and for reporting and recovery if misuse is found.

Step 6: Watch for scam messages

Criminals often follow a breach with fake "verify your account" messages. Contact the company only through its official app or website.

What companies should learn

Uber said it had not found misuse of recipients' information at the time of writing. Still, open questions remain: why identity information was reachable through the supplier, what permissions allowed it and how long they existed. An AI supplier's involvement also does not mean the documents were used to train models, or that a model caused the breach.

For any company using AI services, the practical lesson is that supplier reviews must cover credentials, stored datasets, development machines and connected systems, not only the model. A promise not to keep your prompts covers only one small part of the risk.

Conclusion

The Uber driver breach is a supplier-access story first and an AI story second. A stolen key at a third party reached sensitive identity data, the true size of the exposure is still unclear, and the attackers' motive appears to be stolen AI computing. Drivers should read their letters and use the offered help. Companies should map exactly what each supplier's credentials can reach, and cut what is not needed.

Merits

• Uber cut its supplier connections quickly once it was told.
• Free credit monitoring and fraud help are offered to recipients.
• Fireworks published bulletins and clear advice to rotate exposed keys.
• The case gives security teams a concrete reason to review supplier access.
• Public reporting on LLMjacking helps companies spot unusual AI usage bills early.

Demerits

• Sensitive identity data was reachable through a third-party connection.
• Affected-people numbers differ widely between sources and are not fully verified.
• Credit monitoring does not catch every kind of fraud.
• Two separate Fireworks incidents make the timeline easy to misread.
• Key technical details of how Uber's data was reached are not public.

Caution

This article is educational. The example person Rohit is a placeholder for any affected driver, and the steps must be matched to your own notice and location. The facts here summarise public notifications, company bulletins and third-party trackers as reported at the time of writing, and some figures, including the larger affected-people total, have not been independently confirmed. Verify details against official notices and authorities before relying on them.

Frequently asked questions

• What happened in the Uber driver data breach? — Attackers used compromised credentials belonging to Uber's AI supplier, Fireworks AI, to access Uber data, including personal records of drivers.
• How many Uber drivers were affected? — Early state filings covered 7,870 people in three states, while trackers citing a Texas filing list 149,346, a figure not yet independently confirmed.
• What data was exposed in the Uber breach? — Filings and trackers list names, addresses, dates of birth, driving licence numbers and government ID numbers, though not every person had every field exposed.
• Was Uber's own network hacked? — The disclosures describe access through the supplier's account, not a compromise of Uber's wider corporate network.
• What is LLMjacking? — It is the theft and resale of access to large language model services, leaving the real account owner to pay the computing bill.
• What should affected drivers do? — Read the notice, enrol in the free Cyberscout monitoring within 90 days, watch bank statements and use IdentityTheft.gov if misuse appears.
• Does deleting an exposed API key make it safe? — No, deleting a stored secret does not cancel it; the issuer must revoke or rotate the key.
• Were drivers' documents used to train AI models? — Nothing in the public disclosures shows that; supplier involvement alone does not establish it.

Tags

#databreach #uber #cybersecurity #thirdpartyrisk #supplychainsecurity #llmjacking #identitytheft #aisecurity #credentialsecurity #privacy