GLOBALClaimed by LockBit 3.xFirst sighting
Posted to leak site Aug 10, 2022bd_88fe38d865e0c77d
Clustered 4 filings across 4 jurisdictions · filing window Aug 10, 2022 → May 13, 2023. View entity profile → Other incidents for this victim →
incident inc_528d075a114d4884 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
MT OR WA
Leak Site · State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Jul 29, 2022
When the intrusion reportedly occurred, per the linked filings
Jul 29, 2022
Reported by WASHINGTON AG filing
Whitworth University, a education sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2022-07-29 and filed notice on 2022-10-04. 41,746 Washington residents were affected. 67 days elapsed between awareness and notification. -39 days to identify the breach. 39 days to contain the breach.
Affected (this filing): 41,746
Whitworth University reported a data breach to the Montana Attorney General. The breach was reported on 2023-05-12. The breach occurred on 7/29/2022. 1,223 Montana residents were affected.
Affected (this filing):
Whitworth University reported a data breach to the Oregon Attorney General. The breach was reported on 2023-05-13. The breach occurred during 7/29/2022 - 7/29/2022. The breach was discovered on 1/1/0001. 65,593 individuals were affected. Notice was sent on 1/1/0001.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Affected (this filing): 65,593