DisclosureLens
Leak SiteState AGConfirmed4 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedsilentransomgrouphigh sensitivity
Merged incident · 4 filings

Sanchez Daniels & Hoffman LLP — March 2023 breach

Clustered 4 filings across 4 jurisdictions · filing window Apr 26, 2024 May 1, 2024. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

4 filings

States

3

Affected · reported

3,938

First → last filing

Apr 26, 2024 May 1, 2024

Merge confidence

100%

incident inc_4f39990baf4d43d9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings and 1 unverified claim. The filing describes unauthorized access. Intrusion Mar 9, 2023–May 1, 2023, discovered Apr 15, 2024 — the first regulatory filing landed 11 days later. 3,938 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 5-day schedule across 3 filings beginning Apr 26, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
11days

Discovered → first regulatory filing

Leak precedence
Noneclaim trailed by 6d

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

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delayno SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksMaine ME AG ≤30d · 11dMassachusetts MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 9, 2023breach begins
Apr 15, 2024discovered
notification delay · 11 days
Apr 26, 2024first filing
Apr 27, 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. APR 26IN AGIN AG noticefirst filing · states nationwide total 3,938day 0
  2. APR 26ME AGME AG noticestates nationwide total 3,938day 0
  3. APR 27MA AGMA AG notice2 MA residents+1d
  4. MAY 1Leak sitesilentransomgroup postmost recent · attacker claim · unverified+6d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 9, 2023
IN AG
Discovered
Apr 15, 2024· 403d undetected
ME AG
Data types
Identity (basic) · Government ID
ME AG + MA AG
Attack vector
Unauthorized Access
ME 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,938

Sum of filed state slices

63· 1.6% of stated

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

US3,938
IN60
MA2
ME1

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 filing3 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 23, 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

5 days

Cadence

~1 / 1.7d

vs. multi-state median

1.6× faster

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.