Clustered 3 filings across 2 jurisdictions · filing window Aug 16, 2021 → Sep 28, 2021. View entity profile → Other incidents for this victim →
incident inc_457879503f0045c4 · merge_method human · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
ME MT
all 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
Apr 23, 2021
When the intrusion reportedly occurred, per the linked filings
May 12, 2021
Reported by MAINE AG filing
New York Life Insurance reported a data breach to the Montana Attorney General. The breach was reported on 2021-08-16. The breach occurred on 4/23/2021. 3 Montana residents were affected.
Affected (this filing): 3
New York Life Insurance reported a data breach to the Montana Attorney General. The breach was reported on 2021-09-28. The breach occurred from 4/13/2021 to 5/12/2021. 5 Montana residents were affected.
Affected (this filing): 5
New York Life Insurance Company reported a phishing incident that occurred between April 13, 2021, and May 12, 2021. The breach was discovered on May 12, 2021. The incident affected 3 Maine residents, exposing their names and Social Security numbers. The company provided written notification to affected individuals on September 28, 2021, and offered one year of credit monitoring services from Equifax.
Affected (this filing): 3
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.