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

WILMER CUTLER PICKERING HALE AND DORR LLP — May 2026 breach

Clustered 15 filings across 12 jurisdictions · filing window Jul 10, 2026 → Aug 21, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 filings

States

12

Affected · reported

not comparable

First → last dated filing

Jul 10, 2026 → Aug 21, 2026

Merge confidence

100%

incident inc_c1f82e04dc3d41ca · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings. Intrusion May 8, 2026, discovered May 8, 2026. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 42-day schedule across 13 dated filings beginning Jul 10, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
52days

Range of discovered_at dates across filings

Filing span
42days

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 clocksOregon✗ OR AG >45dMassachusetts⏱ MA AG >30dWashington⏱ WA AG >30dTexas✓ TX AG ≤30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 8, 2026breach begins
May 8, 2026discovered · members disagree
Jul 10, 2026first dated filing
Aug 21, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JUL 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JUL 10IN AGIN AG noticefirst filing · states nationwide total 33,156day 0
  3. JUL 10NE AGNE AG noticefiling day not on record · no count stated—
  4. JUL 10MA AGMA AG notice42 MA residentsday 0
  5. JUL 10MA AGMA AG notice42 MA residentsday 0
  6. JUL 10VT AGVT AG notice11 VT residentsday 0
  7. JUL 10NH AGNH AG notice35 NH residentsday 0
  8. JUL 10CA AGCA AG noticeno count statedday 0
  9. JUL 14TX AGTX AG noticestates nationwide total 4,711+4d
  10. JUL 15WA AGWA AG notice692 WA residents+5d
  11. AUG 5OR AGOR AG noticestates nationwide total 35,218+26d
  12. AUG 12SC AGSC AG notice14,496 SC residents+33d
  13. AUG 12DE AGDE AG noticeno count stated+33d
  14. AUG 19NH AGNH AG notice3,128 NH residents+40d
  15. AUG 21TX AGTX AG noticemost recent · 80,528 affected+42d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 8, 2026
IN AG
Discovered
May 8, 2026NE AG + MA AG + NH AG +5Jun 25, 2026TX AGJun 29, 2026IL AGfilings disagree on discovery
Data types
Education · Identity (basic) · Government ID · PII
IL AG + NE AG + MA AG +7
Attack vector
Unauthorized Access
NE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

US35,218
TX80,528
IN28,518
SC14,496
NH3,128
WA692
MA42
VT11

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

42 days

Cadence

~1 / 3.5d

vs. multi-state median

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