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

Rodenburg Law Firm — August 2025 breach

Clustered 10 filings across 9 jurisdictions · filing window Dec 9, 2025 → Jul 2, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

81,307

First → last filing

Dec 9, 2025 → Jul 2, 2026

Merge confidence

100%

incident inc_a268c2244ef44851 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 26, 2025, discovered Aug 26, 2025 — the first regulatory filing landed 238 days later (flagged late). 81,307 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 205-day schedule across 9 filings beginning Dec 9, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
238days

Discovered → first regulatory filing

Discovery variance
197days

Range of discovered_at dates across filings

Leak precedence
133days 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
205days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine✗ ME AG >90d · 241dCalifornia✗ CA 60-day late · 238dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 26, 2025breach begins
Aug 26, 2025discovered · members disagree
notification delay · 238 days
Apr 21, 2026first filing
Jul 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. DEC 9Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. APR 21NE AGNE AG noticeno count stated+133d
  3. APR 21IN AGIN AG noticestates nationwide total 81,307+133d
  4. APR 21IN AGIN AG noticestates nationwide total 81,307+133d
  5. APR 24TX AGTX AG noticestates nationwide total 81,307+136d
  6. APR 24MT AGMT AG notice14,382 MT residents+136d
  7. APR 24MA AGMA AG notice37 MA residents+136d
  8. APR 24ME AGME AG noticestates nationwide total 81,307+136d
  9. APR 30NH AGNH AG notice17 NH residents+142d
  10. JUL 2CA AGCA AG noticemost recent · no count stated+205d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 26, 2025
IN AG
Discovered
Aug 26, 2025NE AG + MT AG + ME AG +2Mar 11, 2026TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
NE AG + TX AG + MT AG +4
Attack vector
Unauthorized Access
NE 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)

81,307

Sum of filed state slices

15,131· 18.6% of stated

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

US81,307
MT14,382
TX606
IN72
MA37
ME17
NH17

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 filing9 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 14, 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

205 days

Cadence

~1 / 22.8d

vs. multi-state median

25.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.