HackingTechnologyRetail & ConsumerInformationCustomer Data InvolvedEmployee Data InvolvedIdentity (basic)Financial accountFinancial credentialsLowContained

EatStreet

bd_6c8bdb60faeed336 · schema v1 · pii pii-v1

Severity

Low

Discovered

May 17, 2019

Filed

Jun 14, 2019

To disclose

28 days

Affected

Not disclosed

Linked

4 filings

Confidence

65%

Full breach record for EatStreet →

On May 3, 2019, an unauthorized third party gained access to EatStreet's database, which was discovered on May 17, 2019. The incident affected delivery partners, restaurant partners, and diners. Compromised data included names, phone numbers, email addresses, bank account and routing numbers for partners, and payment card information (including CVV) for diners. EatStreet engaged forensic investigators, terminated unauthorized access, and enhanced security controls including MFA and credential rotation.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 14 days

discovery → filing · 28 days

May 3, 2019

Begins

May 17, 2019

Discovered

Jun 14, 2019

Filed

vs. sector median

15 wks faster

This filing is one of 4 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Massachusetts State AGbd_1cc588007e9343b02019-06-14Verified
Montana State AGbd_479241cd8f1e9b6e2019-07-14 · +30dVerified
South Carolina State AGbd_a08f50a84a4629542019-08-06 · +53dVerified

Name: EatStreet
norm: eatstreet
Domain: go.geteatstreet.com

Name: EatStreet
norm: eatstreet
Domain: go.geteatstreet.com
Industry: TechnologyllmRetail & Consumerllm

Discovered: May 17, 2019
Breach occurred: May 3, 2019
Undetected for: 14 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)Financial accountFinancial credentials
Attack vector: Unauthorized Access
Threat actor: External

During the incident: Hired a leading external IT forensics firm to respond to and investigate the incident
Audited our systems to validate that there was no other unauthorized access
Enhanced the security of our systems, including reinforcing multi-factor authentication, rotating credential keys and reviewing and updating coding practices
Continues to work with outside experts to identify other measures it can take to improve its security controls
Notified our credit card payment processor of the incident
Changes made: Reinforcing multi-factor authentication
Rotating credential keys
Reviewing and updating coding practices
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 28 days(28 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Massachusetts State AGJun 14 · first

California State AGJun 14 · first · this page

Montana State AG+30d

South Carolina State AG+53d

Pattern: first filing Jun 14 (MA), last Aug 6 (SC) — a 53-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.ca.gov/ecrime/databreach/reports/sb24-148118
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 14, 2019
Raw hash: 3d7d600ec82fd0105dc155033dc0f67031faeab6687d035536f2651ffe609a67

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityEatStreet

Victim entityEatStreet

Incidentdiscovered May 17, 2019

Stated responseHired a leading external IT forensics firm to respond to and investigate the incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov