FMC Services, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-09-23. The breach occurred on 7/26/2022. 78 Montana residents were affected.
Affected (this filing): 78
Clustered 3 filings across 3 jurisdictions · filed Sep 23, 2022. View entity profile → Other incidents for this victim →
incident inc_7f6643fa83144289 · merge_method deterministic · 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.
CA MT TX
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 26, 2022
When the intrusion reportedly occurred, per the linked filings
Jul 26, 2022
Reported by CALIFORNIA AG filing
FMC Services, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-09-23. The breach occurred on 7/26/2022. 78 Montana residents were affected.
Affected (this filing): 78
FMC Services, LLC, a primary care clinic operator in Texas, detected a ransomware attack on July 26, 2022. An unauthorized third party infiltrated the network and demanded ransom. The incident potentially exposed patient and employee data, including names, addresses, dates of birth, Social Security numbers, and health information. FMC engaged forensic investigators, secured its network, and offered one year of identity monitoring via Kroll.
FMC Services, LLC reported to HHS on 2022-09-23 a Hacking/IT Incident affecting 233948 individuals. Breached information located on Network Server.
Affected (this filing): 233,948
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.