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

Lee Valley Tools Ltd. — October 2024 breach

Clustered 12 filings across 12 jurisdictions · filing window Apr 9, 2025 → Jun 6, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

12 filings

States

12

Affected · reported

57,708

First → last filing

Apr 9, 2025 → Jun 6, 2025

Merge confidence

100%

incident inc_ee47796fa3354799 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe hacking. Intrusion Oct 8, 2024–Mar 12, 2025, discovered Mar 12, 2025 — the first regulatory filing landed 28 days later (flagged late). 57,708 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Financial credentials, and 1 more. Notifications rolled out on a 58-day schedule across 12 filings beginning Apr 9, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
28days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
58days

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 clocksTexas✗ TX AG >30dVermont⏱ VT AG >14 bdayWashington✓ WA AG ≤30dMaine✓ ME AG ≤30d · 28dCalifornia✓ CA 60-day OK · 16dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Oct 8, 2024breach begins
Mar 12, 2025discovered
notification delay · 28 days
Apr 9, 2025first filing
Jun 6, 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. APR 9WA AGWA AG noticefirst filing · 2,882 WA residentsday 0
  2. APR 9IA AGIA AG notice583 IA residentsday 0
  3. APR 9MA AGMA AG notice2,436 MA residentsday 0
  4. APR 9NH AGNH AG notice774 NH residentsday 0
  5. APR 9ME AGME AG noticestates nationwide total 57,707day 0
  6. APR 9CA AGCA AG noticeno count statedday 0
  7. APR 9OR AGOR AG noticestates nationwide total 57,707day 0
  8. APR 9MT AGMT AG notice520 MT residentsday 0
  9. APR 15IN AGIN AG noticestates nationwide total 57,707+6d
  10. APR 15NE AGNE AG noticeno count stated+6d
  11. APR 15VT AGVT AG noticeno count stated+6d
  12. JUN 6TX AGTX AG noticemost recent · states nationwide total 57,708+58d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 8, 2024 – Mar 12, 2025
WA AG
Discovered
Mar 12, 2025· 155d undetected
WA AG + IA AG + NH AG +7
Data types
Financial account · Financial credentials · Identity (basic) · PCI
WA AG + IA AG + NH AG +7
Attack vector
Unauthorized Access
WA 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)

57,708

Sum of filed state slices

11,809· 20.5% of stated

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

US57,708
WA2,882
TX2,656
MA2,436
IN1,022
ME936
NH774
IA583
MT520

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

58 days

Cadence

~1 / 5.3d

vs. multi-state median

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