Summary
- Environment: Rideshare/Tech
- Operational impact: The reviewed source does not establish a precise operational or data impact
- Financial impact: No financial figure is established by the reviewed source evidence
- Record status: Developing record. Reviewed September 19, 2026; updated as evidence emerges.
What happened
In 2022, Uber experienced an incident in its rideshare/tech environment. The retained source describes the attack path as follows: Lapsus$-linked; MFA fatigue (repeated push notifications) + Slack/internal wiki access. [1]
Impact
- The reviewed source does not establish a precise affected-person count, data scope, or operational consequence.
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.
Threat Group & Attack Vector
The retained source describes the attack path as follows: Lapsus$-linked; MFA fatigue (repeated push notifications) + Slack/internal wiki access. The canonical record does not add intrusion steps beyond those supported by the source. [1]
Actors
- Lapsus$ — identified in the supported attack description. [1]
TTPs
- T1621 — Multi-Factor Authentication Request Generation — mapped from the cited behavior. [1]
Response
The reviewed source does not describe containment, notification, or restoration steps in enough detail to summarize them responsibly.
This account is bounded to Security update. Details absent from that evidence are left unresolved rather than inferred. [1]