---
title: "DoorDash security incident"
description: "What the retained public evidence establishes about the DoorDash 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/doordash-security-incident-2022"
markdown_url: "https://www.ally.security/incidents/doordash-security-incident-2022.md"
stix_url: "https://www.ally.security/incidents/doordash-security-incident-2022/stix.json"
---

# DoorDash security incident

The reviewed public source documents a cybersecurity incident involving DoorDash, while leaving material details unresolved.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Food delivery
- **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

The reviewed public record documents a cybersecurity incident involving DoorDash in 2022. It does not establish the initial access path with enough specificity to describe it here. [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 reviewed source does not establish a sufficiently specific initial-access vector. The article therefore does not infer credentials, malware, a vulnerability, or a social-engineering path.

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

- No specific MITRE ATT\&CK technique is currently mapped for this case.

## Response

The reviewed source does not describe containment, notification, or restoration steps in enough detail to summarize them responsibly.

This account is bounded to [How we're responding to a third-party vendor phishing incident](https://help.doordash.com/es-us/dashers/article/how-we-re-responding-to-a-third-party-vendor-phishing-incident-dx). 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/doordash-security-incident-2022/stix.json>)

## Sources

Primary source records used to research this incident.

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

### How we're responding to a third-party vendor phishing incident

official · DoorDash

<https://help.doordash.com/es-us/dashers/article/how-we-re-responding-to-a-third-party-vendor-phishing-incident-dx>

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

Review the supporting structured claims.

1. **Affected Organization · 100% confidence · current**  
   DoorDash security incident: DoorDash
2. **Resulted In · 100% confidence · current**  
   DoorDash security incident: The reviewed source documents the doordash security incident involving DoorDash.

</details>