GLOBALClaimed by Cl0pFirst sighting
Posted to leak site Mar 10, 2023bd_b26b2e75a816546f
Home - MedMinder
Clustered 4 filings across 4 jurisdictions · filing window Mar 10, 2023 → Sep 7, 2023. View entity profile → Other incidents for this victim →
incident inc_cda4ec0fa1af4482 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
MA MT WA
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 7, 2023
When the intrusion reportedly occurred, per the linked filings
Feb 21, 2023
Reported by WASHINGTON AG filing
Home - MedMinder
MedMinder Systems, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-09-01. The breach occurred from 2/7/2023 to 2/21/2023. 2 Montana residents were affected.
Affected (this filing):
MedMinder Systems, Inc. reported to HHS on 2023-09-01 a Hacking/IT Incident affecting 12,146 individuals. Breached information located on Network Server. The cyber-attack compromised PHI including dates of birth and medications. The entity offered free credit monitoring and implemented additional safeguards.
MedMinder Systems, Inc., a health sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2023-02-21 and filed notice on 2023-09-07. 1,252 Washington residents were affected. 198 days elapsed between awareness and notification. 14 days to identify the breach. 0 days to contain the breach.
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.
Affected (this filing): 12,146
Affected (this filing): 1,252