DoorDash Breach Incident Score: Analysis & Impact (DOO5203452112125)

In this Rankiteo incident briefing, we review the DoorDash breach identified under incident ID DOO5203452112125.

The analysis begins with a detailed overview of DoorDash's information like the linkedin page: https://www.linkedin.com/company/doordash-for-business, the number of followers: 1424762, the industry type: Software Development and the number of employees: 74124 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 766 and after the incident was 766 with a difference of 0 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on DoorDash and their customers.

DoorDash recently reported "DoorDash Data Breach via Social Engineering Attack (October 2025)", a noteworthy cybersecurity incident.

A sophisticated social engineering attack compromised personal information of DoorDash customers, Dashers (delivery workers), and merchants in October 2025.

The disruption is felt across the environment, affecting Internal systems (unspecified), and exposing Names, Email addresses and Phone numbers, with nearly Unspecified (potentially large, given 30M+ user base) records at risk.

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Employee verification process enhancements and System access reviews, and began remediation that includes User notifications (email) and Free credit monitoring via Experian (1 year), and stakeholders are being briefed through Public statements downplaying severity, emails to affected users with mitigation advice (password updates, account monitoring).

The case underscores how Ongoing (in collaboration with external security firms), teams are taking away lessons such as Human error remains a critical vulnerability; robust employee training and MFA enforcement are essential, Third-party risk management requires stricter controls, especially in gig economy platforms with vast PII repositories and Proactive measures (e.g., zero-trust architectures, AI-driven anomaly detection) are needed to prevent recurring breaches, and recommending next steps like Implement **zero-trust security models** to eliminate implicit trust in users/devices, Enforce **multi-factor authentication (MFA)** for all employee and third-party access and Conduct **regular phishing/social engineering simulations** to test employee vigilance, with advisories going out to stakeholders covering Users advised to update passwords, monitor accounts, and enable two-factor authentication.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Phishing: Spearphishing Link (T1566.002) with high confidence (95%), supported by evidence indicating phishing email targeting a DoorDash employee, tricked an employee into granting access to internal systems and Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), supported by evidence indicating employee into granting access to internal systems via social engineering. Under the Credential Access tactic, the analysis identified Steal Web Session Cookie (T1539) with moderate to high confidence (70%), supported by evidence indicating lack of robust multi-factor authentication (MFA) enforcement suggests session hijacking risk and Valid Accounts (T1078) with moderate to high confidence (85%), supported by evidence indicating tricked an employee into granting access implies misuse of legitimate credentials. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating exposing names, email addresses, phone numbers, and physical addresses from internal systems. Under the Exfiltration tactic, the analysis identified Exfiltration Over Alternative Protocol: Exfiltration Over Unencrypted/Obfuscated Non-C2 Protocol (T1048.003) with moderate to high confidence (80%), supported by evidence indicating data accessed by unauthorized party (method unspecified but implied transfer). Under the Impact tactic, the analysis identified Phishing for Information (T1598) with high confidence (95%), supported by evidence indicating exposed data can be weaponized for phishing, identity theft, or targeted scams and Malicious Crafted Email with Malicious Link/Attachment (T1659) with moderate to high confidence (85%), supported by evidence indicating high identity theft risk and targeted scams enabled by leaked PII. Under the Defense Evasion tactic, the analysis identified Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (80%), supported by evidence indicating lack of MFA enforcement allowed attacker to masquerade as legitimate user and Obfuscated Files or Information (T1027) with moderate confidence (65%), supported by evidence indicating no direct evidence, but sophisticated attack suggests possible obfuscation. Under the Persistence tactic, the analysis identified Account Manipulation: Additional Cloud Credentials (T1098.003) with moderate to high confidence (70%), supported by evidence indicating system access reviews post-incident suggests potential credential abuse for persistence. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.