DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed10 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedinc_ransomhigh sensitivity
Merged incident · 10 filings

Monterey Mushrooms, Inc. — August 2025 breach

Clustered 10 filings across 8 jurisdictions · filing window Aug 7, 2025 → Sep 19, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

7

Affected · reported

9,717

First → last filing

Aug 7, 2025 → Sep 19, 2025

Merge confidence

100%

incident inc_32718eabf084483c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 3 unverified claims. The filings describe unauthorized access. Intrusion Aug 2, 2025–Aug 7, 2025, discovered Aug 30, 2025 — the first regulatory filing landed 2 days later. 9,717 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 43-day schedule across 7 filings beginning Aug 7, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
2days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
25days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
43days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 2, 2025breach begins
Aug 30, 2025discovered
notification delay · 2 days
Sep 1, 2025first filing
Sep 19, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. AUG 7Leak siteinc_ransom postfirst filing · attacker claim · unverifiedday 0
  2. AUG 8Leak sitepayoutsking postattacker claim · unverified+1d
  3. SEP 1IL AGIL AG noticeno count stated+25d
  4. SEP 4Leak siteinc_ransom postattacker claim · unverified+29d
  5. SEP 18CA AGCA AG noticeno count stated+42d
  6. SEP 18ME AGME AG notice1 ME residents+42d
  7. SEP 18MA AGMA AG notice1 MA residents+42d
  8. SEP 18NH AGNH AG notice1 NH residents+42d
  9. SEP 18IN AGIN AG notice10 IN residents+42d
  10. SEP 19TX AGTX AG noticemost recent · states nationwide total 9,717+43d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 2, 2025 – Aug 7, 2025
CA AG
Discovered
Aug 30, 2025· 28d undetected
IL AG + ME AG + TX AG
Data types
Identity (basic) · Government ID
IL AG + CA AG + ME AG +3
Attack vector
Unauthorized Access
ME 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)

9,717

Sum of filed state slices

2,324· 23.9% of stated

76% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US9,717
TX2,311
IN10
ME1
MA1
NH1

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim3 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing7 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 2026 · at least one link edge was human-adjudicated
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

43 days

Cadence

~1 / 4.8d

vs. multi-state median

5.4× 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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.