Clustered 4 filings across 4 jurisdictions · filed May 23, 2025. View entity profile → Other incidents for this victim →
incident inc_ae4b9c569ad742f9 · merge_method deterministic · 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.
PII · Identity (basic) · Government ID
IN ME NH NJ
HHS OCR · State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
May 1, 2024
Reported by NEW HAMPSHIRE AG filing
May 14, 2024
When the intrusion reportedly occurred, per the linked filings
Mar 26, 2025
Reported by MAINE AG filing
The Cooper Health System notified the NH Attorney General of a data security incident discovered in May 2024. Unauthorized actors may have acquired personal and protected health information. One NH resident was notified. Cooper engaged cybersecurity experts and is offering credit monitoring.
Affected (this filing): 1
The Cooper Health System reported a data breach to the Indiana Attorney General. The breach occurred on 2024-05-14 and was reported on 2025-05-23. 2 Indiana residents were affected. 57,412 individuals affected in total.
Affected (this filing): 57,412
The Cooper Health System reported to HHS on 2025-05-23 a Hacking/IT Incident affecting 57412 individuals. Breached information located on Network Server.
Affected (this filing): 57,412
The Cooper Health System, a healthcare organization headquartered in Camden, NJ, experienced an external system breach (hacking) in May 2024 involving unauthorized access to its network. The breach was discovered on March 26, 2025, after a thorough investigation with cybersecurity experts. Affected data included names and Social Security numbers of 57,412 individuals total, with 1 Maine resident affected. Notifications were sent May 23, 2025. IDX identity protection services were offered.
Affected (this filing): 1
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.