DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed13 records · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3high sensitivity
Merged incident · 13 records

Legacy Professionals, LLP — April 2024 breach

Clustered 13 records across 11 jurisdictions: 12 filings and 1 leak-site claim · filing window Feb 27, 2025 → May 9, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 records

States

11

Affected · reported

216,752

First → last dated filing

Feb 27, 2025 → May 9, 2025

Merge confidence

100%

incident inc_7b716d83151e4486 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. Intrusion Apr 1, 2024–Apr 30, 2024, discovered Apr 1, 2024. 216,752 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 71-day schedule across 10 dated filings beginning Feb 27, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
29days

Range of discovered_at dates across filings

Filing span
71days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dMaryland✗ MD AG >90dCalifornia✗ CA 60-day late · 308dWashington✗ WA AG >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 1, 2024breach begins
Apr 1, 2024discovered · members disagree
Feb 27, 2025first dated filing
May 9, 2025most 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. MAY 3Leak sitelockbit_3 postfirst record · attacker claim · unverifiedday 0
  2. FEB 1IL AGIL AG noticefiling day not on record · no count stated—
  3. FEB 27IN AGIN AG noticestates nationwide total 190,818+300d
  4. FEB 27NE AGNE AG noticefiling day not on record · 848 NE residents—
  5. FEB 27IA AGIA AG notice1,672 IA residents+300d
  6. FEB 28MA AGMA AG notice501 MA residents+301d
  7. FEB 28MD AGMD AG notice477 MD residents+301d
  8. FEB 28MT AGMT AG notice154 MT residents+301d
  9. FEB 28HHS OCRHHS OCR noticestates nationwide total 216,752+301d
  10. FEB 28NH AGNH AG notice94 NH residents+301d
  11. FEB 28ME AGME AG notice60 ME residents+301d
  12. FEB 28CA AGCA AG noticeno count stated+301d
  13. MAY 9WA AGWA AG noticemost recent · 890 WA residents+371d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 25, 2024
IN AG
Discovered
Apr 1, 2024IL AG + IA AG + MD AG +2Apr 25, 2024ME AG + CA AGApr 27, 2024WA AGApr 30, 2024NE AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NE AG + IA AG + MD AG +7
Attack vector
Unauthorized Access
NE 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)

216,752

Sum of filed state slices

33,996· 15.7% of stated

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

US216,752
IN29,300
IA1,672
WA890
NE848
MA501
MD477
MT154
NH94
ME60

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 filing12 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 Aug 22, 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

71 days

Cadence

~1 / 7.9d

vs. multi-state median

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