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

Wisner Baum LLP — October 2025 breach

Clustered 11 filings across 10 jurisdictions · filing window Jan 1, 2026 → Jan 27, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

28,823

First → last filing

Jan 1, 2026 → Jan 27, 2026

Merge confidence

100%

incident inc_2b5a33677f2b4aa9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Oct 8, 2025–Oct 9, 2025, discovered Dec 15, 2025 — the first regulatory filing landed 17 days later. 28,823 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Financial account, and 3 more. Notifications rolled out on a 26-day schedule across 11 filings beginning Jan 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
17days

Discovered → first regulatory filing

Discovery variance
36days

Range of discovered_at dates across filings

Filing span
26days

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 clocksWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 39dCalifornia✓ CA AG copy ≤15d · 1dVermont✓ VT AG ≤14 bdayOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 8, 2025breach begins
Dec 15, 2025discovered · members disagree
notification delay · 17 days
Jan 1, 2026first filing
Jan 27, 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JAN 23WA AGWA AG notice717 WA residents+22d
  3. JAN 23MA AGMA AG noticeno count stated+22d
  4. JAN 23CA AGCA AG noticeno count stated+22d
  5. JAN 23IN AGIN AG noticestates nationwide total 16,922+22d
  6. JAN 23VT AGVT AG noticeno count stated+22d
  7. JAN 23ME AGME AG notice56 ME residents+22d
  8. JAN 23OR AGOR AG noticestates nationwide total 28,823+22d
  9. JAN 23IN AGIN AG noticestates nationwide total 16,922+22d
  10. JAN 23NE AGNE AG notice74 NE residents+22d
  11. JAN 27TX AGTX AG noticemost recent · states nationwide total 28,823+26d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 8, 2025 – Oct 9, 2025
WA AG
Discovered
Dec 15, 2025IL AG + WA AG + ME AG +3Jan 20, 2026VT AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + WA AG + TX AG +5
Attack vector
Ransomware
WA 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)

28,823

Sum of filed state slices

4,271· 14.8% of stated

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

US28,823
TX3,154
WA717
IN270
NE74
ME56

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
deterministic
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

26 days

Cadence

~1 / 2.6d

vs. multi-state median

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