Uber is notifying close to 150,000 drivers that their personal information was stolen, and the company wants you to know one thing up front. Nobody hacked Uber. The break-in happened at Fireworks AI, a smaller company that runs artificial intelligence models for other businesses, and the stolen data was sitting in Uber's account there. The hackers used Fireworks' own internal login credentials, which meant they walked in through the front door with keys that worked. Uber says its own alarms never went off, because nothing about the login looked wrong. The drivers whose names, home addresses, dates of birth and license numbers were taken are now getting letters in the mail about a breach at a company most of them had never heard of.
The keys were already in the lock
According to breach notices Uber filed with state attorneys general, the timeline runs like this. On October 7, an unauthorized party used Fireworks' stolen internal credentials to get into Uber's account with the provider and reach Uber data stored there. Fireworks told Uber about the break-in on October 9, and Uber cut its data connections to the company the same day and started an investigation. By October 13, Uber had confirmed that the intruders had reached its data. The letters to affected drivers started going out on November 10, and a filing with Oregon's attorney general put the total at 149,346 people. The stolen data included names, home addresses, dates of birth and driver's license numbers, and in some cases images of the licenses themselves.
The alarms never went off
Uber says it had alerts set up to catch unauthorized access to its Fireworks environment, but the alerts did nothing. The hackers were using Fireworks' own internal credentials, so the systems saw a normal login from a trusted account and stayed quiet. That is the part that should worry every company that hands its data to a vendor. Your own security can be perfect and still fail, because the door the intruders used belongs to somebody else. TechCrunch first identified Fireworks as the unnamed provider in Uber's notices, and an Uber spokesperson later confirmed it. Fireworks, which lets developers run and fine-tune open-weight AI models, said the attack came from a financially motivated criminal group. The group steals access tokens for large language models and sells them, a scheme security researchers call LLMjacking, and Fireworks has hired Palo Alto Networks' Unit 42 team to investigate what happened.
Uber was not the only one hit
Uber was not the only customer caught in the Fireworks breach, and it may not be the last to send out notices. Notion, the productivity startup, and Cursor, the AI coding startup, have both confirmed that data was stolen from them in the same incident. Cursor said the attackers also infected some users' devices with backdoor malware, which is a nastier outcome than a stolen database. Fireworks also reported a second break-in on October 24, this time through a separate cloud provider that hosted its research machines. The company says no known criminal group has taken credit for the theft, and it did not answer questions about how the credentials were stolen in the first place.
This is Uber's second known data breach this year, after an incident at its Uber Freight trucking unit that an extortion gang claimed. The company has been here before, and the history is not flattering. Hackers stole data on 50 million riders and 7 million drivers in 2016, and the Lapsus$ group broke in again in 2022 by bombarding a contractor with login approval requests until one got through. Uber disclosed another breach in December 2022 after data was leaked from a third-party service provider. Each time, the weak point was not Uber's main systems. It was someone Uber trusted with access to them. BleepingComputer first reported the full scale of the driver notifications in the state filings.
Close to 150,000 drivers are now waiting on letters telling them their license numbers are in criminal hands, and the company that lost the data was not the company they drive for. Uber did the right things after it found out, cutting the connection and notifying drivers and regulators. The damage was already done by then, and it was done with keys that Uber never controlled. If your data lives with a vendor, your security is only as good as theirs, and this time theirs was not good enough.
---------------
Author: Alan Ward
Seattle News Desk
