GLOBALClaimed by Hunters InternationalFirst sightinglinked via shared-victim match · 100%
Posted to leak site Aug 6, 2024bd_d8334e0eb4c8b728
Country : United States of America - Exfiltraded data : yes - Encrypted data : no
Clustered 3 filings across 3 jurisdictions · filing window Aug 6, 2024 → Oct 10, 2024. View entity profile → Other incidents for this victim →
incident inc_2a47ff54762e45c8 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
CA VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Country : United States of America - Exfiltraded data : yes - Encrypted data : no
Aug 7, 2024
When the intrusion reportedly occurred, per the linked filings
Aug 7, 2024
Reported by CALIFORNIA AG, VERMONT AG filings
Omni Family Health notified patients of a data breach discovered on August 7, 2024, involving personal and health information posted on the dark web. Affected data includes names, addresses, SSNs, dates of birth, insurance info, and medical records. The organization engaged cybersecurity specialists and notified law enforcement. Credit monitoring services were offered to affected individuals.
Omni Family Health notified patients and employees of a data breach discovered on August 7, 2024. Information including names, SSNs, DOBs, insurance info, and medical records was posted on the dark web. The organization engaged cybersecurity specialists, notified law enforcement, and offered 12 months of credit monitoring via Experian.
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.