Clustered 2 filings across 2 jurisdictions · filed Dec 23, 2020. View entity profile → Other incidents for this victim →
incident inc_121b4679518341ec · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA OR
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
Nov 10, 2020 → Nov 11, 2020
When the intrusion reportedly occurred, per the linked filings
Nov 11, 2020
Reported by CALIFORNIA AG filing
Dec 11, 2020
Reported by OREGON AG filing
Tree Top, Inc. and Northwest Naturals LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2020-12-23. The breach occurred during 11/10/2020 - 11/11/2020. The breach was discovered on 12/11/2020. 18,000 individuals were affected. Notice was sent on 12/23/2020.
Affected (this filing): 18,000
Tree Top, Inc. and its subsidiary Northwest Naturals experienced a ransomware attack on November 10, 2020, discovered on November 11, 2020. Attackers gained access via a compromised user account and encrypted servers containing personal information of employees, applicants, cooperative members, and customers. Data exposed included names, addresses, SSNs, bank account info, health insurance numbers, and credit card details. The company engaged forensic experts, contained the breach, upgraded security controls, and offered one year of credit monitoring.
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.