Itasca County Health & Human Services reported a data breach to the Montana Attorney General. The breach was reported on 2023-06-27. The breach occurred from 4/7/2023 to 4/11/2023. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filed Jun 27, 2023. View entity profile → Other incidents for this victim →
incident inc_df96b9fed4b245c7 · 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.
MN MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 7, 2023
When the intrusion reportedly occurred, per the linked filings
Itasca County Health & Human Services reported a data breach to the Montana Attorney General. The breach was reported on 2023-06-27. The breach occurred from 4/7/2023 to 4/11/2023. 2 Montana residents were affected.
Affected (this filing): 2
Itasca County Health & Human Services (MN) reported to HHS on 2023-06-27 a Hacking/IT Incident (email phishing) affecting 1,413 individuals. An employee's email account was compromised via phishing, exposing PHI including names, SSNs, driver's license numbers, diagnoses, lab results, medications, addresses, birthdates, and claims/treatment information. The CE notified individuals, media, and posted substitute notice. Remediation included credit monitoring, additional safeguards, and staff retraining. Breached information located in Email.
Affected (this filing):
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.