Clustered 3 filings across 3 jurisdictions · filing window Feb 9, 2023 → Apr 3, 2023. View entity profile → Other incidents for this victim →
incident inc_99b81e4b451c44a1 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Identity (basic) · Government ID · Financial account
NH VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 27, 2023
Reported by VERMONT AG, NEW HAMPSHIRE AG filings
The service provider of choice for individuals with IDD, their families and community, we welcome the opportunity to show you that when it comes to your provider you should expect more. Everyone deserves the best, and we deliver on that expectation e...
The Arc of Essex County notified consumers of a cybersecurity incident detected on January 27, 2023, involving malware on its network. An unauthorized actor accessed files containing employee information, including names, SSNs, driver's licenses, and financial account data. The organization secured its environment, investigated the scope, and offered one year of complimentary credit monitoring to affected employees.
The Arc of Essex County detected malware on its network on January 27, 2023. An unauthorized actor accessed files containing employment information and potentially other personal data. The incident affects one New Hampshire resident. The organization is offering one year of credit monitoring and is reviewing security policies. The investigation was ongoing at the time of filing.
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.
Affected (this filing): 1