DisclosureLens
GLOBALMalwareAgriculture & FoodAgricultureRansomwareInc RansomRansom DemandedActor NamedData Leak ThreatenedData PublishedHigh

Monterey Mushrooms, Inc.

bd_13df222688d571e3 · schema v1 · pii pii-v1

Severity

High

Discovered

Filed

Aug 7, 2025

To disclose

Affected

Not disclosed

Linked

10 filings

Confidence

50%
Full breach record for Monterey Mushrooms, Inc.

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group INC Ransom on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.

Group activity: Agriculture and Food ProductionDiscovered: 2025-09-04

Source: Ransomware.live

Post text · scraped from the leak site

Monterey Mushrooms, Inc. was initially established in 1971 as a single farm operation in Royal Oaks, California. Today, this multi-site business is headquartered in Watsonville, California, and has production, sales and administrative offices, internationally. Monterey is the country’s largest and only national marketer of fresh mushrooms, supplying products for sale to supermarkets, foodservice and ingredient manufacture operations, and for preparation of processed, canned, and frozen mushroom products. In 1999, the company furthered its expansion into the Midwestern and Southeastern regions via the acquisition of mushroom farms in Princeton, Illinois, and Orlando, Florida. Monterey also continued its expansion in the Pacific Northwest via contracted pounds from Canada - all pounds are packed and distributed under the Monterey Mushrooms label.

Incident timeline — mostly unverified

? — ?

Breach window unknown

Aug 7, 2025

Claim posted

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

Claim → filing

Compliance clock

Not assessable

This filing is one of 10 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (2)

Regulatory filings (7) · sorted by filing gap

Show 3 more filingsup to 43d gap

Filing propagation · 8 filings · 7 states

View merged incident ↗

Pattern: first filing Aug 7, last Sep 19 (TX) — a 43-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claimThis record

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source ceiling

  • actor name
  • victim claim
  • ransom/leak status
  • discovery date
  • materiality
  • notification
  • affected count
  • confirmed data types
  • compliance clock

The ✕ fields stay blank until a regulatory filing or victim disclosure lands.