Confirmed breach. discovered Dec 26, 2024 — the first regulatory filing landed 256 days later (flagged late). 1,099 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksWashington✗ WA AG >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
1,099
Data types
—
Jurisdictions
1
WA
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Skagit County, WA, a government sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2024-12-26 and filed notice on 2025-09-08. 1,099 Washington residents were affected. 256 days elapsed between awareness and notification. 0 days to identify the breach.
Affected (this filing): 1,099
WA AG >90d
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.