Confirmed breach. Intrusion Aug 14, 2024, discovered Aug 14, 2024 — the first regulatory filing landed 79 days later (flagged late). 5,198 individuals reported across the linked filings.
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.
Regulatory clocksVermont✗ VT AG >45 bdayHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
5,198
Data types
3
Identity (basic) · Government ID · Financial account
Jurisdictions
2
FL VT
Linked filings
2
HHS OCR · State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 14, 2024
When the intrusion reportedly occurred, per the linked filings
HealthFund Solutions notified Vermont AG on 2024-11-01 of a breach occurring 2024-08-14 where an unauthorized individual accessed an employee email account. Affected data included names, SSNs, and financial account numbers. No evidence of fraud found. Forensic investigation conducted.
VT AG >45 bday
🇺🇸FLHHS OCRMost recentlinked via same-victim cross-source · 100%
HealthFund Solutions, LLC reported to HHS on 2024-11-15 a Hacking/IT Incident affecting 5,198 individuals. Breached information located on Email. The business associate offered free credit monitoring and implemented administrative, technical and security safeguards.
Affected (this filing): 5,198
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.