Familylinks Inc reported a data breach to the Montana Attorney General. The breach was reported on 2024-11-12. The breach occurred on 5/3/2024. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Nov 12, 2024. View entity profile → Other incidents for this victim →
incident inc_797910f0bedb412f · merge_method deterministic · confidence 100%
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.
Identity (basic) · Government ID · Financial account
FEDERAL MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 3, 2024
When the intrusion reportedly occurred, per the linked filings
Familylinks Inc reported a data breach to the Montana Attorney General. The breach was reported on 2024-11-12. The breach occurred on 5/3/2024. 1 Montana residents were affected.
Affected (this filing): 1
Familylinks Inc. reported to HHS that on November 12, 2024, an employee was the subject of an email phishing scheme that exposed the protected health information (PHI) of 3,775 individuals. The breach occurred via email and compromised data including names, dates of birth, addresses, some Social Security numbers, claims, financial information, and other clinical details. In response, Familylinks Inc. enhanced its multifactor authentication requirements.
Affected (this filing): 3,775
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.