State AGConfirmed3 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 3 filings
9W Halo OpCo L.P. — April 2018 breach
Clustered 3 filings across 3 jurisdictions · filed Jun 7, 2018. View entity profile → Other incidents for this victim →
⚠ 2 cross-filing discrepancies →Merge100%
incident inc_21e0303ccbde43ee · merged by deterministic · confidence 100%
Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe an accidental exposure. Intrusion Apr 3, 2018–Apr 11, 2018, discovered Apr 15, 2018 — the first regulatory filing landed 53 days later. 5 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial, and 2 more. Each member filing remains the legal record for its jurisdiction.
Litigation Timing
Notification delay
53days
Discovered → first regulatory filing
Discovery variance
10days
Range of discovered_at dates across filings
Filing span
0days
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 · 53dFull clock table in Litigation Timeline
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.