/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

DoorDash says hackers accessed some of its internal tools and customer information after compromising a third-party vendor through the Twilio breach on August 4

Carly Page / TechCrunch :

TechCrunch Carly Page

Context & Ripple Effects

Twilio had already disclosed that an attacker used SMS phishing against staff to access information associated with some accounts. DoorDash now identifies a downstream impact from that event, turning Twilio's staff-targeted intrusion into a vendor-access problem for a major delivery platform.

The disclosure also follows DoorDash's 2019 breach affecting customers, workers, and merchants, making third-party access a notable addition to the company’s history of data-security incidents.

First-order effects

  • DoorDash must treat the compromised vendor connection as an exposure path to its internal tools and customer information, while affected customers face another security disclosure from the platform.
  • Twilio’s August 4 incident now has a named downstream consequence at DoorDash, extending its significance beyond the accounts initially described by Twilio.

Second-order effects

  • DoorDash’s disclosure puts pressure on Twilio and DoorDash to scrutinize how vendor access connects customer-facing systems to internal tools, rather than treating the phishing incident as confined to Twilio staff accounts.
  • The recurrence of a DoorDash data incident shifts the immediate trust burden toward the company’s handling of customer and operational data, including data reachable through suppliers.

Third-order effects

  • Together with the later Workday third-party CRM incident in related coverage, the case supports a broader pattern: enterprise breaches increasingly spread through service-provider access rather than a single company’s perimeter.
  • If that pattern persists, security accountability will move further toward governing vendor permissions and identity-based access across interconnected platforms.

The trend: Identity phishing and third-party software access are becoming a shared breach surface that links supplier incidents to downstream customer-data exposure.

Discussion

  • @adam_k_levin Adam Levin on x
    Data breaches seem to be picking up steam of late: https://techcrunch.com/...
  • @jbursz Jessica Bursztynsky on x
    DoorDash says it was hit by a data breach that exposed customers' information like name, address & partial payment card info. “The advanced tactics used appear to be connected to a wider phishing campaign that has targeted a number of other companies.” https://doordash.news/...
  • @campuscodi Catalin Cimpanu on x
    Twilio... the hack that keeps on giving https://twitter.com/...