DisclosureLens
Leak SiteState AGConfirmed5 records · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedqilinhigh sensitivity
Merged incident · 5 records

Orthopaedic Specialists of Massachusetts — January 2026 breach

Clustered 5 records across 3 jurisdictions: 3 filings and 2 leak-site claims · filed Jun 12, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 records

States

3

Affected · reported

20,154

First → last filing

Jun 12, 2026

Merge confidence

100%

incident inc_60655b40f9ae47fc · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings and 2 unverified claims. The filing describes unauthorized access. Intrusion Jan 12, 2026–Jan 15, 2026, discovered Jan 15, 2026 — the first regulatory filing landed 148 days later. 20,154 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
148days

Discovered → first regulatory filing

Leak precedence
146days 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
0days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 12, 2026breach begins
Jan 15, 2026discovered
notification delay · 148 days
Jun 12, 2026first filing
—watching for filings

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

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

  1. JAN 17Leak sitebeast postfirst record · attacker claim · unverifiedday 0
  2. JAN 17Leak siteqilin postattacker claim · unverified+1d
  3. JUN 12MA AGMA AG notice20,147 MA residents+146d
  4. JUN 12NH AGNH AG noticestates nationwide total 244+146d
  5. JUN 12VT AGVT AG noticemost recent · 7 VT residents+146d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 12, 2026 – Jan 15, 2026
NH AG
Discovered
Jan 15, 2026· 3d undetected
NH AG
Data types
Financial · Health (basic) · Identity (basic) · Government ID · PHI
MA AG + NH AG + VT AG
Attack vector
Unauthorized Access
NH AG

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

Affected residents by state

per-state reported counts

US244
MA20,147
NH46
VT7

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

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

Press / market report

No press coverage linked yet.

State AG / regulator filing3 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 9, 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

0 days

Cadence

~1 / 0d

vs. multi-state median

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