DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed7 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 7 filings

OrthoAlaska, LLC — September 2022 breach

Clustered 7 filings across 7 jurisdictions · filing window Apr 3, 2023 → Oct 13, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

161,130

First → last filing

Apr 3, 2023 → Oct 13, 2023

Merge confidence

100%

incident inc_b8a90ef2ad0e4311 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe unauthorized access. Intrusion Sep 6, 2022–Oct 13, 2022, discovered Oct 12, 2022 — the first regulatory filing landed 173 days later (flagged late). 161,130 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 5 more. Notifications rolled out on a 193-day schedule across 7 filings beginning Apr 3, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
173days

Discovered → first regulatory filing

Discovery variance
33days

Range of discovered_at dates across filings

Filing span
193days

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 clocksCalifornia✗ CA 60-day late · 364dOregon✗ OR AG >45dMaine✗ ME AG >90d · 333dWashington✗ WA AG >90dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Sep 6, 2022breach begins
Oct 12, 2022discovered · members disagree
notification delay · 173 days
Apr 3, 2023first filing
Oct 13, 2023most recent filing

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

Member cascade — every filing about this breach

  1. APR 3MT AGMT AG noticefirst filing · 209 MT residentsday 0
  2. OCT 12NH AGNH AG notice40 NH residents+192d
  3. OCT 13CA AGCA AG noticeno count stated+193d
  4. OCT 13OR AGOR AG noticestates nationwide total 161,130+193d
  5. OCT 13MA AGMA AG notice74 MA residents+193d
  6. OCT 13ME AGME AG noticestates nationwide total 161,130+193d
  7. OCT 13WA AGWA AG noticemost recent · 1,529 WA residents+193d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 6, 2022
CA AG
Discovered
Oct 12, 2022MT AG + NH AG + CA AG +1Nov 14, 2022OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
MT AG + NH AG + CA AG +3
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)

161,130

Sum of filed state slices

1,921· 1.2% of stated

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

US161,130
WA1,529
MT209
MA74
ME69
NH40

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

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

193 days

Cadence

~1 / 32.2d

vs. multi-state median

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