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

DocketWise — September 2025 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

8

Affected · reported

143,480

First → last 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). 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 11 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 bdayMaine✗ ME AG >90d · 184dWashington⏱ WA AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 1, 2025breach begins
Oct 1, 2025discovered · members disagree
notification delay · 184 days
Apr 3, 2026first filing
May 22, 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. APR 3CA AGCA AG noticefirst filing · no count statedday 0
  2. APR 3NH AGNH AG notice15 NH residentsday 0
  3. APR 3NE AGNE AG notice94 NE residentsday 0
  4. APR 3VT AGVT AG notice34 VT residentsday 0
  5. APR 3IN AGIN AG noticestates nationwide total 116,666day 0
  6. APR 3WA AGWA AG notice689 WA residentsday 0
  7. APR 3ME AGME AG noticestates nationwide total 116,666day 0
  8. APR 4MA AGMA AG notice657 MA residents+1d
  9. MAY 1NH AGNH AG notice11 NH residents+28d
  10. MAY 1CA AGCA AG noticeno count stated+28d
  11. MAY 22ME AGME AG noticemost recent · states nationwide total 143,480+49d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 1, 2025
IN AG
Discovered
Oct 1, 2025CA AG + NH AG + NE AG +3Feb 19, 2026ME AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + NH AG + NE AG +4
Attack vector
Third-Party / Supply Chain
CA 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)

143,480

Sum of filed state slices

1,695· 1.2% of stated

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

US143,480
WA689
MA657
IN191
NE94
VT34
NH15
ME15

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 filing11 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 Jun 12, 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

49 days

Cadence

~1 / 4.9d

vs. multi-state median

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