Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Happened in the Uber Breach?

In September 2022 an attacker wore down a contractor with repeated MFA prompts, then found hardcoded admin credentials on a network share that unlocked Uber’s privileged access vault.

Illustration for the cybersecurity term Uber Breach
Home / Blog / Cybersecurity Terms / What Happened in the Uber Breach?
17 November 2026

What Happened in the Uber Breach?

What Happened in the Uber Breach?

On the evening of 15 September 2022, an attacker posted a message in Uber’s internal Slack announcing that the company had been breached. It was accurate. Uber later attributed the intrusion to the Lapsus$ group, and the individual responsible was reported to be eighteen years old.

The technical sophistication was minimal. The escalation path was not, and it is the part of the story worth studying, because it involved a mistake that exists in a great many estates right now.

The Way In

The attacker obtained the credentials of an external contractor, most likely bought from a dark web marketplace after they were harvested by information-stealing malware on the contractor’s personal device. The password alone was insufficient, because the account was protected by multi-factor authentication.

So the attacker attacked the second factor directly, first by repeatedly triggering push notifications over roughly an hour, and then by contacting the contractor on WhatsApp posing as Uber IT support and telling them the prompts would stop if they approved one. The contractor approved it.

This technique, variously called MFA fatigue, push bombing, or prompt bombing, works because push approval asks a human to make a security decision with no context: a notification appears, it is annoying, and accepting makes it stop. The countermeasure is number matching, in which the user must type a digit displayed on the login screen, or better, a phishing-resistant FIDO2 security key that cannot be approved by mistake and cannot be relayed at all.

The Escalation That Should Not Have Been Possible

With VPN access, the attacker scanned the internal network and found an unprotected network share. On it was a PowerShell script containing hardcoded administrative credentials for Uber’s privileged access management platform.

A privileged access management system exists to be the single controlled gateway to an organisation’s most sensitive secrets. Holding its administrator credential in plain text on an open file share inverts its purpose entirely. From there the attacker reportedly obtained access to AWS, Google Workspace, the Slack workspace, DUO, OneLogin, the SentinelOne console, and the company’s HackerOne bug bounty programme, which contained details of unfixed vulnerabilities.

Three Durable Lessons

  1. Push-based authentication is not phishing-resistant. Any factor a human can approve on request can be socially engineered. Number matching reduces the risk; hardware security keys bound to the origin remove it.
  2. Secrets scanning must cover file shares, not only repositories. Most organisations now scan source control for credentials. Far fewer scan the departmental shares, scripts directories, and documentation wikis where operational credentials actually accumulate.
  3. VPN access is not a security boundary. Once connected, the attacker found the network flat and scannable. Zero trust principles exist precisely to prevent a remote access session from functioning as general-purpose internal access.

The Governance Postscript

The 2022 incident is often conflated with a separate 2016 breach of Uber in which the data of 57 million riders and drivers was taken. That earlier case ended with the conviction in October 2022 of Uber’s former chief security officer for obstruction of justice and misprision of a felony, over the concealment of the breach from regulators and its characterisation of a payment to the attackers as a bug bounty. He was sentenced in May 2023 to three years’ probation.

For UK readers the parallel obligation is clear: UK GDPR Article 33 requires notification to the ICO within 72 hours of becoming aware of a qualifying personal data breach. Concealment is not a strategy, and the person who decides to conceal may carry personal consequences.

What to Change

FAQ – Frequently Asked Questions

What Is MFA Fatigue?

MFA fatigue, also called push bombing, is the repeated triggering of authentication prompts until the legitimate user approves one to make them stop. It works against push-based approval because the user is asked to make a decision with no context about where the request came from. Attackers often combine it with a call or message impersonating internal IT support.

How Do You Prevent Push Bombing?

Use phishing-resistant authentication such as FIDO2 security keys or passkeys, which are bound to the legitimate site and cannot be approved in response to someone else’s login attempt. Where push remains in use, enable number matching so the user must enter a code shown on the login screen, limit the rate of prompts, and alert on repeated denials.

Why Were Hardcoded Credentials So Damaging Here?

Because they belonged to the privileged access management platform, the system that holds every other high-value secret. Compromising it gave the attacker a single point of access to cloud consoles, collaboration tools, security products, and the bug bounty programme. A secret of that value stored in plain text on an accessible file share defeats the purpose of having a vault at all.

Was This the Same as Uber’s 2016 Breach?

No, they are separate incidents. The 2016 breach exposed data belonging to 57 million riders and drivers and was concealed, with the payment to the attackers recorded as a bug bounty. That concealment led to the criminal conviction of Uber’s former chief security officer in 2022. The 2022 intrusion described here was a fresh compromise through social engineering.

Related Terms

You May Be Interested In These

What Is Oil and Gas OT Security?

Cybersecurity Terms

17 November 2026

What Is Oil and Gas OT Security?

Read More
How Do You Investigate a Suspicious Email?

Cybersecurity Terms

17 November 2026

How Do You Investigate a Suspicious Email?

Read More
What Is Maritime AIS Security?

Cybersecurity Terms

17 November 2026

What Is Maritime AIS Security?

Read More