Clustered 3 filings across 3 jurisdictions · filing window Dec 27, 2018 → Dec 28, 2018. View entity profile → Other incidents for this victim →
incident inc_db1837e267fc47b9 · 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.
CA MI MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 23, 2018
When the intrusion reportedly occurred, per the linked filings
Wolverine Solutions Group reported a data breach to the Montana Attorney General. The breach was reported on 2018-12-27. The breach occurred from 9/23/2018 to 10/25/2018. 79 Montana residents were affected.
Affected (this filing): 79
On approximately September 23, 2018, Wolverine Solutions Group, a services provider for health-related business clients, experienced a ransomware attack that locked up its servers and workstations. The company performed services for Blue Cross Blue Shield of Michigan, and affected data included demographic information, health plan contract numbers, medical information, and Social Security numbers. A forensics investigation found no evidence of data extraction. Notification letters were sent December 28, 2018, with 24 months of AllClear ID identity protection offered.
Wolverine Solutions Group reported to HHS on 2018-12-28 a Hacking/IT Incident affecting 1,024,731 individuals. Breached information located on Network Server. The business associate was the victim of a ransomware attack affecting PHI including names, addresses, DOB, driver's license, SSN, health insurance, claims, diagnoses, lab results, and medications. The BA offered complimentary credit monitoring and implemented additional safeguards.
Affected (this filing): 1,024,731
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.