Clustered 4 filings across 4 jurisdictions · filing window Mar 29, 2024 → Jun 28, 2024. View entity profile → Other incidents for this victim →
incident inc_ae28a10edde44e4f · 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.
IN ME MT 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
Feb 4, 2024
When the intrusion reportedly occurred, per the linked filings
Feb 5, 2024
Reported by HHS OCR, MAINE AG filings
The Prudential Insurance Company of America reported a data breach to the Indiana Attorney General. The breach occurred on 2024-02-04 and was reported on 2024-03-29. 61,560 Indiana residents were affected. 36,545 individuals affected in total.
Affected (this filing): 61,560
The Prudential Insurance Company of America reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-29. The breach occurred from 2/4/2024 to 2/5/2024. 7,824 Montana residents were affected.
Affected (this filing): 7,824
The Prudential Insurance Company of America (Health Plan, NJ) reported a cybersecurity incident to HHS on 2024-04-22, affecting 36,075 individuals. PHI exposed on a network server included names, addresses, dates of birth, driver's license and Social Security numbers, diagnoses, and other treatment information. The CE notified HHS, media, and affected individuals, and implemented additional technical and security safeguards.
Affected (this filing): 36,075
The Prudential Insurance Company of America experienced an external system breach on February 4, 2024, which was discovered the following day. The incident affected 21,877 residents of Maine. In response, the company provided 24 months of identity theft and credit monitoring services through Kroll.
Affected (this filing): 21,877
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.