FDA Closes Recall of Sirna & Sons Jalapeño Peppers Over Salmonella Risk
The FDA has closed the recall of jalapeño peppers distributed by Sirna and Sons Produce, Inc., after the firm carried out the recall.
2 reports on this incident · first at Sep 9, 2026, 8:17 p.m. ET
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 Sep 9, 2026, 10:10 p.m. ET — checked 12 min ago.
Earlier reports
Sep 9, 2026, 8:17 p.m. ETFirst report
Sirna and Sons Produce Recalls Jalapeño Peppers Over Salmonella Risk
Sirna and Sons Produce, Inc., of Ravenna, Ohio, recalled 249 one-pound bags of jalapeño peppers distributed for food service use in Ohio and Pennsylvania, according to an FDA enforcement report dated September 2, 2026. The recall, initiated August 5, 2026, covers the following identifying codes: Lot Numbers: 60947409, 60991812; Pack Dates: 07/13/26, 07/23/26; Internal Product Number: 00184. These are codes, not calendar dates. The product is described as "Sirna & Sons Produce PEPPER JALAPENO BREAK 1LB," repackaged into 1 lb. plastic bags with product number 55255.
The FDA classified the recall as Class I, its most serious category, used when there is a reasonable probability that using the product will cause serious harm or death. The reason cited is potential Salmonella Javiana contamination. The recall is ongoing, and the FDA notes that Salmonella can cause diarrhoea, fever, and abdominal cramps, with severe cases sometimes requiring hospitalization, particularly in young children, older adults, and people with weakened immune systems.
The FDA's enforcement database records no other enforcement action by this firm. The total volume is approximately 249 pounds, calculated from the unit count and pack size.
Was this report accurate and useful?
Sources
Revision history
- Version 110 Sept 2026, 00:17current
First published.
- Version 110 Sept 2026, 00:23current
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.