Clustered 2 filings across 2 jurisdictions · filed Aug 16, 2022. View entity profile → Other incidents for this victim →
incident inc_0c0c9715edd34081 · 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
Sep 18, 2020 → Feb 3, 2022
When the intrusion reportedly occurred, per the linked filings
Feb 1, 2022
Reported by OREGON AG filing
Mar 3, 2022
Reported by WASHINGTON AG filing
Burnt Ridge Nursery and Orchards, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2022-08-16. The breach occurred during 9/18/2020 - 2/3/2022. The breach was discovered on 2/1/2022. 11,734 individuals were affected. Notice was sent on 8/15/2022.
Affected (this filing): 11,734
Burnt Ridge Nursery and Orchards, Inc., a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2022-03-03 and filed notice on 2022-08-16. 2,619 Washington residents were affected. 166 days elapsed between awareness and notification. 531 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 2,619
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.