Uber Driver License Data Stolen in Third-Party Breach
Uber says hackers took driver's license information held by AI infrastructure firm Fireworks AI, affecting close to 150,000 people.
According to TechCrunch, Uber says hackers stole driver's license information on close to 150,000 drivers. The company attributes the theft to a security incident involving AI cloud company Fireworks AI, which stored the records on Uber's behalf.
TechRadar reports that the breach was disclosed by Uber as a third-party incident and that the number of affected individuals is described as thousands. The outlet notes that Uber has filed a notice with several US state attorney general offices and has shared a copy of the letter it is sending to affected people.
According to TechRadar, the letter says Uber is notifying affected users and offering identity theft protection and credit monitoring while its investigations continue. Both outlets describe the compromise as coming from a provider rather than from Uber's own systems.
TechRadar also reports that Fireworks was targeted in broader attacks known as LLMjacking, in which attackers attempt to misuse access to AI model services. The reporting does not establish how the attackers gained access or what else, if anything, was taken.
The public accounts available so far leave several details open, including the exact count of affected drivers and the full scope of the data involved.
Background
Ride-hailing and delivery platforms collect a large amount of personal information about the people who work on them. To verify identity, confirm eligibility to drive, and meet insurance and background-check requirements, companies often store copies of government identification such as driver's licenses. That data is valuable to criminals because it can be used to open accounts, pass identity checks, or commit fraud in a victim's name.
Modern software increasingly depends on outside vendors. A large company may rely on dozens or hundreds of third-party services for hosting, payments, analytics, customer support and artificial intelligence tools. Each connection adds another place where data can be exposed, and a breach at a vendor can affect customers of that vendor who never interacted with it directly. Security teams refer to this as supply chain or third-party risk.
AI infrastructure has become a newer and more sensitive part of this chain. Companies that run or resell access to large language models and related tools often hold credentials, logs and customer data, and they can be attractive targets. The term LLMjacking describes attacks in which criminals steal or abuse access keys for AI services, sometimes to run computing workloads at the victim's expense or to extract data.
Breach notification rules in the United States are set mainly by individual states, and many require companies to tell affected residents and state regulators when certain personal information is exposed. Offering credit monitoring or identity protection is a common response, though its value depends on the type of data involved. Driver's license numbers are generally considered harder to replace than a password, which makes long-term monitoring more relevant.
Why it matters
For the drivers affected, the practical concern is that a government-issued identification number, paired with a name and other details, can be misused for a long time. Unlike a credit card, a license cannot be quickly canceled and reissued without a bureaucratic process, so the risk can linger well after the initial news fades. People who drive for ride-hailing services often rely on that income, which raises the stakes of any uncertainty about their personal information.
The incident also highlights a broader tension in the platform economy. Companies collect identity documents to meet safety and regulatory obligations, but every copy stored creates exposure. Whether a firm needs to keep full images or numbers, and for how long, is a question that security teams and privacy advocates have debated for years. A breach at a vendor shows that a company's responsibility does not end at its own firewall.
For the AI sector, the case is a reminder that the infrastructure behind popular tools is itself a target. As more businesses route sensitive workflows through hosted AI services, a compromise at one provider can reach many downstream customers at once. That concentration can make attacks more efficient for criminals and harder for individual customers to assess in advance.
Finally, the disclosure illustrates how breach response has become a standard playbook: notify regulators, write to affected people, and offer monitoring. Whether that playbook is enough depends on how quickly people are told, how clearly the notices explain the risk, and whether the affected information is ever used in fraud.
What to watch
The most important open question is the final count of affected people, since early reports describe the total in different terms. Watch for updates to the notices filed with state attorneys general, which often contain more precise figures and timelines.
Next, look for any statement from Fireworks AI about how the access was obtained and what safeguards have changed. Information about whether the LLMjacking activity is linked to this incident would also shape how widely the lessons apply.
Drivers should watch for the specific instructions in the notification letters, including how to enroll in the offered monitoring and what signs of misuse to report. Regulators may also respond, and any inquiry could clarify what standards apply to vendors that handle identification documents.
Viewpoints
Commentary from our columns: three angles on this story.
The Skeptic open questions and weak points
Offers of free credit monitoring have become so routine after breaches that they can feel like a formality. The question worth asking is whether they address the actual problem. A credit monitoring service can alert someone when new accounts are opened in their name, but it cannot restore a driver's license number to secrecy. Once an identifier is out, the protection it offers depends on how carefully other institutions check identity, and that varies widely.
We also do not yet have a complete picture. Reports describe the total as close to 150,000 in one place and as thousands in another, and the public explanation of how the attackers got in remains thin. Before accepting the reassurance, readers should want a clear count, a clear timeline, and a clear description of what changed at the vendor. Until those arrive, it is reasonable to treat the response as a starting point rather than a resolution.
The Rulebook privacy, safety and regulation
Driver's license numbers are sensitive for a specific reason: they are issued by governments, they are hard to change, and they are often accepted as proof of identity. When a platform stores copies of these documents, it takes on a duty to limit access, encrypt what it keeps, and delete what it no longer needs. A vendor relationship does not transfer that duty away. The company that collected the information remains the one drivers trust.
Regulation in this area is uneven across states, so the notices filed with attorneys general matter. They create a record of what was disclosed and when. Lawmakers may ask whether identity documents should be collected at all in some cases, or whether retention limits should be stricter. Affected drivers should read the notices closely, follow the enrollment steps, and watch for unusual activity involving their name and license details.
The User what changes for people who use it
For a driver, a breach notice is not an abstract story. It arrives as a letter, sometimes in an envelope that looks like junk mail, and it asks for a few minutes of attention to sign up for a service and check some accounts. Many people will set it aside, which is understandable when money and time are tight. Yet the people most affected are often the ones least able to absorb a fraud problem, such as a missed payment or a denied application.
The practical step is simple: read the letter, enroll if the offer is useful, and keep an eye on financial statements for a while. It also helps to know that a license number alone is not usually enough to empty an account, but it can be one piece in a larger effort to impersonate someone. Drivers who understand that can respond calmly rather than panicking, and they can act before a problem grows.