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

PILLSBURY WINTHROP SHAW PITTMAN LLP — April 2025 breach

Clustered 10 filings across 10 jurisdictions · filing window Nov 6, 2025 → Nov 7, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

43,412

First → last filing

Nov 6, 2025 → Nov 7, 2025

Merge confidence

100%

incident inc_547937786d0b4583 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe a phishing attack. Intrusion Apr 1, 2025–Apr 30, 2025, discovered Apr 1, 2025 — the first regulatory filing landed 219 days later (flagged late). 43,412 individuals reported across the linked filings. Data reported: Government ID, Financial account, PII, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
219days

Discovered → first regulatory filing

Discovery variance
29days

Range of discovered_at dates across filings

Filing span
1days

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 >90dTexas✗ TX AG >30dSouth Carolina✓ SC CRA notice dueIowa✓ IA AG ≤5 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 1, 2025breach begins
Apr 1, 2025discovered · members disagree
notification delay · 219 days
Nov 6, 2025first filing
Nov 7, 2025most 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. NOV 6MA AGMA AG noticefirst filing · 12 MA residentsday 0
  2. NOV 6NH AGNH AG notice4 NH residentsday 0
  3. NOV 6SC AGSC AG notice3,061 SC residentsday 0
  4. NOV 6WA AGWA AG notice32 WA residentsday 0
  5. NOV 6NE AGNE AG noticeno count statedday 0
  6. NOV 6MT AGMT AG notice13 MT residentsday 0
  7. NOV 6IA AGIA AG noticeno count statedday 0
  8. NOV 6DE AGDE AG noticeno count statedday 0
  9. NOV 6IN AGIN AG noticestates nationwide total 43,412day 0
  10. NOV 7TX AGTX AG noticemost recent · states nationwide total 43,412+1d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 20, 2025 – Apr 30, 2025
SC AG
Discovered
Apr 1, 2025WA AG + MT AGApr 23, 2025DE AGApr 30, 2025SC AG + NE AG + TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MA AG + NH AG + TX AG +6
Attack vector
Phishing
NH 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)

43,412

Sum of filed state slices

42,712· 98.4% of stated

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

US43,412
TX39,573
SC3,061
WA32
IN17
MT13
MA12
NH4

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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

8.0× faster

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.