Northwest Crop Protection LLC — January 2023 breach
Clustered 2 filings across 2 jurisdictions · filing window Oct 1, 2024 → Oct 7, 2024. View entity profile → Other incidents for this victim →
incident inc_ea4666f76fbf4a63 · merged by deterministic · confidence 100%
Litigation Timing
Discovered → first regulatory filing
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.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- OCT 1NH AGNH AG noticefirst filing · 21 NH residentsday 0
- OCT 7ME AGME AG noticemost recent · states nationwide total 7,307auto-linked+6d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Jan 1, 2023 – Mar 31, 2023 NH AG
- Discovered
- May 15, 2023· 134d undetected ME AG
- Data types
- Financial account · PII · Identity (basic) NH AG + ME AG
- Attack vector
- Third-Party / Supply Chain NH AG
- Response
- Rebuilt their webhost and infrastructure from the ground up · Implemented two factor authentication for all server administration actions · Installed Managed Endpoint Detection and Response (mEDR) software on all servers and user computers NH AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Count reconciliation
per-state reported counts
Nationwide (stated in a filing)
7,307
Sum of filed state slices
51· 0.7% of stated
99% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
6 days
vs. multi-state median
1.2× slower
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.