DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed9 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblack_bastahigh sensitivity
Merged incident · 9 filings

LEONARD'S EXPRESS, INC. — November 2023 breach

Clustered 9 filings across 8 jurisdictions · filing window Dec 5, 2023 → Jun 18, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

6,540

First → last filing

Dec 5, 2023 → Jun 18, 2024

Merge confidence

100%

incident inc_39d3adef3ed24fd7 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. Intrusion Nov 15, 2023–Dec 2, 2023, discovered Dec 2, 2023 — the first regulatory filing landed 198 days later (flagged late). 6,540 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 196-day schedule across 8 filings beginning Dec 5, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
198days

Discovered → first regulatory filing

Discovery variance
160days

Range of discovered_at dates across filings

Leak precedence
195days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
196days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dMaine✗ ME AG >90d · 199dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 15, 2023breach begins
Dec 2, 2023discovered · members disagree
notification delay · 198 days
Jun 17, 2024first filing
Jun 18, 2024most 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. DEC 5Leak siteblack_basta postfirst filing · attacker claim · unverifiedday 0
  2. JUN 17DE AGDE AG noticeno count stated+195d
  3. JUN 17MA AGMA AG notice59 MA residents+195d
  4. JUN 17ME AGME AG noticestates nationwide total 6,540+195d
  5. JUN 17NH AGNH AG notice1 NH residents+195d
  6. JUN 17MT AGMT AG notice8 MT residents+195d
  7. JUN 17IN AGIN AG noticestates nationwide total 6,540+195d
  8. JUN 18ME AGME AG noticestates nationwide total 6,540+196d
  9. JUN 18VT AGVT AG noticemost recent · no count stated+196d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 15, 2023 – Dec 2, 2023
DE AG
Discovered
Dec 2, 2023DE AG + NH AG + MT AG +2May 10, 2024ME AGfilings disagree on discovery
Data types
Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PII
DE AG + ME AG + NH AG +3
Attack vector
Ransomware
DE 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)

6,540

Sum of filed state slices

89· 1.4% of stated

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

US6,540
MA59
IN18
MT8
ME3
NH1

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

196 days

Cadence

~1 / 24.5d

vs. multi-state median

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

Leonard's Express, Inc. data breach (2023) · DisclosureLens