GLOBALClaimed by BlackbyteFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Jul 6, 2022bd_555f42e9e8001a5d
Clustered 4 filings across 4 jurisdictions · filing window Jul 6, 2022 → Aug 11, 2022. View entity profile → Other incidents for this victim →
incident inc_0fded63ba7c74383 · 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) · Government ID · Health (basic)
ME MT VT
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 12, 2022
When the intrusion reportedly occurred, per the linked filings
Jun 24, 2022
Reported by MAINE AG filing
Lamoille Health Partners reported a data breach to the Montana Attorney General. The breach was reported on 2022-08-11. The breach occurred from 6/12/2022 to 6/13/2022. 19 Montana residents were affected.
Affected (this filing):
Lamoille Health Partners, a healthcare provider, experienced an external system breach between June 12 and June 13, 2022. The breach was discovered on June 24, 2022. The incident affected 59,381 individuals, exposing names and Social Security Numbers. Affected individuals were notified on August 11, 2022, and were offered 12 months of identity protection services through Experian.
Affected (this filing): 59,381
Lamoille Health Partners (Vermont healthcare provider) reported to HHS on 2022-08-11 a ransomware incident affecting 59,381 individuals. PHI on network servers included names, Social Security numbers, addresses, dates of birth, medications, diagnoses, and lab results. The CE notified HHS, affected individuals, and the media, posted substitute notice on its website, and implemented additional administrative, technical, and security safeguards.
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): 59,381