AccidentalRetail & ConsumerRetailMisconfigurationCustomer Data InvolvedPIIPCIIdentity (basic)Financial accountLowContained

TigerChef

bd_943bfa857051f3af · schema v1 · pii pii-v1

Severity

Low

Discovered

Sep 9, 2019

Filed

Apr 10, 2020

To disclose

31 weeks

Affected

1state residents only

Linked

3 filings

Confidence

65%

Full breach record for TigerChef →

TigerChef (dba Suburban Bowery of Suffern Inc) notified Montana residents of a payment card compromise on its website. Suspicious code was present on the checkout page from July 17 to September 10, 2019, potentially capturing card info. The company removed the code and implemented the iField framework.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 54 days

discovery → filing · 31 weeks / 214 days

Jul 17, 2019

Begins

Sep 9, 2019

Discovered

Apr 10, 2020

Filed

vs. sector median

+23 wks slower

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

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Massachusetts State AGbd_3c4f09f4fee5a93c2020-04-10Verified
Indiana State AGbd_af4f5056683cdde12020-04-10Verified

Name: TigerChef
norm: tigerchef

Name: TigerChef
norm: tigerchef
Also named: Suburban Bowery of Suffern Incdba oflegal entity
TigerChefdba oftrade name
Industry: Retail & Consumerllm

Discovered: Sep 9, 2019
Breach occurred: Jul 17, 2019 – Sep 10, 2019
Undetected for: 54 daysoccurrence → discovery
Materiality determined: —
Notification sent: Apr 10, 2020
Affected individuals: 1state-resident count only
Data types: PIIPCIIdentity (basic)Financial account
Attack vector: Misconfiguration
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Threat actor: ExternalFinancial
Initial access: exploit_public_facing

During the incident: TigerChef began monitoring the backend setting that had previously been changed
TigerChef implemented the iField framework, which adds extra layers of protection
Changes made: TigerChef implemented the iField framework, which adds extra layers of protection
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Massachusetts State AGApr 10 · first

Indiana State AGApr 10 · first

Montana State AGApr 10 · first · this page

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/doc-20-1.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 10, 2020
Raw hash: e21fbeb636de5f3c013b7a56bf527d581e9834a36614a9124c115ad0320829d4

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityTigerChef

Victim entityTigerChef

Incidentdiscovered Sep 9, 2019

Stated responseTigerChef began monitoring the backend setting that had previously been changed

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov