HackingHospitalityHospitalityStolen CredentialsData ExfiltratedCustomer Data InvolvedFinancial accountIdentity (basic)PCILowContained

Cheddar's Scratch Kitchen

bd_bf44ec2af9891675 · schema v1 · pii pii-v1

Severity

Low

Discovered

Aug 16, 2018

Filed

Aug 22, 2018

To disclose

6 days

Affected

Not disclosed

Linked

6 filings

Confidence

69%

Full breach record for Cheddar's Scratch Kitchen →2 incidents on file

Cheddar's Scratch Kitchen disclosed a cyberattack occurring between November 3, 2017, and January 2, 2018, discovered on August 16, 2018. Unauthorized access to a now-disabled network resulted in the potential exposure of payment card information for customers in 22 states. The company engaged forensic investigators and offered credit monitoring services.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 286 days

discovery → filing · 6 days

Nov 3, 2017

Begins

Aug 16, 2018

Discovered

Aug 22, 2018

Filed

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

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Oregon State AGbd_4f996fc23fae99ef2018-08-23 · +1dVerified by operator
California State AGbd_f2728b56e66f0bad2018-08-23 · +1dVerified
New Hampshire State AGbd_0c8c7dd41ed820792018-08-24 · +2dVerified
South Carolina State AGbd_fd0b017b0faa47282018-08-28 · +6dVerified

Show 1 more filing ↓up to 6d gap

Montana State AGbd_4124c4909d33b7c12018-08-16 · +6dCandidate

Name: Cheddar's Scratch Kitchen
norm: cheddar s scratch kitchen

Name: Cheddar's Scratch Kitchen
norm: cheddar s scratch kitchen
Industry: Hospitalityllm

Discovered: Aug 16, 2018
Breach occurred: Nov 3, 2017 – Jan 2, 2018
Undetected for: 286 daysoccurrence → discovery
Materiality determined: —
Notification sent: Nov 22, 2018
Affected individuals: Not disclosed
Data types: Financial accountIdentity (basic)PCI
Data elements: NameFinancial account number
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 200-299dexposure 1-99d
WA-stated discovery: Found after the fact
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: ExternalFinancial
Initial access: valid_credentials

During the incident: Engaged a third-party cybersecurity firm to investigate
Arranged to have ID Experts provide identity protection services at no cost
Changes made: Permanently disabled and replaced the affected network by April 10, 2018
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 6 states

View merged incident ↗

Montana State AGAug 16 · first

Washington State AG+6d · this page

Oregon State AG+7d

California State AG+7d

New Hampshire State AG+8d

South Carolina State AG+12d

Pattern: first filing Aug 16 (MT), last Aug 28 (SC) — a 12-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://agportal-s3bucket.s3.amazonaws.com/databreach/BreachM10577.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 22, 2018
Raw hash: 69b62185eb2e5775824ecd807d93396b6a7c829d1332da3f485f46eadbf2d8b6

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityCheddar's Scratch Kitchen

Victim entityCheddar's Scratch Kitchen

Incidentdiscovered Aug 16, 2018

Stated responseEngaged a third-party cybersecurity firm to investigate

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com