DoorDash Breach Incident Score: Analysis & Impact (DOO5993759111725)

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

The analysis begins with a detailed overview of DoorDash's information like the linkedin page: https://www.linkedin.com/company/doordash, 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 633 and after the incident was 582 with a difference of -51 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 Affecting 4.9 Million Users", a noteworthy cybersecurity incident.

Restaurant and food delivery service DoorDash confirmed a data breach affecting 4.9 million customers, drivers, and merchants.

The disruption is felt across the environment, and exposing Names, Email Addresses and Phone Numbers, with nearly 4.9 million records at risk.

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Blocked unauthorized access, while recovery efforts such as Notifying affected users via in-app/email continue, and stakeholders are being briefed through Public blog post, Direct notifications to affected users and Media statements.

The case underscores how Ongoing (collaboration with law enforcement), teams are taking away lessons such as Supply chain vulnerabilities remain a critical risk vector, especially for third-party vendors with access to credentials, Social engineering continues to be a dominant attack method, bypassing technical controls and Contact information (phone numbers, addresses) can enable highly targeted phishing campaigns even without financial data exposure, and recommending next steps like Implement phishing-resistant multifactor authentication (MFA) for all employees and third-party vendors, Enforce least-privilege access principles to limit exposure from compromised credentials and Conduct regular security awareness training focused on social engineering tactics, with advisories going out to stakeholders covering Customers, Dashers, and merchants advised to watch for phishing attempts citing order history or delivery addresses and Official notifications will never request passwords or full payment details.

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 Valid Accounts: Cloud Accounts (T1078.004) with high confidence (95%), with evidence including attacker exploited credentials from a **third-party vendor** to gain unauthorized access, and entry point such as Third-party service provider credentials (obtained via social engineering) and Phishing: Spearphishing Link (T1566.002) with high confidence (90%), supported by evidence indicating breach originated from **social engineering**, tricking an employee into divulging access credentials. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (85%), with evidence including credentials obtained through a third-party service provider, and vulnerability exploited such as Human error (social engineering of third-party employee) and Steal Web Session Cookie (T1539) with moderate to high confidence (70%), supported by evidence indicating blocked unauthorized access suggests session/credential misuse over a **two-week reconnaissance period**. Under the Persistence tactic, the analysis identified Account Manipulation: Additional Cloud Credentials (T1098.003) with moderate to high confidence (80%), with evidence including reconnaissance period such as Approximately two weeks before the breach, and high value targets such as Customer PII, Dasher partial payment data. Under the Defense Evasion tactic, the analysis identified Valid Accounts: Cloud Accounts (T1078.004) with high confidence (95%), supported by evidence indicating used credentials obtained through a third-party service provider to gain unauthorized access and Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (75%), supported by evidence indicating lack of detection for unauthorized access over a two-week period. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating exposed data included **names, email addresses, phone numbers, delivery addresses, order history hashes**. 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 (85%), with evidence including data exfiltration such as true, and 4.9 million customers, drivers, and merchants records exposed. Under the Impact tactic, the analysis identified Phishing for Information: Spearphishing via Service (T1598.003) with high confidence (95%), with evidence including heightens risks of **targeted phishing, smishing (SMS scams), and vishing (voice fraud)**, and customers, Dashers, and merchants advised to watch for phishing attempts citing order history. Under the Reconnaissance tactic, the analysis identified Gather Victim Host Information (T1592) with high confidence (90%), with evidence including reconnaissance period such as Approximately two weeks before the breach, and high value targets such as Customer PII, Dasher partial payment data and Gather Victim Network Information: Scan Victim (T1590.005) with moderate to high confidence (80%), supported by evidence indicating monitor for unusual activity in third-party vendor accounts with access to sensitive systems (implied pre-breach scanning). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.