Landry's, Inc. — January 2019 breach

Clustered 6 filings across 6 jurisdictions · filing window Dec 31, 2019 → Jan 6, 2020. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

Affected · reported

1,000,001

First → last filing

Dec 31, 2019 → Jan 6, 2020

Merge confidence

100%

incident inc_0653ab7dbd4241c0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filing describes a ransomware attack. Intrusion Jan 18, 2019–Oct 17, 2019, discovered Nov 22, 2019 — the first regulatory filing landed 39 days later. 1,000,001 individuals reported across the linked filings. Data reported: Government ID, PCI, Financial account, and 2 more. Notifications rolled out on a 6-day schedule across 6 filings beginning Dec 31, 2019. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

39days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

6days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.