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

New Horizons Medical — February 2023 breach

Clustered 9 filings across 5 jurisdictions · filing window Jun 7, 2023 → Jun 16, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

4

Affected · reported

12,317

First → last filing

Jun 7, 2023 → Jun 16, 2023

Merge confidence

100%

incident inc_75169b60ea1f4c58 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 4 unverified claims. The filings describe unauthorized access. Intrusion Feb 12, 2023–Apr 23, 2023, discovered Apr 19, 2023 — the first regulatory filing landed 58 days later. 12,317 individuals reported across the linked filings. Data reported: Government ID, Financial account, PII, and 3 more. Notifications rolled out on a 9-day schedule across 5 filings beginning Jun 7, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
58days

Discovered → first regulatory filing

Discovery variance
30days

Range of discovered_at dates across filings

Leak precedence
9days 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
9days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont⏱ VT AG >14 bdayMaine✓ ME AG ≤30d · 28dMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 12, 2023breach begins
Apr 19, 2023discovered · members disagree
notification delay · 58 days
Jun 16, 2023first filing
—watching for filings

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

Member cascade — every filing about this breach

  1. JUN 7Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. JUN 7Leak sitedispossessor postattacker claim · unverifiedday 0
  3. JUN 7Leak sitedevman postattacker claim · unverifiedday 0
  4. JUN 14Leak sitealphv postattacker claim · unverified+7d
  5. JUN 16ME AGME AG noticestates nationwide total 12,317+9d
  6. JUN 16NH AGNH AG notice60 NH residents+9d
  7. JUN 16MA AGMA AG notice12,157 MA residents+9d
  8. JUN 16VT AGVT AG noticeno count stated+9d
  9. JUN 16HHS OCRHHS OCR noticemost recent · states nationwide total 12,317+9d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 12, 2023 – Apr 23, 2023
ME AG
Discovered
Apr 19, 2023NH AG + VT AGMay 19, 2023ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
ME AG + MA AG + VT AG +2
Attack vector
Unauthorized Access
ME AG

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)

12,317

Sum of filed state slices

12,226· 99.3% of stated

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

US12,317
MA12,157
NH60
ME9

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 claim4 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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
human
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

9 days

Cadence

~1 / 1.1d

vs. multi-state median

1.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.