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

DAVID'S BRIDAL, LLC — January 2024 breach

Clustered 13 records across 10 jurisdictions: 11 filings and 2 leak-site claims · filing window Sep 13, 2024 → Nov 11, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 records

States

10

Affected · reported

46,165

First → last dated filing

Sep 13, 2024 → Nov 11, 2024

Merge confidence

100%

incident inc_9db4df65c9d74b73 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings and 2 unverified claims. Intrusion Jan 20, 2024–Jan 21, 2024, discovered Jan 20, 2024. 46,165 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 2 more. Notifications rolled out on a 59-day schedule across 10 dated filings beginning Sep 13, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
208days

Range of discovered_at dates across filings

Filing span
59days

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 >180dVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 237dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 20, 2024breach begins
Jan 20, 2024discovered · members disagree
Sep 13, 2024first dated filing
Nov 11, 2024most 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. JAN 22Leak sitelockbit_3 postfirst record · attacker claim · unverifiedday 0
  2. FEB 14Leak sitewerewolves postattacker claim · unverified+22d
  3. SEP 1IL AGIL AG noticefiling day not on record · no count stated—
  4. SEP 13WA AGWA AG notice911 WA residents+234d
  5. SEP 13IN AGIN AG noticestates nationwide total 46,165+234d
  6. SEP 13MT AGMT AG notice126 MT residents+234d
  7. SEP 13VT AGVT AG noticeno count stated+234d
  8. SEP 13OR AGOR AG noticestates nationwide total 46,165+234d
  9. SEP 13MA AGMA AG notice283 MA residents+234d
  10. SEP 13ME AGME AG notice58 ME residents+234d
  11. SEP 13NH AGNH AG notice41 NH residents+234d
  12. SEP 16CA AGCA AG noticeno count stated+237d
  13. NOV 11CA AGCA AG noticemost recent · no count stated+293d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 20, 2024 – Jan 21, 2024
WA AG
Discovered
Jan 20, 2024IL AG + MT AG + VT AG +1Jan 21, 2024WA AG + ME AG + NH AGAug 15, 2024OR AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + MT AG + VT AG +4
Attack vector
Ransomware
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)

46,165

Sum of filed state slices

2,753· 6.0% of stated

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

US46,165
IN1,334
WA911
MA283
MT126
ME58
NH41

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 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 25, 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

59 days

Cadence

~1 / 6.6d

vs. multi-state median

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