# Uber confirms hackers stole thousands of drivers' licences

> Uber has confirmed hackers took thousands of drivers' licence details. Its 2016 breach, with 600,000 US licence records, offers the detailed comparison.

- Published: 2026-11-13
- Topic: [Security](https://futuretechnologyhq.com/topic/security/)
- URL: https://futuretechnologyhq.com/article/uber-confirms-hackers-stole-thousands-of-drivers-licences/
- Publisher: [Future Technology HQ](https://futuretechnologyhq.com/), free to read. Quote as "Future Technology HQ" with a link to the article.

## Key points

- Uber has confirmed a breach affecting thousands of drivers' licence details
- The 2016 Uber breach is the detailed comparison: 57 million users, 600,000 US licence numbers, and a $100,000 payment disguised as a bug bounty
- Credentials left in a code repository gave the 2016 attackers the keys to cloud storage, a failure IT teams can check for today

## Article

Uber has confirmed that hackers stole thousands of drivers' licence details in a data breach, according to TechCrunch. Uber has been through a breach involving driver data before, in 2016. Its 2016 breach exposed 600,000 US driver licence numbers, and it was kept from the public for about a year, with the payment to the attackers disguised as a bug bounty.

The new confirmation is the news. The 2016 case is the detailed comparison, because the sources give figures for it.

## The headline numbers

The confirmation reported by TechCrunch concerns thousands of drivers' licences. The figures below come from the 2016 incident, as reported by The Register in November 2017, citing Uber CEO Dara Khosrowshahi and Bloomberg.

| Measure | 2016 breach figure |
| --- | --- |
| Passengers and drivers affected | 57 million |
| US driver records including licence numbers | 600,000 |
| Payment to the attackers | $100,000 |
| Attackers | Two individuals |

The newly confirmed "thousands" is a long way below the 57 million affected in 2016.

## What the data shows

Driver licence data is a different class of exposure from an email address. A licence number tied to a name is a fixed identifier. Unlike a password, it cannot simply be reset by the person it belongs to, so the harm from its theft can outlast the incident itself.

The 2016 mechanics are instructive. According to Bloomberg, as relayed by The Register, two attackers took the keys for Uber's AWS S3 data stores from its GitHub code repository in October 2016. S3 is Amazon's cloud object storage service. Khosrowshahi said the data sat on "a third-party cloud-based service" and that Uber's corporate systems and infrastructure were not breached.

The second pattern is the response. Uber's then chief of information security, Joe Sullivan, ordered the attackers to be paid off, the stolen files erased and the whole matter hushed up, according to the reporting. The payment was disguised as a bug bounty, a reward scheme meant for researchers who report flaws, complete with non-disclosure agreements. Sullivan and one of his lieutenants were ousted after the new CEO's investigation.

Khosrowshahi, who had been installed at the San Francisco company over the summer, also said that security breaches would be disclosed publicly in future as required.

## Reading Uber's 2016 statements with care

The 2016 figures carry caveats of their own. Khosrowshahi said outside forensics experts had not seen any indication that trip location history, credit card numbers, bank account numbers, Social Security numbers or dates of birth were downloaded. That is a statement about what investigators did not see, rather than a guarantee about what was taken.

The Register took a sceptical view of another phrase in his statement. Uber said it had "obtained assurances" that the downloaded data had been destroyed. The Register called that "a funny way of putting it", and the arrangement it describes involved a payment of $100,000 to the people who held the data.

## How the two cases compare

Against 2016, the newly confirmed breach looks smaller in volume. Against the standard Khosrowshahi set after that episode, the test is different. He said security breaches would be disclosed publicly in future as required, that anyone affected would be notified, and that the affected accounts were being monitored and flagged for "additional fraud protection".

California's breach notification law, as The Register described it, requires disclosure in "the most expedient time possible and without unreasonable delay". The Register noted that a gap of 12 months did not fit that description. New York Attorney General Eric Schneiderman also launched an investigation into the 2016 handling. Those are the regulatory consequences on record for the earlier case.

## So what?

The 2016 case offers a practical checklist for security teams, particularly those that manage platform workforces and the identity documents they hold:

- Scan code repositories for committed cloud keys, and rotate any found. This is the exact failure behind the 2016 breach.
- Restrict access to cloud storage accounts and strengthen the controls around them, as Uber said it did after the earlier incident.
- Decide in advance who may authorise contact with extortionists, and ensure legal and compliance sit in that decision. The 2016 payment was disguised as a bug bounty, yet the breach came to light a year later.
- Keep an incident timeline that can survive scrutiny. The 2016 breach reached the public only after a year, and two executives were ousted after the new CEO's investigation.

Related guidance on [UK GDPR and backups](/article/uk-gdpr-backups-retention-right-to-erasure/) covers the retention duties that shape what data exists to be stolen. Teams building a wider response plan can start with the [ransomware guide for UK organisations](/article/ransomware-guide-uk-organisations/), which covers the decisions that follow a theft-and-extortion event.

## Key takeaways

Uber has confirmed that hackers stole thousands of drivers' licence details. The 2016 case shows what matters most in any such incident: how the keys leaked, how quickly the company told people, and whether anyone tried to bury it. According to Bloomberg, its attackers got in using keys taken from a code repository, and the breach was not disclosed for a year.

## Sources

- [TechCrunch](https://techcrunch.com/2026/11/13/uber-confirms-hackers-stole-thousands-of-drivers-license-information-in-data-breach/)
- [The Register](https://www.theregister.com/2017/11/22/uber_2016_data_breach)
