DisclosureLens
Leak SiteState AGConfirmed7 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3low sensitivity
Merged incident · 7 filings

Thede Culpepper Moore Munro & Silliman LLP — April 2024 breach

Clustered 7 filings across 6 jurisdictions · filing window Apr 21, 2024 May 15, 2025. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

1,259

First → last filing

Apr 21, 2024 May 15, 2025

Merge confidence

100%

incident inc_c5399e441c9244e0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Apr 11, 2024–Apr 12, 2024, discovered Apr 21, 2024 — the first regulatory filing landed 355 days later (flagged late). 1,259 individuals reported across the linked filings. Data reported: Identity (basic). Notifications rolled out on a 389-day schedule across 5 filings beginning Apr 21, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
355days

Discovered → first regulatory filing

Discovery variance
247days

Range of discovered_at dates across filings

Leak precedence
355days 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
389days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksVermont VT AG >45 bdayMaine ME AG >90d · 355dOregon OR AG >45dLeak gap Leak >180dFull clock table in Litigation Timeline

Incident timeline

Apr 11, 2024breach begins
Apr 21, 2024discovered · members disagree
notification delay · 355 days
Apr 11, 2025first filing
May 15, 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 21Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. MAY 7Leak sitelockbit_3 postattacker claim · unverified+16d
  3. APR 11VT AGVT AG noticeno count stated+355d
  4. APR 11ME AGME AG noticestates nationwide total 437+355d
  5. MAY 15OR AGOR AG noticestates nationwide total 1,259+389d
  6. MAY 15NE AGNE AG noticeno count stated+389d
  7. MAY 15IN AGIN AG noticemost recent · states nationwide total 1,259+389d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 11, 2024Apr 12, 2024
ME AG
Discovered
Apr 21, 2024VT AG + ME AG + NE AGDec 24, 2024OR AGfilings disagree on discovery
Data types
Identity (basic)
VT AG + ME AG + NE AG
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)

1,259

Sum of filed state slices

2· 0.2% of stated

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

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 filing5 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 Jun 12, 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

389 days

Cadence

~1 / 64.8d

vs. multi-state median

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