State AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings
LÍLLÉbaby — June 2016 breach
Clustered 5 filings across 5 jurisdictions · filed Aug 29, 2018. View entity profile → Other incidents for this victim →
⚠ 2 cross-filing discrepancies →Merge100%
incident inc_f4e1c5372507460b · merged by deterministic · confidence 100%
Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe malware. Intrusion Jun 1, 2016–Jul 9, 2018, discovered Jun 1, 2018 — the first regulatory filing landed 89 days later (flagged late). 37,000 individuals reported across the linked filings. Data reported: PCI, Financial account, Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.
Litigation Timing
SupplementalNotification delay
89days
Discovered → first regulatory filing
Discovery variance
14days
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 clocksOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 88dFull 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.