Fireworks AI Data Breach: Uber Notifies 149,346 People After Hackers Stole Driver License Data From Its AI Vendor, What Is Confirmed and What Businesses Should Check
Uber says hackers stole drivers' names, addresses, dates of birth and license numbers in a breach at vendor Fireworks AI, and it notified 149,346 people. Here is what is confirmed, what is not known and what to check this week.
Where Worldwide
On this page 9 sections
Uber has confirmed that hackers stole drivers' personal information, including driver's license numbers, in a breach at one of its outside vendors, and it says it notified 149,346 people. TechCrunch has identified that vendor as Fireworks AI, a service developers use to access open-weight AI models, so the data was taken from an AI provider, not from Uber's own app.
If your business hands employee or customer data to any outside service, AI tools included, this story applies to you too: your people can be exposed in a breach on systems you do not control and never see.
What happened in the Fireworks AI breach
Here is the timeline as the sources state it:
- October 9: Uber says the provider notified it on this date that hackers had broken in.
- October 23 to October 30, 2026: Fireworks says a second incident ran during these dates.
- TechCrunch reported Uber's confirmation and the number of people notified.
Of the second incident, Fireworks says: "This incident is also contained and remediated."
The dates matter. Uber heard from the vendor before the dates Fireworks gives for its second incident, and Fireworks itself calls the October 23 to 30 event its second incident. Our sources do not say which incident Uber's driver data was taken in, or when the first one began.
What Uber driver data was stolen
According to TechCrunch, the stolen data includes affected drivers' names, addresses, dates of birth and driver's license numbers. Put together, those details can be used to impersonate someone, pass basic identity checks or make a scam call or email sound convincing.
Uber described the notices this way: "The notices to drivers are in relation to a security incident impacting one of our third-party vendors". TechCrunch also notes that this is Uber's second known data breach this year.
Uber is not the only customer affected. TechCrunch reports that two other organizations have both confirmed that they had data stolen during the Fireworks hack. We have not verified their names from a primary source, so we do not name them here.
Who is behind the Fireworks AI hack
The sources we reviewed do not name a group. The Fireworks security bulletin says: "The evidence indicates links to a cybercriminal threat actor group, which is financially motivated." Fireworks links the intrusion to a group engaged in LLMJacking, a term generally used for abusing someone else's paid access to AI models.
Was my Fireworks AI account affected?
If your business has a Fireworks account, some of your data was probably included. Fireworks says the attackers "accessed account and billing information for all accounts created before Oct 30th". Any account opened before October 30 is in that group.
What the bulletin text we verified does not say: whether API keys, uploaded files, or model inputs and outputs were accessed. Treat that as unknown, not as safe.
What is confirmed and what is not known
| Claim | Status | Source |
|---|---|---|
| 149,346 people notified | Stated by Uber | TechCrunch |
| Names, addresses, dates of birth and license numbers stolen | Reported | TechCrunch |
| The vendor is Fireworks AI | Reported by TechCrunch | TechCrunch |
| Uber was notified by the provider on October 9 | Stated by Uber | TechCrunch |
| Second incident ran October 23 to October 30, 2026 | Stated by Fireworks | Fireworks bulletin |
| Account and billing data accessed for all accounts created before October 30 | Stated by Fireworks | Fireworks bulletin |
| Second incident contained and remediated | Stated by Fireworks | Fireworks bulletin |
| Financially motivated cybercriminal group | Fireworks' assessment | Fireworks bulletin |
Not known from the sources: how the attackers got in, when the first intrusion started, which incident involved Uber's data, why driver records were held at an AI provider, whether the stolen data has been sold or published, and who the attackers are.
What to do this week
| Who | What to do | How to check |
|---|---|---|
| Businesses with a Fireworks AI account | Assume account and billing details are exposed if the account was created before October 30 | Check the account creation date and billing contacts in your Fireworks account |
| Businesses with a Fireworks AI account | Rotate Fireworks API keys as a precaution, since the sources we reviewed do not say whether keys were taken | Create new keys, update your apps, then revoke the old ones |
| Businesses with a Fireworks AI account | Watch for usage or charges you did not expect | Compare recent usage and invoices with your normal pattern |
| Staff who drive for Uber or received a notice | Watch for identity fraud and for phishing that uses their real details | Review credit reports and consider a credit freeze where available |
| Every business | List every vendor, AI tools included, that holds employee or customer personal data | A one-page inventory: vendor, what data, who approved it |
| Every business | Ask each AI vendor how and how fast it will tell you about a breach | Check your contract or terms of service |
| Every business | Stop sending personal data to AI services that do not need it | Review what your integrations actually send |
One more point for staff: breach news is often followed by fake breach notice emails. Tell people to log in through the official app or website rather than clicking links in messages about this incident.
Why a vendor breach matters for your business
Uber's drivers were exposed through a vendor. Uber describes the incident as one affecting a third-party vendor, and the data still ended up in criminals' hands. Every time your business connects a service to your data, a copy of that data, or access to it, sits on someone else's servers under someone else's security.
AI services are the newest link in that chain. Many businesses now wire them into support desks, document processing, onboarding and custom apps, often quickly and without a vendor review. If your website or customer app sends names, addresses or ID details to an AI API, a breach at that provider can become a breach notice you have to write.
If you are building or buying AI features, the question of who keeps them secure after launch is the one we raised in AI Can Build Your App. Who Is Going to Keep It Running?. For some workloads, running models on infrastructure you control is worth weighing, which is what our self-hosting and infrastructure work covers. And the same ownership question applies to every other system you rely on, as we covered in Who Is Patching the Software That Runs Your Business?.
Fireworks AI breach questions people are asking
Was Uber hacked?
Uber says the notices relate to a security incident at one of its third-party vendors. TechCrunch identifies that vendor as Fireworks AI.
How many Uber drivers were affected?
Uber said it notified 149,346 people in total that their information was taken in the breach at Fireworks.
What information was stolen in the Uber driver data breach?
Names, addresses, dates of birth and driver's license numbers, according to TechCrunch.
Is the Fireworks AI breach over?
Fireworks says its second incident, which ran October 23 to October 30, 2026, is contained and remediated. Our sources do not give a full account of the first incident.
Who hacked Fireworks AI?
No group is named in the sources. Fireworks links the intrusion to a financially motivated cybercriminal group engaged in LLMJacking.
Were Fireworks AI API keys stolen?
The sources we verified do not say. Fireworks confirms that account and billing information was accessed for all accounts created before October 30. Rotating your keys is a sensible precaution.
Should my business stop using Fireworks AI?
That is your call. Before deciding, ask Fireworks exactly what was accessed for your account, review what data you send it, and remove anything personal that does not need to be there.
The bigger lesson
Your data is only as safe as the least careful vendor holding a copy. Find out which vendors have it, send them only what they need, and plan for what you will do the day one of them sends you a breach notice.
To have your apps and vendor connections reviewed, see security hardening or request a quote.
Get security alerts like this by email, with the free checklist, at security alerts.
Sources: TechCrunch: Uber confirms hackers stole thousands of drivers' license information; Fireworks AI: October 2026 security incident update.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Uber Data Breach: Hackers Used Vendor Fireworks AI's Credentials to Reach Driver's License Data on 149,346 People, and What Businesses Should Check
Uber says compromised credentials at its vendor Fireworks AI let hackers take names, addresses, dates of birth...
PostgreSQL Vulnerability CVE-2026-6460: Object Creators Can Run Code on the Database Server, 52 Flaws Fixed, and Why Updating Without Rebuilding Extensions Is Not Enough
PostgreSQL fixed 52 security flaws, including CVE-2026-6460, which lets an account that can create objects run...
ScreenConnect Vulnerability CVE-2026-84869: Exploited Flaw Runs on Technician Machines, Why Server Updates Fall Short, and Version 26.6.5
A ScreenConnect flaw, CVE-2026-84869, is being exploited, and the vulnerable code runs on the technician's mac...