Clustered 3 filings across 3 jurisdictions · filing window Jul 24, 2021 → Jul 29, 2021. View entity profile → Other incidents for this victim →
incident inc_bb4d75671f734045 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Health (basic) · Identity (basic) · Government ID
FEDERAL ME MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 2, 2021
When the intrusion reportedly occurred, per the linked filings
Jun 29, 2021
Reported by MAINE AG filing
NCH Corporation reported to HHS on 2021-07-24 a Hacking/IT Incident involving a ransomware attack that affected 11,427 individuals. The breach compromised names, birthdates, Social Security numbers, and health insurance information from a Network Server.
Affected (this filing): 11,427
NCH Corporation reported a data breach to the Montana Attorney General. The breach was reported on 2021-07-29. The breach occurred from 3/2/2021 to 3/5/2021. 36 Montana residents were affected.
Affected (this filing): 36
NCH Corporation reported an external system breach (hacking) occurring between March 2 and March 5, 2021, discovered on June 29, 2021. The incident affected 13,824 individuals, including 6 Maine residents. Acquired data included names and driver's license numbers. NCH provided one year of complimentary credit monitoring and identity theft protection services through Equifax.
Affected (this filing): 13,824
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.