HackingRetail & ConsumerRetailStolen CredentialsCapture Stored DataTargetedCustomer Data InvolvedPIIIdentity (basic)Financial accountAuthenticationLowContained

EatStreet

bd_57e2e2bc6fca25aa · schema v1 · pii pii-v1

Severity

Low

Discovered

May 17, 2019

Filed

Jun 14, 2019

To disclose

28 days

Affected

25state residents only

Linked

5 filings

Confidence

66%

Full breach record for EatStreet →

EatStreet notified Montana residents of a May 3, 2019 database breach discovered on May 17, 2019. Unauthorized access compromised customer names, payment card details, CVVs, billing addresses, emails, and phone numbers. The company engaged forensic investigators, audited systems, and enhanced security controls including MFA.

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

6 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Massachusetts State AGbd_1cc588007e9343b02019-06-14Verified
California State AGbd_6c8bdb60faeed3362019-06-14Candidate
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: Retail & Consumerllm

Discovered: May 17, 2019
Breach occurred: May 3, 2019
Undetected for: 14 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 25state-resident count only
Data types: PIIIdentity (basic)Financial accountAuthentication
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: ExternalFinancial
Initial access: valid_credentials

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
Reinforcing multi-factor authentication
Rotating credential keys
Reviewing and updating coding practices
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 · 5 filings · 4 states

View merged incident ↗

Massachusetts State AGJun 14 · first

California State AGJun 14 · first

Montana 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://dojmt.gov/wp-content/uploads/OCP/Data-Breach-Notification-5.pdf
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: a20a1501ae2be0c79ac0de68ad4be1bf160a11dad37476b869a32ddb63fd7473

Linked disclosures

Regulatory filings (4) · 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 provenancedojmt.gov