City of Post Falls Police Department reported a data breach to the Montana Attorney General. The breach was reported on 2022-05-09. The breach occurred on 2/19/2022. 6 Montana residents were affected.
Affected (this filing): 6
Clustered 2 filings across 2 jurisdictions · filing window May 9, 2022 → May 10, 2022. View entity profile → Other incidents for this victim →
incident inc_1816e4b5dc344315 · 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.
ID MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 19, 2022
When the intrusion reportedly occurred, per the linked filings
Feb 19, 2022
Reported by IDAHO AG filing
City of Post Falls Police Department reported a data breach to the Montana Attorney General. The breach was reported on 2022-05-09. The breach occurred on 2/19/2022. 6 Montana residents were affected.
Affected (this filing): 6
Post Falls Police Department (Idaho) disclosed a ransomware attack detected on February 19, 2022. Cybercriminals exfiltrated data before deploying ransomware, affecting approximately 973 Idaho residents. Compromised data included names, DOB, addresses, SSNs, driver's license numbers, and bank account/routing numbers. PFPD notified the FBI, engaged forensic experts, and provided 973 residents with credit monitoring via Experian. Remediation included enhanced network monitoring, password policies, and intrusion detection.
Affected (this filing): 973
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.