Omni Hotels & Resorts — December 2015 breach

Clustered 7 filings across 7 jurisdictions · filing window Jul 7, 2016 → Jul 21, 2016. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

Affected · reported

2,056

First → last filing

Jul 7, 2016 → Jul 21, 2016

Merge confidence

100%

incident inc_1c76c808361a4716 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe a ransomware attack. Intrusion Dec 23, 2015–Jun 14, 2016, discovered May 30, 2016 — the first regulatory filing landed 38 days later (flagged late). 2,056 individuals reported across the linked filings. Data reported: Financial account, Financial credentials, PCI, and 1 more. Notifications rolled out on a 14-day schedule across 7 filings beginning Jul 7, 2016. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

38days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

14days

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 >45dCalifornia✓ CA 60-day OK · 39dFull 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.