Clustered 3 filings across 3 jurisdictions · filing window Sep 10, 2025 → Jan 16, 2026. View entity profile → Other incidents for this victim →
incident inc_42a417726b314ece · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
OR WA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 9, 2025 → Sep 12, 2025
When the intrusion reportedly occurred, per the linked filings
First Fruits Farms, located in Prescott, Washington, is an agricu ltural company that specializes in apple and cherry orchards. We will upload 26gb of corporate documents soon. Employee persona l documents (SSNs, passports, w-9 forms), detailed financials, cu stomer data, contracts and agreements, projects, drawings and spe cifications, etc.
Sep 12, 2025
Reported by OREGON AG, WASHINGTON AG filings
FirstFruits Farms, LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2026-01-16. The breach occurred during 9/9/2025 - 9/12/2025. The breach was discovered on 9/12/2025. 7,007 individuals were affected. Notice was sent on 12/29/2025.
FirstFruits Farms, LLC, a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2025-09-12 and filed notice on 2026-01-16. 6,335 Washington residents were affected. 126 days elapsed between awareness and notification. 3 days to identify the breach. 0 days to contain the breach.
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.
Affected (this filing): 7,007
Affected (this filing): 6,335