MJ Care reported a data breach to the Montana Attorney General. The breach was reported on 2022-12-29. The breach occurred from 5/31/2021 to 6/24/2022. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Dec 29, 2022. View entity profile → Other incidents for this victim →
incident inc_7136941ef97f4f9e · 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
MT WI
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 31, 2021
When the intrusion reportedly occurred, per the linked filings
MJ Care reported a data breach to the Montana Attorney General. The breach was reported on 2022-12-29. The breach occurred from 5/31/2021 to 6/24/2022. 1 Montana residents were affected.
Affected (this filing): 1
MJ Care (a covered entity and business associate) reported to HHS on 2022-12-29 a Hacking/IT Incident affecting 1,832 individuals. An employee was subjected to an email phishing scheme that compromised PHI including names, Social Security numbers, dates of birth, financial information, diagnoses, medications, and other treatment information. Breached information was located in Email. MJ Care notified HHS, affected individuals, and the media, and implemented additional administrative and technical safeguards.
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.