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

Whitworth University — July 2022 breach

Clustered 11 filings across 11 jurisdictions · filing window Aug 10, 2022 → May 19, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

65,593

First → last filing

Aug 10, 2022 → May 19, 2023

Merge confidence

100%

incident inc_528d075a114d4884 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. Intrusion Jul 29, 2022, discovered Jul 29, 2022 — the first regulatory filing landed 67 days later (flagged late). 65,593 individuals reported across the linked filings. Data reported: Government ID, Education, Financial account, and 5 more. Notifications rolled out on a 281-day schedule across 10 filings beginning Aug 10, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
67days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
54days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
281days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 288dCalifornia✗ CA 60-day late · 66dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 29, 2022breach begins
Jul 29, 2022discovered
notification delay · 67 days
Oct 4, 2022first filing
May 19, 2023most 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. AUG 10Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. OCT 4WA AGWA AG notice41,746 WA residents+54d
  3. APR 28IN AGIN AG noticestates nationwide total 65,593+260d
  4. APR 28VT AGVT AG noticeno count stated+260d
  5. MAY 12MT AGMT AG notice1,223 MT residents+274d
  6. MAY 12NH AGNH AG notice28 NH residents+274d
  7. MAY 13MA AGMA AG notice81 MA residents+275d
  8. MAY 13ME AGME AG noticestates nationwide total 65,593+275d
  9. MAY 13OR AGOR AG noticestates nationwide total 65,593+275d
  10. MAY 13CA AGCA AG noticeno count stated+275d
  11. MAY 19ID AGID AG noticemost recent · 2,425 ID residents+281d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 29, 2022
WA AG
Discovered
Jul 29, 2022
WA AG + VT AG + MT AG +4
Data types
Education · Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + CA AG + VT 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)

65,593

Sum of filed state slices

45,604· 69.5% of stated

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

US65,593
WA41,746
ID2,425
MT1,223
MA81
IN78
NH28
ME23

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 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 Aug 22, 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

281 days

Cadence

~1 / 28.1d

vs. multi-state median

35.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.