
Monterey Mushrooms hit by INC ransomware, employee data exposed
Monterey Mushrooms, LLC, a major U.S. mushroom producer, was hit by a cyberattack between August 2 and August 7, 2025. The INC ransomware group claimed responsibility and posted stolen data details to their dark web site around September 5, 2025. An unauthorized actor accessed the company's servers, compromising personally identifiable information of employees, including names, Social Security numbers, and in some cases, driver's license or passport numbers. The company secured its network, launched an investigation, and offered credit monitoring services to those affected.
Signal context
First seen: Sep 5, 2025
Last updated: Jun 25, 2026
Status: Public signal
Key points
- Affected individuals: Employees.
- Data exposed: Names, Social Security numbers, and in limited cases, driver's license or passport numbers.
- Cause: Ransomware attack by INC ransomware group.
Signal analysis
BetaIt helps compare this signal with other published signals without treating the labels as final determinations.
Likely country: Location not provided
The feed marks multiple actor roles. Treat this as a review signal rather than a final attribution.
- Source type: outside the affected organization
- Source type: possible insider or internal misuse
Impact area: Confidentiality, Availability
Likely asset: User or customer data
- 1 signal in the same sector
- 100 signals with the same likely impact area
- 1 signal linked to this organization/domain
External sources
Related signals
Grouped by why the signal is relevant.
eogb.co.uk Hit by Stormous Ransomware Group
eogb.co.uk, a UK-based organization, was claimed as a victim by the Stormous ransomware group. The incident was discovered on June 28, 2026, at 21:29 UTC, with deep access to Microsoft Dynamics GP, internal legal documents, partnership agreements, customer contracts, operational spreadsheets, financial reports, and executive documents.
Alamo Heights ISD Reports Data Breach Following Ransomware Attack
Alamo Heights Independent School District (ISD) reported a data breach impacting over 26,000 people, disclosed to the Texas Attorney General's office on June 25, 2026 (published June 26, 2026 UTC). The breach was linked to a ransomware attack by the Qilin group, which occurred on April 9, 2026. The compromised information included names, Social Security numbers, driver's license numbers, and bank and medical information.
Challenge Manufacturing Data Breach Exposes Social Security Numbers
Challenge Manufacturing, an automotive manufacturing company, disclosed a data breach to the Texas Attorney General on June 26, 2026. The Chaos ransomware group claimed responsibility on May 17, 2026, stating they obtained 270 GB of data from the company's systems.
Vienna Airport Targeted in APT73/Bashe Ransomware Attack
The ransomware group APT73/Bashe claimed responsibility for a cyberattack against Vienna Airport (Flughafen Wien AG) on June 23, 2026, threatening to leak sensitive data. The airport acknowledged a limited leakage of old cargo-related files from one email inbox but denied a broader system compromise.
AYA BANK Hit by Lapsus$ Ransomware Attack
AYA BANK, a prominent financial institution in Myanmar, fell victim to a ransomware attack by the Lapsus$ group, discovered on June 23, 2026. Lapsus$ claimed to have stolen over 120 gigabytes of data, including a full dump and PII, and threatened to sell it if a ransom was not paid. AYA Bank acknowledged a breach of an older application portal exposing some customer information but stated its core financial networks remained secure.
McKay Sugar Cyber Incident by Gentlemen Ransomware Group
McKay Sugar, a major Australian sugar producer, suffered a cyber incident that disrupted operations at its Farley and Racecourse Mills. The Gentlemen ransomware group claimed responsibility for the attack around June 15-16, 2026, on their leak site. Public reporting indicated that McKay Sugar was working to verify what data was stolen or accessed. The ransomware group claimed to have stolen over 26 million records containing PII of customers and other internal data. The incident was discussed in public reporting around June 21, 2026.
