Clustered 4 filings across 3 jurisdictions · filing window Jul 21, 2023 → Aug 31, 2023. View entity profile → Other incidents for this victim →
incident inc_a83ee3837eba4205 · merge_method human · confidence 100%
Discovered → 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.
ME MT NH
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 23, 2023
When the intrusion reportedly occurred, per the linked filings
May 24, 2023
Reported by NEW HAMPSHIRE AG filing
New England Life Care, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-07-21. The breach occurred from 5/23/2023 to 5/24/2023. 3 Montana residents were affected.
Affected (this filing): 3
New England Life Care, Inc. reported to HHS on 2023-07-21 a Hacking/IT Incident affecting 51,854 individuals. Breached information located on Network Server. The incident involved PHI including names, addresses, and treatment information. The entity provided credit monitoring, implemented security safeguards, and retrained staff.
Affected (this filing): 51,854
Jul 25, 2023
Reported by MAINE AG filing
New England Life Care, Inc. experienced an external system breach (hacking) between May 23, 2023, and May 24, 2023, which was discovered on July 25, 2023. The breach affected 3 Maine residents, compromising their names and Social Security numbers. The company provided one year of credit monitoring and identity theft protection services through Experian to those affected.
Affected (this filing): 3
New England Life Care, Inc. reported an unauthorized access to its IT network between May 23-24, 2023. The attacker accessed vendor files potentially containing names and Social Security numbers. The company engaged forensic investigators, contained the breach, and offered one year of Experian IdentityWorks to affected individuals.
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.