# Uber (2022): what the sources say about the cloud incident

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Uber disclosed the incident on 16 Sep 2022. What was exposed, as the sources state it: The company stated that the attacker accessed several internal systems, downloaded some internal Slack messages, accessed information from an internal finance tool and its HackerOne dashboard, and that it had not found access to customer or user data held by its cloud providers.

- **Disclosed:** 16 Sep 2022
- **Incident window:** September 2022
- **Cloud or provider:** Google Workspace
- **What was exposed:** The company stated that the attacker accessed several internal systems, downloaded some internal Slack messages, accessed information from an internal finance tool and its HackerOne dashboard, and that it had not found access to customer or user data held by its cloud providers.
- **How access was gained:** The company stated that an attacker likely bought a contractor's corporate password after malware on the contractor's personal device exposed it, then repeated two-factor login requests until the contractor accepted one.
- **Access path:** [Stolen user credentials and session tokens](/access-paths/stolen-user-credentials/); also [Over-permissioned identities](/access-paths/over-permissioned-identity/)
- **Kind of control that addresses it:** require phishing-resistant MFA that cannot be satisfied by an approval prompt, and rate-limit and alert on repeated MFA requests

## In the words of the source

“It is likely that the attacker purchased the contractor’s Uber corporate password on the dark web, after the contractor’s personal device had been infected with malware, exposing those credentials.” (company statement, [Security update](https://www.uber.com/newsroom/security-update/))

## Primary sources

- company statement: [Security update](https://www.uber.com/newsroom/security-update/), dated 19 Sep 2022

If a field is wrong or a newer primary source exists, [write to the editor](mailto:editor@cloudsecuritybreaches.com?subject=Correction%3A%20Uber%20(uber-2022)) with the entry name in the subject.

## Related pages

- [GitHub users (phishing campaign reported by GitHub) 2022: ](/incidents/github-circleci-phishing-2022/)
- [MyRepublic Limited 2022: pdpc](/incidents/myrepublic-pdpc-2021/)
- [Mailchimp (Intuit) 2022: crypto social engineering](/incidents/mailchimp-crypto-social-engineering-2022/)

## Sources

- Security update: https://www.uber.com/newsroom/security-update/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/incidents/uber-2022/
