---
title: "Uber security incident"
description: "What the retained public evidence establishes about the Uber incident, its attack path, impact, and response."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-09-19"
canonical_url: "https://www.ally.security/incidents/uber-security-incident-2022"
markdown_url: "https://www.ally.security/incidents/uber-security-incident-2022.md"
stix_url: "https://www.ally.security/incidents/uber-security-incident-2022/stix.json"
---

# Uber security incident

The retained public source describes the Uber incident as Lapsus$-linked; MFA fatigue (repeated push notifications) + Slack/internal wiki access. Other material details remain unresolved.

Last modified Sep 19, 2026 · 1 source

## 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

## 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](#source-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](#source-1)

### Actors

- **Lapsus$** — identified in the supported attack description. [1](#source-1)

### TTPs

- [T1621 — Multi-Factor Authentication Request Generation](https://attack.mitre.org/techniques/T1621/) — mapped from the cited behavior. [1](#source-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](https://www.uber.com/mx/es/newsroom/actualizacion-de-seguridad-3/). Details absent from that evidence are left unresolved rather than inferred. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/uber-security-incident-2022/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Security update

official · Uber

<https://www.uber.com/mx/es/newsroom/actualizacion-de-seguridad-3/>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   Uber security incident: The reviewed source documents the uber security incident involving Uber.
2. **Affected Organization · 100% confidence · current**  
   Uber security incident: Uber
3. **Resulted In · 82% confidence · current**  
   Uber security incident: Lapsus$-linked; MFA fatigue (repeated push notifications) + Slack/internal wiki access.
4. **Used Attack Technique · 90% confidence · current**  
   Uber security incident: https://attack.mitre.org/techniques/T1621/

</details>