Noble House Hotels & Resorts — December 2014 breach

Clustered 6 filings across 4 jurisdictions · filing window Oct 22, 2015 → Nov 13, 2015. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

Affected · reported

not comparable

First → last filing

Oct 22, 2015 → Nov 13, 2015

Merge confidence

100%

incident inc_e922594fd4f9439c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe a ransomware attack. Intrusion Dec 29, 2014–Aug 11, 2015, discovered Sep 25, 2015 — the first regulatory filing landed 27 days later. Data reported: Financial account, Financial credentials, PII, and 2 more. Notifications rolled out on a 22-day schedule across 6 filings beginning Oct 22, 2015. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

27days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

22days

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 clocksCalifornia✓ CA 60-day OK · 20dFull 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.