When to Toss Contaminated Mushroom Substrate

The Save-or-Toss Decision Framework

Every contamination event comes down to three variables: what type of contamination you're dealing with, what stage your grow is at, and how far the contamination has spread. These three factors together determine whether you have any realistic chance of salvaging your grow or whether you're wasting time fighting an inevitable loss. Understanding this framework saves you from both throwing away perfectly saveable grows and from stubbornly holding on to lost causes.

When Saving Is Possible

Not all contamination is a death sentence. Cobweb mould (Dactylomyces) caught early can often be treated with a direct spray of 3% hydrogen peroxide — the cobweb dies on contact while healthy mycelium tolerates it well. Small bacterial wet spots on the surface of a fully colonized substrate can sometimes be isolated by the surrounding mycelium, especially on aggressive species like oyster mushrooms. The key is catching it early: a single spot smaller than a coin on an otherwise healthy, fully colonized block has a reasonable chance of being contained by the mycelium's own defences.

When You Must Toss — No Exceptions

Green mould (Trichoderma) on anything less than fully colonized substrate is terminal. Trichoderma grows faster than mushroom mycelium and releases enzymes that actively digest it — once it gets a foothold on uncolonized grain or substrate, the battle is already lost. Black mould (Aspergillus niger) should always be discarded and handled with respiratory protection, as its spores pose real health risks. Any contamination that covers more than about 20% of the surface area, regardless of type, has released enough spores and metabolites to compromise the rest of the block even if it looks clean.

The Salt Method for Small Trichoderma Spots

For tiny green spots on a fully colonized block (smaller than a fingernail), some growers have success with the salt method: pour a thick layer of non-iodized salt directly over the contaminated spot, covering it completely and extending about an inch beyond the edges. The salt creates an environment too hostile for Trichoderma while the underlying mycelium, protected by its colonized substrate, can tolerate it. This is a last-resort technique, not a reliable cure — but on a fully colonized block that you'd otherwise toss, it's worth attempting.

Harvesting Through Contamination on Fully Colonized Blocks

A fully colonized block that develops contamination after pinning presents a unique situation. If the mushroom pins are healthy and growing on a part of the block away from the contamination, you can often harvest that flush safely. The fruit bodies themselves are not contaminated just because the block is — mushrooms grow rapidly and pull nutrients from healthy mycelium. However, do not consume fruit bodies growing directly adjacent to or on top of contaminated areas, and do not expect a second flush from a contaminated block.

Safe Disposal and Grow Space Cleanup

Never open contaminated bags or containers indoors. Each contaminated block contains billions of spores that will become airborne the moment you break the seal. Seal contaminated items in a plastic bag, take them outside, and dispose of them in the compost or garbage. After removing contaminated grows from your space, wipe down all surfaces with a 10% bleach solution or 70% isopropyl alcohol. Clean or replace HEPA filters if you use them. Allow the space to air out completely before introducing new grows.

Preventing the Next Batch From Failing

Contamination is almost always a process failure, not bad luck. After dealing with a contamination event, audit your entire workflow before starting your next batch. Check your pressure cooker's gauge calibration, verify your still air box or flow hood is actually providing clean air, test your grain hydration level, and examine your spawn source. The most common cause of repeated contamination is inadequate sterilization time — if you're losing batches regularly, add 15-20 minutes to your pressure cooking time and see if the problem resolves.