DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SitePressHHS OCRState AGConfirmed14 records · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmonticritical sensitivity
Merged incident · 14 records

Excelsior Orthopaedics, LLC — June 2024 breach

Clustered 14 records across 9 jurisdictions: 12 filings, 1 press report and 1 leak-site claim · filing window Aug 21, 2024 → Sep 2, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

14 records

States

9

Affected · reported

394,752

First → last dated filing

Aug 21, 2024 → Sep 2, 2025

Merge confidence

100%

incident inc_3f48a91aecab4688 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings, 1 press report and 1 unverified claim. The filings describe unauthorized access. Intrusion Jun 18, 2024–Jun 27, 2024, discovered Jun 23, 2024 — the first regulatory filing landed 59 days later; 1 later filing was flagged late. 394,752 individuals reported across the linked filings. Data reported: Government ID, Biometric, PII, and 6 more. Notifications rolled out on a 377-day schedule across 9 dated filings beginning Aug 21, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
59days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
43days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
377days

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 >180dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

biometricidentity_government

Incident timeline

Jun 18, 2024breach begins
Jun 23, 2024discovered
notification delay · 59 days
Aug 21, 2024first dated filing
Sep 2, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. JUN 23Leak sitemonti postfirst record · attacker claim · unverifiedday 0
  2. AUG 21NE AGNE AG noticefiling day not on record · 14 NE residents—
  3. AUG 21HHS OCRHHS OCR noticestates nationwide total 292,913+59d
  4. DEC 31IN AGIN AG noticestates nationwide total 357,000+191d
  5. DEC 31NE AGNE AG noticefiling day not on record · no count stated—
  6. JAN 7ME AGME AG noticestates nationwide total 357,000+198d
  7. JAN 7MT AGMT AG notice12 MT residents+198d
  8. JAN 7MA AGMA AG notice248 MA residents+198d
  9. JAN 13NH AGNH AG notice3 NH residents+204d
  10. AUG 29ME AGME AG noticestates nationwide total 394,752+432d
  11. SEP 2NH AGNH AG notice28 NH residents+436d
  12. SEP 2VT AGVT AG noticemost recent · no count stated+436d
  13. NOV 13MD AGMD AG noticefiling day not on record · 18 MD residents—
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 18, 2024 – Jun 27, 2024
NE AG
Discovered
Jun 23, 2024· 5d undetected
NE AG + ME AG + MT AG +3
Data types
Biometric · Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
NE AG + NH AG + MD AG +5
Attack vector
Unauthorized Access
NE 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)

394,752

Sum of filed state slices

406· 0.1% of stated

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

US394,752
MA248
IN54
ME32
NH28
MD18
NE14
MT12

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 report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing12 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 Oct 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

377 days

Cadence

~1 / 47.1d

vs. multi-state median

62.8× 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.