ILKB, LLC — October 2016 breach
Clustered 6 filings across 5 jurisdictions · filing window Mar 6, 2017 → Apr 24, 2017. View entity profile → Other incidents for this victim →
incident inc_8e5d82c5f2ac4289 · merged by human · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
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.
Sensitive data
authenticationfinancial_credentialsidentity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- MAR 6NH AGNH AG noticefirst filing · 4 NH residentsauto-linkedday 0
- MAR 8MA AGMA AG notice1,558 MA residentsauto-linked+2d
- APR 11NH AGNH AG notice74 NH residentsauto-linked+36d
- APR 12WA AGWA AG notice1,140 WA residents+37d
- APR 19MT AGMT AG notice159 MT residentsoperator-confirmed+44d
- APR 24CA AGCA AG noticemost recent · no count statedauto-linked+49d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Oct 1, 2016 – Oct 7, 2016 NH AG
- Discovered
- Dec 23, 2016NH AG + MT AGMar 24, 2017NH AG + WA AGfilings disagree on discovery
- Data types
- Authentication · Credentials · Financial account · Financial credentials · Identity (basic) · Government ID · PCI · PII NH AG + WA AG + MT AG +2
- Attack vector
- Unauthorized Access NH AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Affected residents by state
per-state reported counts
State AGs report only their own residents; teal bars show each state's reported slice.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- human
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
49 days
Cadence
~1 / 9.8d
vs. multi-state median
6.1× slower
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
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.