Confirmed breach. Intrusion Jan 20, 2017–Jan 29, 2018. 16,023 individuals reported across the linked filings.
incident inc_989c295fdfa545bf · merge_method human · confidence 100%
Litigation Timing
Filing span
0days
Time between earliest and latest filing
Not recorded for this incident
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 clocksOregon✗ OR AG >45dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
16,023
Data types
—
Jurisdictions
2
MT OR
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 20, 2017 → Jan 29, 2018
When the intrusion reportedly occurred, per the linked filings
399 days
🦫Oregon State AGFirst filinglinked via operator-confirmed · 100%
North 40 Outfitters reported a data breach to the Oregon Attorney General. The breach was reported on 2018-02-23. The breach occurred during 1/20/2017 - 1/29/2018. The breach was discovered on 1/10/20181/29/2018. 14,734 individuals were affected. Notice was sent on 2/23/2018.
Affected (this filing): 14,734
OR AG >45d
🦬Montana State AGMost recentlinked via operator-confirmed · 100%
North 40 Outfitters reported a data breach to the Montana Attorney General. The breach was reported on 2018-02-23. The breach occurred from 1/20/2017 to 1/29/2018. 1,289 Montana residents were affected.
Affected (this filing): 1,289
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.