DocketWise — September 2025 breach

Clustered 11 filings across 8 jurisdictions · filing window Apr 3, 2026 → May 22, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

Affected · reported

143,480

First → last dated filing

Apr 3, 2026 → May 22, 2026

Merge confidence

100%

incident inc_448db25ed6944c4e · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe hacking. Intrusion Sep 1, 2025–Oct 3, 2025, discovered Oct 1, 2025 — the first regulatory filing landed 184 days later (flagged late); 1 later filing was also flagged late. 143,480 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 49-day schedule across 10 dated filings beginning Apr 3, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

184days

Discovered → first regulatory filing

Discovery variance

141days

Range of discovered_at dates across filings

Filing span

49days

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 clocksCalifornia✗ CA 60-day late · 184dVermont✗ VT AG >45 bdayWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 184dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.