GLOBALClaimed by VicesocietyFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Apr 17, 2022bd_de29c5de1c1817a5
Clustered 4 filings across 4 jurisdictions · filing window Apr 17, 2022 → Dec 19, 2022. View entity profile → Other incidents for this victim →
incident inc_5ddd9f51fe1f4b5f · 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.
Identity (basic) · Financial account · Financial credentials
ME MT NH
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 9, 2022
When the intrusion reportedly occurred, per the linked filings
Apr 13, 2022
Reported by MAINE AG filing
NuLife Med, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-05-09. The breach occurred from 3/9/2022 to 3/11/2022. 22 Montana residents were affected.
Affected (this filing): 22
NuLife Med, LLC reported to HHS on 2022-07-25 a Hacking/IT Incident affecting 3805 individuals. Breached information located on Network Server. Business Associate present.
Healthcare provider NuLife Med, LLC reported a hacking incident affecting 29,453 individuals. The breach, occurring on March 9, 2022, and discovered on April 13, 2022, exposed names and financial account data. NuLife Med offered affected individuals 12 months of credit monitoring and identity restoration services.
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.
Affected (this filing): 3,805