Confirmed breach. Intrusion Dec 21, 2020, discovered Dec 21, 2020 — the first regulatory filing landed 51 days later. 8,564 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksWashington⏱ WA AG >30dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
8,564
Data types
—
Jurisdictions
2
MT WA
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Dec 21, 2020
When the intrusion reportedly occurred, per the linked filings
City of Ellensburg, Washington, a government sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2020-12-21 and filed notice on 2021-02-10. 8,523 Washington residents were affected. 51 days elapsed between awareness and notification.
Affected (this filing): 8,523
WA AG >30d
🦬Montana State AGMost recentlinked via multistate filing link · 100%
City of Ellensburg, Washington reported a data breach to the Montana Attorney General. The breach was reported on 2021-02-10. The breach occurred on 12/21/2020. 41 Montana residents were affected.
Affected (this filing): 41
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.