DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed8 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

Riddle & Butts, LLP — December 2025 breach

Clustered 8 filings across 6 jurisdictions · filing window Mar 10, 2026 → Jun 2, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

6,946

First → last filing

Mar 10, 2026 → Jun 2, 2026

Merge confidence

100%

incident inc_c0311928cc80446f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe unauthorized access. Intrusion Dec 30, 2025–Jan 7, 2026, discovered Jan 7, 2026 — the first regulatory filing landed 62 days later (flagged late). 6,946 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Notifications rolled out on a 84-day schedule across 8 filings beginning Mar 10, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
62days

Discovered → first regulatory filing

Discovery variance
36days

Range of discovered_at dates across filings

Filing span
84days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksTexas✗ TX AG >30dMaine⏱ ME AG >30d · 62dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 30, 2025breach begins
Jan 7, 2026discovered · members disagree
notification delay · 62 days
Mar 10, 2026first filing
Jun 2, 2026most 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. MAR 10IN AGIN AG noticefirst filing · states nationwide total 6,673day 0
  2. MAR 10MA AGMA AG noticeno count statedday 0
  3. MAR 10ME AGME AG noticestates nationwide total 6,673day 0
  4. MAR 10IN AGIN AG noticestates nationwide total 6,673day 0
  5. MAR 12TX AGTX AG noticestates nationwide total 6,673+2d
  6. JUN 2TX AGTX AG noticestates nationwide total 6,946+84d
  7. JUN 2NH AGNH AG notice1 NH residents+84d
  8. JUN 2NE AGNE AG noticemost recent · 4 NE residents+84d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 30, 2025
IN AG
Discovered
Jan 7, 2026ME AG + NH AG + NE AGFeb 12, 2026TX AGfilings disagree on discovery
Data types
Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MA AG + ME AG + TX AG +2
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)

6,946

Sum of filed state slices

6,663· 95.9% of stated

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

US6,946
TX6,650
IN7
NE4
ME1
NH1

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 claim

No leak-site claim on record for this incident.

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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
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

84 days

Cadence

~1 / 12d

vs. multi-state median

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