Clustered 2 filings across 2 jurisdictions · filing window Feb 27, 2026 → Mar 31, 2026. View entity profile → Other incidents for this victim →
incident inc_dbb87733ac32437e · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
OR WA
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 4, 2024 → Dec 9, 2024
When the intrusion reportedly occurred, per the linked filings
Dec 9, 2024
Reported by WASHINGTON AG, OREGON AG filings
Drivestream Inc., a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2024-12-09 and filed notice on 2026-02-27. 505 Washington residents were affected. 445 days elapsed between awareness and notification. 5 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 505
Drivestream, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2026-03-31. The breach occurred during 12/4/2024 - 12/9/2024. The breach was discovered on 12/9/2024. 91,108 individuals were affected. Notice was sent on 3/31/2026.
Affected (this filing): 91,108
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.