DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed7 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhunters_internationalhigh sensitivity
Merged incident · 7 filings

Omni Family Health — August 2024 breach

Clustered 7 filings across 6 jurisdictions · filing window Aug 6, 2024 → Oct 11, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

468,344

First → last filing

Aug 6, 2024 → Oct 11, 2024

Merge confidence

100%

incident inc_2a47ff54762e45c8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 7, 2024, discovered Aug 7, 2024 — the first regulatory filing landed 58 days later. 468,344 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 4 more. Notifications rolled out on a 65-day schedule across 6 filings beginning Aug 6, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
58days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
58days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
65days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap⏱ Leak >30dVermont⏱ VT AG >14 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 7, 2024breach begins
Aug 7, 2024discovered
notification delay · 58 days
Oct 4, 2024first filing
Oct 11, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. AUG 6Leak sitehunters_international postfirst filing · attacker claim · unverifiedday 0
  2. OCT 4HHS OCRHHS OCR noticestates nationwide total 468,344+58d
  3. OCT 10MT AGMT AG notice90 MT residents+64d
  4. OCT 10VT AGVT AG noticeno count stated+64d
  5. OCT 10CA AGCA AG noticeno count stated+64d
  6. OCT 10MA AGMA AG notice15 MA residents+64d
  7. OCT 11NH AGNH AG noticemost recent · 8 NH residents+65d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 7, 2024
CA AG
Discovered
Aug 7, 2024
MT AG + VT AG + CA AG +1
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MT AG + VT AG +3
Attack vector
Unauthorized Access
HHS OCR

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

468,344

Sum of filed state slices

113· 0.0% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US468,344
MT90
MA15
NH8

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing6 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

65 days

Cadence

~1 / 10.8d

vs. multi-state median

8.1× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.