Physicians Insurance A Mutual Company reported a data breach to the Montana Attorney General. The breach was reported on 2023-07-19. The breach occurred on 3/2/2023. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filed Jul 19, 2023. View entity profile → Other incidents for this victim →
incident inc_ab85cf984d6c4079 · 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 · Health (basic)
MT WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 2, 2023
When the intrusion reportedly occurred, per the linked filings
Physicians Insurance A Mutual Company reported a data breach to the Montana Attorney General. The breach was reported on 2023-07-19. The breach occurred on 3/2/2023. 2 Montana residents were affected.
Affected (this filing): 2
Physicians Insurance A Mutual Company, a business associate based in WA, reported to HHS on 2023-07-19 a Hacking/IT Incident (email phishing) affecting 1,852 individuals. An employee was the victim of a phishing scheme that compromised PHI including names, Social Security numbers, dates of birth, health insurance information, and other treatment information. Breached information was located in Email. The BA notified HHS, affected individuals, and media, offered credit monitoring, and implemented new administrative and technical safeguards.
Affected (this filing): 1,852
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.