Confirmed breach. Intrusion Aug 2, 2025–Aug 7, 2025, discovered Aug 2, 2025 — the first regulatory filing landed 47 days later. 11 individuals reported across the linked filings.
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 clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
11
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 2, 2025 → Aug 7, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Aug 2, 2025
Reported by NEW HAMPSHIRE AG filing
47 days
⛰️New Hampshire State AGFirst filinglinked via multistate filing link · 100%
Monterey Mushrooms, LLC notified the New Hampshire Attorney General of a cybersecurity incident affecting one NH resident. Unauthorized access occurred between August 2-7, 2025. Data involved name, SSN, and potentially driver's license/passport numbers. Notification sent September 18, 2025, with credit monitoring offered.
Monterey Mushrooms reported a data breach to the Indiana Attorney General. The breach occurred on 2025-08-02 and was reported on 2025-09-18. 10 Indiana residents were affected.
Affected (this filing): 10
Leak >30d
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.