Mango Recall Expanded to Include Additional Brands and UPC Codes
Panorama Produce expands its Salmonella-related mango recall; consumers urged to check for specific PLU and UPC codes.
3 reports on this incident · first at Aug 30, 2026, 10:00 p.m. ET
Earlier reports
Aug 30, 2026, 10:06 p.m. ET
FDA Reports Illnesses in Salmonella-Linked Mango Recall
The U.S. Food and Drug Administration (FDA) has now received reports of illnesses linked to the recall of mangoes distributed by Panorama Produce, according to a report from Food Safety News. The agency had previously stated that no illnesses had been reported.
The recall, announced on August 30, 2026, involves 302 boxes of mangoes sold under the brand names Martina and Agrofepac, distributed in Connecticut, New York, New Jersey, and Pennsylvania. The mangoes may be contaminated with Salmonella, the FDA said. Consumers can identify the affected mangoes by the PLU number 4584 and UPC # 07503061948050.
The FDA advises consumers to dispose of the mangoes or return them to the place of purchase. The agency has not specified the number of illnesses reported.
Aug 30, 2026, 10:00 p.m. ETFirst report
Mangoes Sold at Walmart Recalled Due to Salmonella Risk
Panorama Produce has recalled 302 boxes of mangoes sold under the Martina and Agrofepac brands because they may be contaminated with Salmonella, according to a report from Food Safety News. The recall was reported on August 30, 2026, and covers mangoes distributed in Connecticut, New York, New Jersey, and Pennsylvania.
The affected mangoes carry a PLU number of 4584 and UPC # 07503061948050. Consumers who have these mangoes should dispose of them or return them to the place of purchase, the report said. No illnesses have been reported to date.
The recall was initiated by the FDA, according to Food Safety News.
Was this report accurate and useful?
Sources
- Mangoes sold at Walmart recalled because of Salmonella riskfoodsafetynews.com
Revision history
- Version 131 Aug 2026, 02:11current
First published.
- Version 131 Aug 2026, 02:00current
First published.
- Version 131 Aug 2026, 02:06current
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.