DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed9 records · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlynxhigh sensitivity
Merged incident · 9 records

Sheheen, Hancock & Godwin, LLP. — April 2025 breach

Clustered 9 records across 8 jurisdictions: 8 filings and 1 leak-site claim · filing window Sep 25, 2025 → Oct 1, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 records

States

8

Affected · reported

42,077

First → last filing

Sep 25, 2025 → Oct 1, 2025

Merge confidence

100%

incident inc_434391bcf03d4623 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Apr 8, 2025, discovered Apr 8, 2025 — the first regulatory filing landed 170 days later; 1 later filing was flagged late. 42,077 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 6-day schedule across 8 filings beginning Sep 25, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
170days

Discovered → first regulatory filing

Discovery variance
41days

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

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksTexas✗ TX AG >30dLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 129dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 8, 2025breach begins
Apr 8, 2025discovered · members disagree
notification delay · 170 days
Sep 25, 2025first filing
Oct 1, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing and leak-site claim in this incident

  1. APR 7Leak sitelynx postfirst record · attacker claim · unverifiedday 0
  2. SEP 25IN AGIN AG noticestates nationwide total 42,077+171d
  3. SEP 25ME AGME AG notice49 ME residents+171d
  4. SEP 25NH AGNH AG notice19 NH residents+171d
  5. SEP 25VT AGVT AG noticeno count stated+171d
  6. SEP 25MA AGMA AG notice56 MA residents+171d
  7. SEP 25MT AGMT AG noticestates nationwide total 42,077+171d
  8. SEP 26TX AGTX AG noticestates nationwide total 42,077+172d
  9. OCT 1SC AGSC AG noticemost recent · 34,059 SC residents+177d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 8, 2025
IN AG
Discovered
Apr 8, 2025MT AGMay 19, 2025ME AG + TX AG + SC AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
ME AG + NH AG + VT AG +4
Attack vector
Unauthorized Access
MT 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)

42,077

Sum of filed state slices

34,712· 82.5% of stated

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

US42,077
SC34,059
TX416
IN98
MA56
ME49
NH19
MT15

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

6 days

Cadence

~1 / 0.9d

vs. multi-state median

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