Confirmed breach. Intrusion Jan 21, 2025, discovered Jan 28, 2025 — the first regulatory filing landed 127 days later. 2 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
2
Data types
3
Identity (basic) · Government ID · Financial account
Jurisdictions
1
NH
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 21, 2025
When the intrusion reportedly occurred, per the linked filings
Hanafin Financial notified the NH AG of a data security incident affecting 2 NH residents. Unauthorized access to an employee email account occurred on Jan 21, 2025, detected on Jan 28, 2025. Data exposed included names, SSNs, driver's license numbers, and financial account numbers. Notifications mailed June 3, 2025, with credit monitoring offered.
Affected (this filing): 2
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.