All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed4 filings · 4 statesUnverified claimConfirmedEnforcedcritical sensitivity

Merged incident · 4 filings

Alta Orthopaedics Medical Group, Inc. — February 2026 breach

Clustered 4 filings across 4 jurisdictions · filing window Jul 3, 2026 → Jul 8, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

24,496

First → last filing

Jul 3, 2026 → Jul 8, 2026

Merge confidence

100%

incident inc_192ea67dadb64a43 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe unauthorized access. Intrusion Feb 3, 2026–Feb 6, 2026, discovered Mar 10, 2026 — the first regulatory filing landed 115 days later (flagged late). 24,496 individuals reported across the linked filings. Data reported: Government ID, Biometric, PHI, and 3 more. Notifications rolled out on a 5-day schedule across 4 filings beginning Jul 3, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

115days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

5days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMassachusetts✗ MA AG >90dCalifornia✗ CA 30-day late · 118dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

biometricidentity_government

Incident timeline

Feb 3, 2026breach begins

Mar 10, 2026discovered

notification delay · 115 days

Jul 3, 2026first filing

Jul 8, 2026most recent filing

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

Member cascade — every filing about this breach

JUL 3HHS OCRHHS OCR noticefirst filing · states nationwide total 24,496auto-linkedday 0
JUL 6NH AGNH AG notice3 NH residentsauto-linked+3d
JUL 8MA AGMA AG notice19 MA residentsauto-linked+5d
JUL 8CA AGCA AG noticemost recent · no count statedauto-linked+5d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Feb 3, 2026 – Feb 6, 2026
Discovered: Mar 10, 2026· 35d undetected
Data types: Biometric · Financial account · Health (basic) · Identity (basic) · Government ID · PHI
Attack vector: Unauthorized Access

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)

24,496

Sum of filed state slices

22· 0.1% of stated

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

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

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

5 days

Cadence

~1 / 1.7d

vs. multi-state median

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