DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed16 records · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit2high sensitivity
Merged incident · 16 records

WARNER NORCROSS & JUDD LLP — June 2021 breach

Clustered 16 records across 10 jurisdictions: 15 filings and 1 leak-site claim · filing window Jul 11, 2022 → Aug 26, 2022 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

16 records

States

10

Affected · reported

255,160

First → last dated filing

Jul 11, 2022 → Aug 26, 2022

Merge confidence

100%

incident inc_5da452244a3a4722 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings and 1 unverified claim. Intrusion Jun 1, 2021–Oct 22, 2021, discovered Jun 28, 2021. 255,160 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 46-day schedule across 14 dated filings beginning Jul 11, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
116days

Range of discovered_at dates across filings

Filing span
46days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dCalifornia✗ CA 60-day late · 262dOregon✗ OR AG >45dWashington✗ WA AG >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 1, 2021breach begins
Jun 28, 2021discovered · members disagree
Jul 11, 2022first dated filing
Aug 26, 2022most 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 and leak-site claim in this incident

  1. OCT 22Leak sitelockbit2 postfirst record · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JUL 11IN AGIN AG noticestates nationwide total 19,274+262d
  4. JUL 11CA AGCA AG noticeno count stated+262d
  5. JUL 11ME AGME AG noticestates nationwide total 19,280+262d
  6. JUL 11MA AGMA AG notice1,157 MA residents+262d
  7. AUG 15OR AGOR AG noticestates nationwide total 214,439+297d
  8. AUG 15WA AGWA AG notice747 WA residents+297d
  9. AUG 16SC AGSC AG notice1,565 SC residents+298d
  10. AUG 16MT AGMT AG notice237 MT residents+298d
  11. AUG 17CA AGCA AG noticeno count stated+299d
  12. AUG 17ME AGME AG noticestates nationwide total 214,439+299d
  13. AUG 24HHS OCRHHS OCR noticestates nationwide total 255,160+306d
  14. AUG 25CA AGCA AG noticeno count stated+307d
  15. AUG 26OR AGOR AG noticestates nationwide total 255,160+308d
  16. AUG 26WA AGWA AG noticemost recent · 780 WA residents+308d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 1, 2021
IN AG
Discovered
Jun 28, 2021ME AGOct 22, 2021IL AG + CA AG + OR AG +4filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
CA AG + WA AG + SC AG +4
Attack vector
Unauthorized Access
ME 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)

255,160

Sum of filed state slices

6,285· 2.5% of stated

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

US255,160
IN2,415
SC1,565
MA1,157
WA780
MT237
ME131

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 25, 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

46 days

Cadence

~1 / 3.5d

vs. multi-state median

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