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

Wolf Haldenstein Adler Freeman & Herz LLP — December 2023 breach

Clustered 16 records across 13 jurisdictions: 15 filings and 1 leak-site claim · filing window May 23, 2024 → Jan 28, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

16 records

States

13

Affected · reported

3,445,537

First → last dated filing

May 23, 2024 → Jan 28, 2025

Merge confidence

100%

incident inc_b9a72aa9eb464dc6 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings and 1 unverified claim. Intrusion Dec 12, 2023–Dec 13, 2023, discovered Dec 13, 2023 — the first regulatory filing landed 162 days later; 3 later filings were flagged late. 3,445,537 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 3 more. Notifications rolled out on a 250-day schedule across 12 dated filings beginning May 23, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
162days

Discovered → first regulatory filing

Discovery variance
127days

Range of discovered_at dates across filings

Leak precedence
153days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
250days

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 >180dCalifornia✗ CA 60-day late · 394dWashington✗ WA AG >90dRhode Island✗ RI AG >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 12, 2023breach begins
Dec 13, 2023discovered · members disagree
notification delay · 162 days
May 23, 2024first dated filing
Jan 28, 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. DEC 22Leak siteblack_basta postfirst record · attacker claim · unverifiedday 0
  2. MAY 23VT AGVT AG noticeno count stated+152d
  3. MAY 23IN AGIN AG noticestates nationwide total 211+152d
  4. MAY 23NE AGNE AG noticefiling day not on record · no count stated—
  5. JAN 13DE AGDE AG noticeno count stated+387d
  6. JAN 13IN AGIN AG noticestates nationwide total 3,445,537+387d
  7. JAN 14NH AGNH AG notice3,802 NH residents+388d
  8. JAN 15CA AGCA AG noticeno count stated+389d
  9. JAN 15ME AGME AG noticestates nationwide total 3,445+389d
  10. JAN 16WA AGWA AG notice67,820 WA residents+390d
  11. JAN 17SC AGSC AG noticeno count stated+391d
  12. JAN 17MA AGMA AG notice21,182 MA residents+391d
  13. JAN 17IA AGIA AG notice17,378 IA residents+391d
  14. JAN 28RI AGRI AG noticemost recent · 16,071 RI residents+402d
  15. NOV 13MD AGMD AG noticefiling day not on record · 79,732 MD residents—
  16. NOV 13MD AGMD AG noticefiling day not on record · 79,732 MD residents—
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 13, 2023
IN AG
Discovered
Dec 13, 2023DE AG + NH AG + CA AG +4Apr 18, 2024NE AG + ME AG + RI AGfilings disagree on discovery
Data types
Employment · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + DE AG + NH AG +8
Attack vector
Unauthorized Access
VT 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)

3,445,537

Sum of filed state slices

234,635· 6.8% of stated

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

US3,445,537
MD79,732
WA67,820
IN25,430
MA21,182
IA17,378
RI16,071
NH3,802
ME3,220

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

250 days

Cadence

~1 / 22.7d

vs. multi-state median

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