FDA Reports Ongoing Class I Recall of Clover Hill Dairy Sharp Cheese Snack Packs

Refrigerated sharp cheese sticks distributed in MD, VA, and NY are subject to an ongoing Class I recall due to Listeria monocytogenes contamination.

By AI ReporterWritten Aug 18, 2026, 10:56 a.m. ET

Developing · checked 12h ago

This recall is open. The agency updates its record as an action is expanded, reclassified or terminated, and this page is rewritten when it does.

We last searched for new coverage of this at Aug 18, 2026, 1:07 a.m. ET — checked 12h ago.

On August 12, 2026, an FDA enforcement report documented an recall initiated on June 1, 2026, by for its Sharp Cheese Snack Pack Sharp Stix White or Yellow. The recall, listed under recall number , was issued because the product was contaminated with Listeria monocytogenes. The item was distributed in Maryland, Virginia, and New York. According to the FDA enforcement record, the affected product carries identifying code AA051526 and is sold in approximate 0.40-lb (6.4oz) units that require refrigeration. The total quantity distributed, packaging, and labeling details remain unknown. A classification is defined by the FDA as a situation involving a reasonable probability that using or exposure to the product will cause serious adverse health consequences or death. According to the FDA, Listeria monocytogenes can cause serious and sometimes fatal infections in young children, frail or elderly people, and others with weakened immune systems, and infection in pregnant women can cause miscarriage and stillbirth. Registry and standard-of-identity records list cheddar cheese as a product made by coagulating milk, with "sharp" denoting longer aging and color differences resulting from added annatto or natural milk appearance. FDA database records show 17 other recall actions involving , including August 12, 2026 recalls for mild cheese and Pepper Jack varieties contaminated with Listeria monocytogenes. Agency records also show 569 food recalls citing Listeria monocytogenes in the last two years; these historical records do not establish fault or cause for the current recall.

Was this report accurate and useful?

Sources

Revision history

Version 118 Aug 2026, 14:56current
First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.