Clustered 2 filings across 2 jurisdictions · filed Jan 7, 2022. View entity profile → Other incidents for this victim →
incident inc_649f1076779c45fb · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID
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.
ME NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 4, 2021
When the intrusion reportedly occurred, per the linked filings
Oct 5, 2021
Reported by NEW HAMPSHIRE AG filing
Oct 16, 2021
Reported by MAINE AG filing
National Association of Community Health Centers (NACHC) reported an external system breach that occurred on October 4, 2021, and was discovered on October 16, 2021. The breach affected 2 Maine residents, compromising their names and Social Security numbers. NACHC offered affected individuals 24 months of credit and identity monitoring services.
Affected (this filing): 2
National Association of Community Health Centers (NACHC) notified the New Hampshire Attorney General on January 7, 2022, of a cyberattack affecting two NH residents. Threat actors gained access around October 4, 2021, and encrypted servers (ransomware). Employee PII (SSNs, names, DOB, salary) was stored on compromised servers. NACHC engaged forensic investigators, notified law enforcement (FBI/DHS), and is offering 24 months of credit monitoring. No evidence of data exfiltration was found.
Affected (this filing): 2
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.