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

OrthoMinds — November 2024 breach

Clustered 10 filings across 10 jurisdictions · filing window Mar 1, 2025 → Mar 20, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

93,598

First → last filing

Mar 1, 2025 → Mar 20, 2025

Merge confidence

100%

incident inc_529b40ceb7c444b7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Nov 17, 2024–Nov 27, 2024, discovered Nov 1, 2024 — the first regulatory filing landed 120 days later (flagged late). 93,598 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 5 more. Notifications rolled out on a 19-day schedule across 10 filings beginning Mar 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
120days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
19days

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 clocksMaine✗ ME AG >90d · 139dMaryland✗ MD AG >90dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Nov 17, 2024breach begins
Nov 1, 2024discovered
notification delay · 120 days
Mar 1, 2025first filing
Mar 20, 2025most 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. MAR 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 20ME AGME AG notice5 ME residents+19d
  3. MAR 20CA AGCA AG noticeno count stated+19d
  4. MAR 20NE AGNE AG notice10 NE residents+19d
  5. MAR 20NH AGNH AG noticeno count stated+19d
  6. MAR 20MD AGMD AG notice28 MD residents+19d
  7. MAR 20MT AGMT AG notice20 MT residents+19d
  8. MAR 20IN AGIN AG noticestates nationwide total 93,598+19d
  9. MAR 20VT AGVT AG noticeno count stated+19d
  10. MAR 20MA AGMA AG noticemost recent · 25 MA residents+19d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 17, 2024 – Nov 27, 2024
ME AG
Discovered
Nov 1, 2024
IL AG + ME AG + NE AG +4
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
IL AG + ME AG + NE AG +6
Attack vector
Unauthorized Access
ME 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)

93,598

Sum of filed state slices

112· 0.1% of stated

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

US93,598
MD28
MA25
IN24
MT20
NE10
ME5

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 filing10 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
Reviewed
operator-reviewed Jun 12, 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

19 days

Cadence

~1 / 2.1d

vs. multi-state median

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