DisclosureLens
Leak SiteHHS OCRState AGConfirmed6 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedpearhigh sensitivity
Merged incident · 6 records

Western Orthopaedics — September 2025 breach

Clustered 6 records across 5 jurisdictions: 5 filings and 1 leak-site claim · filing window May 1, 2026 → May 5, 2026 (dated filings only). View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

6 records

States

5

Affected · reported

113,330

First → last dated filing

May 1, 2026 → May 5, 2026

Merge confidence

100%

incident inc_dc171be9d4ea4360 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Sep 17, 2025–Sep 25, 2025, discovered Oct 2, 2025 — the first regulatory filing landed 211 days later (flagged late); 1 later filing was also flagged late. 113,330 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
211days

Discovered → first regulatory filing

Discovery variance
152days

Range of discovered_at dates across filings

Leak precedence
209days 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
4days

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 >180dMassachusetts✗ MA AG >90dTexas✗ TX AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 17, 2025breach begins
Oct 2, 2025discovered · members disagree
notification delay · 211 days
May 1, 2026first dated filing
May 5, 2026most 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. SEP 30Leak sitepear postfirst record · attacker claim · unverifiedday 0
  2. MAY 1MT AGMT AG notice100 MT residents+213d
  3. MAY 1HHS OCRHHS OCR noticestates nationwide total 113,330+213d
  4. MAY 1MA AGMA AG notice46 MA residents+213d
  5. MAY 1NE AGNE AG noticefiling day not on record · no count stated—
  6. MAY 5TX AGTX AG noticemost recent · states nationwide total 113,330+217d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 17, 2025 – Sep 25, 2025
MT AG
Discovered
Oct 2, 2025MT AG + MA AG + NE AGMar 3, 2026TX AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · Financial account · Health (basic) · PHI
MT AG + HHS OCR + MA AG +2
Attack vector
Unauthorized Access
MT 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)

113,330

Sum of filed state slices

509· 0.4% of stated

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

US113,330
TX363
MT100
MA46

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 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
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

4 days

Cadence

~1 / 1.3d

vs. multi-state median

1.5× faster

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.