On Friday, October 23, 2026, the USDA’s Food Safety and Inspection Service confirmed that Trader Joe’s Tarragon Chicken Salad Wraps are the source of the E. coli O157:H7 outbreak that has sickened at least 50 people. FSIS did not say it in a press release, a recall notice, a public health alert or an update to its own outbreak page, because it does not have one. It said it in an email to USA TODAY, after USA TODAY reported on our lawsuit and on state investigation records the paper had reviewed. USA TODAY is public health’s new press office. Tip of the pen to Mary Walrath-Holdridge and the editors who kept asking.

USA TODAY also got something the public had never been told. Trader Joe’s said in an October 20 email to the paper that it pulled the wraps from shelves in nine states after the FDA notified the company in September of a “possible issue.” So, Trader Joe’s knew in September. The FDA knew in September. FSIS, the agency with jurisdiction over a product made with chicken, knew. The people who bought and ate the wraps found out a month later, and only because a lawyer filed a complaint and a reporter asked a question.

The timeline

Late August. Gayle Gottlieb of Pembroke, North Carolina, buys three Tarragon Chicken Salad Wraps at the Trader Joe’s in Myrtle Beach on August 23, eats the first on August 27 and is in the emergency department by August 30. Meaghan Egan Bright of Somerville, Massachusetts, buys one at the Trader Joe’s in Allston on August 24, falls ill on August 27 and is hospitalized at Massachusetts General from August 31 through September 6.

September. The FDA tells Trader Joe’s there may be a “possible issue” with the wraps, and Trader Joe’s pulls them in nine states. Massachusetts records describe a call with federal partners, the pull, a halt in production, a commonly identified contract manufacturer, and a focused questionnaire built around Trader Joe’s wraps and sandwiches that went to every state.

September 23. The FDA opens reference 1421 (USDA-FSIS 2026-04) on its table of active outbreak investigations with 25 sick. The vehicle: “Multi-ingredient wrap with chicken (suspect).” No brand, no retailer, no manufacturer, no states, no recall.

October 15. The count reaches 50. Marler Clark files Gottlieb and Bright v. Trader Joe’s Company, No. 2:26-cv-12017, in the Central District of California. The name enters the public record for the first time, in a court filing, not a government notice.

October 15 to 22. The name spreads through local and trade press, including Patch, WPDE, Hoodline, Yahoo and Quality Assurance & Food Safety. The FDA’s table does not change.

October 23. FSIS confirms the link to USA TODAY.

What the timeline tells us

Nothing about the science changed between September 23 and October 23. The traceback was done. The product was pulled. Production was halted. A questionnaire built around Trader Joe’s products was in the hands of every state health department. What changed is that a lawsuit put the name in a public court file and a national newspaper asked a direct question. Faced with that, FSIS confirmed it in one email. Naming the product cost the government nothing on October 23. It would have cost nothing on September 23.

The harder question is what happens in the outbreak with no lawsuit, no receipt and no reporter. We saw the answer this week: on October 21, the FDA closed a 119-person Salmonella Newport outbreak without ever naming a food. That is the default, and the Trader Joe’s wraps were headed for the same ending.

What still has not been said

FSIS’s email answered one question. It left the rest. Who made the wraps? Based on what I have learned in this case, I believe it was F&S Fresh Foods of Vineland, New Jersey; neither agency has said a word about F&S. Which nine states? How many people were hospitalized, and how many developed hemolytic uremic syndrome? Which ingredient is under investigation, and did it go into other products made for other retailers? The CDC still has not posted an investigation notice, and FSIS still has no 2026-04 page of its own.

This is the argument for the outbreak firm disclosure petition

The outbreak firm disclosure petition I have circulated in draft asks the FDA to treat the identity of a firm implicated in an outbreak as information the public is entitled to, not a confidential business secret. Until a rule is final, it asks the agency to use the authority it already has under section 705(b) of the Food, Drug, and Cosmetic Act to name firms now, to publish case counts, states, onset dates, hospitalizations and HUS cases for open investigations, and to name the suspect food – and, for a multi-ingredient product like a wrap, the ingredient under investigation – once traceback begins.

Public health information should not depend on whether a newspaper has the staff to chase it. If you want a copy of the draft, email me. Comments are welcome through Friday, October 30, before I file.

What should happen now

FSIS and the FDA should put on their own websites what FSIS told USA TODAY in an email, and then finish the job: name the manufacturer, publish the states, the hospitalizations and the HUS count, and say whether the suspect ingredient went anywhere else. The CDC should post an investigation notice. Trader Joe’s should tell its customers who made the Tarragon Chicken Salad Wraps and which stores sold them. In 2013, when Glass Onion Catering’s chicken salads and wraps sickened 33 people who shopped at Trader Joe’s and elsewhere, the agencies named the maker and the products within days. Thirteen years later, it took a reporter.

Petting zoos and E. coli. Here we go again. But instead of just reporting the case count, let’s walk through what we actually know, what we don’t, and the questions that public health officials – and parents – should be asking, using the playbook that has existed for two decades.

What We Know

On Friday, October 23, the Will County Health Department announced it is investigating five laboratory-confirmed cases of Shiga toxin-producing E. coli (STEC) that may be connected to visits to Bengtson’s Pumpkin Farm, 13341 W. 151st St. in Homer Glen, Illinois. The department says it is working to determine how the infections occurred and whether there is a common source.

According to owner Scott Bengtson, the health department first contacted the farm on Wednesday, October 21. The farm voluntarily closed its petting zoo and is arranging for animal testing; the rest of the farm remains open. In its statement, the farm said health officials inspected its food service areas and food vendors on October 21 and found no problems, and that a veterinarian will collect samples from the animals. ABC7 Chicago reports that health department personnel will be at the petting zoo Monday to collect samples.

Health officials believe the exposures occurred on or after September 29 and are asking anyone who became ill after visiting the farm since then to fill out a confidential online survey. Anyone who develops symptoms – especially bloody diarrhea or severe stomach cramps – should contact a healthcare provider, and signs of dehydration, decreased urination or unusual tiredness require immediate medical attention.

The farm has described its precautions. It says the petting zoo has staff on-site at all times, handwashing stations at the entrance and exit, and pens that are cleaned daily. Speaking to ABC7, Bengtson emphasized hand sanitizers and signage about the importance of handwashing.

Sean Conners, the department’s Director of Environmental Health, has been careful not to prejudge the source: animals can carry E. coli even when they appear healthy, but animal contact is not the only route – E. coli can also spread through contaminated food, water or surfaces. He also noted that this strain is especially hard on young children.

Kudos to Bengtson’s for closing the petting zoo and cooperating. I wrote about the initial announcement here.

What We Do Not Know

  • Who is sick. No ages, hospitalizations or cases of hemolytic uremic syndrome (HUS) have been released.
  • What is making them sick. We do not know whether this is E. coli O157:H7 or a non-O157 STEC, or whether whole genome sequencing shows the five cases are genetically linked to each other.
  • What the sick people did at the farm. Did all five visit the petting zoo? Did they feed animals, eat at the farm, attend the pig races, or visit on the same days?
  • Which animals. We do not know what species are in the petting zoo, how old they are, whether the farm owns them or leases them from an exhibitor, or where else they have been.
  • What “handwashing stations” means. Soap, running water and paper towels at child height – or sanitizer dispensers? The farm’s written statement and the owner’s interview leave that open.
  • The water source. Municipal water or a well, and whether hoses or water lines near the animals are connected to anything the public uses.
  • How big this gets. The survey just launched, STEC symptoms can begin one to ten days after exposure, and secondary (person-to-person) cases are common in households with small children. Five is a starting number, not a final one.
  • The sampling results. Animal and environmental results will likely take a week or more, and – as discussed below – a negative animal test does not end the inquiry.

The Questions to Ask – Straight from the Compendium

Since 2005, the National Association of State Public Health Veterinarians (NASPHV), with CDC, has published the Compendium of Measures to Prevent Disease Associated with Animals in Public Settings. The current 2023 edition appeared in the Journal of the American Veterinary Medical Association (also available from CDC Stacks). It applies by name to agritourism venues, farms open to the public and petting zoos. It also says it plainly: there is no federal law addressing these risks, and some states regulate practices like handwashing stations. That makes the Compendium the standard of care investigators will measure Bengtson’s against.

Here is what they should be asking, section by section:

1. Handwashing (Compendium §§ III.A.3.a, IV.D.2.a(2), Appendix 3)

  • Was there soap and running water at the petting zoo exit, or only sanitizer? The Compendium says soap and water is preferred because sanitizers do not work equally well on all pathogens or on heavily soiled hands.
  • Were the stations accessible to small children and people with disabilities? In a British Columbia pumpkin patch outbreak the Compendium cites, there was no running water, and the sanitizer was mounted too high for some children to reach.
  • Was a staff member stationed at the exit to remind visitors to wash? The Compendium cites studies showing staff presence and verbal reminders improve compliance.
  • Were paper towels provided? Drying hands on clothing increased the risk of illness in outbreak studies.
  • Were there handwashing stations and signs where food was sold and eaten?

2. Education and Signage (§ IV.D.1)

  • Were visitors warned before entering that animals can carry pathogens that cause serious illness – and told who is at highest risk, including children under five?
  • Did signs tell visitors not to eat, drink, or use bottles or pacifiers in the animal area? Were they in plain language, multiple formats and languages?
  • Did school or daycare groups visit, and were the organizers given prevention information before the trip?

3. Layout and Traffic Flow (§ IV.D.2.a)

  • Was the farm divided into animal areas, transition areas and non-animal areas, as the Compendium recommends?
  • Was there one-way flow with a separate entrance and exit, and was crowding controlled?
  • Were food, drinks, strollers, toys, pacifiers and sippy cups kept out of the petting zoo, with stroller parking outside?
  • Were children kept from sitting or playing on the ground? Were there double barriers?
  • How far is the petting zoo from food service, the pig races and play areas – and was manure or bedding ever carried through areas where visitors walk?

4. Animal Feeding (§ IV.D.2.a(1))

  • Online reviews mention buying carrots to feed the goats. How was feed sold and handed out? The Compendium says the public should feed animals only where contact is controlled, such as by barriers, and never from containers people might eat. It also notes that people who fed animals and did not wash before eating were more likely to become ill.

5. Manure, Cleaning and Pests (§ IV.D.2.a–b)

  • How quickly was manure removed, where was it stored, and were waste tools kept away from the public?
  • What disinfectant was used on railings and surfaces, and for how long? Most compounds need more than ten minutes of contact time, after organic matter is cleaned off.
  • Did the farm have a fly and pest control program? The Compendium notes house flies can carry pathogens to surfaces.

6. Water and Unpasteurized Products (§ IV.D.2.c–d)

  • Was the drinking water inspected? Were backflow devices installed between livestock water outlets and other lines? Were hoses left on the ground or unlabeled?
  • Was any unpasteurized cider, juice or dairy sold? The Compendium says it should not be.

7. The Animals (§ IV.D.3; § III.A.1.a)

  • What species and ages? Young animals shed STEC at higher rates than mature animals, and transport, crowding and commingling increase shedding.
  • Did the farm retain a licensed veterinarian? Were animals checked daily, and were any from herds with recent diarrhea?
  • Are the animals owned or contracted? Are there USDA Animal Welfare Act licenses and current Certificates of Veterinary Inspection? Do records show where the animals came from and where else they have been exhibited?

8. The Investigation Itself (§ IV.C.2)

  • Will samples from people, animals and the environment be tested and sequenced? The Compendium calls for exactly that kind of One Health investigation, with reporting to CDC’s National Outbreak Reporting System.
  • Will they sample fences, bedding, hay and soil – not just animal feces? STEC can survive in soil for months, and outbreaks have followed exposure to environments after the animals were gone.
  • How will negative animal results be read? The Compendium warns that shedding is intermittent, so a negative test does not mean an animal was not shedding earlier.

This Should Not Keep Happening

Pumpkin patches and petting zoos have a long history together: Willow Grove Gardens in Longview, Washington in 2012; Dehn’s Pumpkins in Dayton, Minnesota in 2013; and the fair outbreaks in North Carolina, Florida and Arizona in 2004–2005 and Cleveland County, North Carolina in 2012, which killed a two-year-old boy. Marler Clark tracks these outbreaks at Fair-Safety.com, including a running list of outbreaks linked to fairs and petting zoos. Tips for families are here, and guidance for owners and operators is here.

Prevention is not complicated, and it is not new. The Compendium has laid it out for twenty years. The question in Homer Glen – as always – is whether it was followed.

We will be watching for the animal and environmental test results and whether the case count grows.

The FDA updated its CORE Investigations of Foodborne Illness Outbreaks table on October 21, 2026. The CDC updated its Current Outbreaks page the same day. Here is where things stand.

What’s new at FDA this week

For the Listeria monocytogenes outbreak (ref #1417), FDA has now initiated an on-site inspection and sampling. Forty-six people are sick. The food has not been identified.

For the Salmonella Newport outbreak (ref #1403), the case count rose from 116 to 119 and the outbreak has been declared over. No food has been identified.

For the Cyclospora outbreak (ref #1392), the case count was adjusted from 240 to 241. No food has been identified.

For the Listeria monocytogenes outbreak (ref #1379), the outbreak has ended with 11 sick. No food has been identified.

Six outbreaks are still ongoing

Listeria monocytogenes (ref #1415), posted September 30: 11 sick, food not yet identified. Traceback, inspection and sampling have all been initiated.

E. coli O26:H11 (ref #1419), posted September 25: raw milk cheese. See the FDA advisory for the case count and recall information. Traceback, inspection and sampling initiated.

E. coli O157:H7 (ref #1421, USDA 2026-04), posted September 23: “multi-ingredient wrap with chicken (suspect).” Fifty sick. Traceback, inspection and sampling initiated. Still no recall, no brand, no manufacturer, no states, and no hospitalization or HUS numbers.

Listeria monocytogenes (ref #1417), posted September 23: 46 sick, food not yet identified. Traceback, inspection and sampling initiated.

Salmonella Bovismorbificans (ref #1411), posted September 10: sprouts. See the FDA advisory. Traceback and sampling initiated.

E. coli (multiple strains) and Salmonella Agona (ref #1394), posted August 19: alfalfa sprouts. See the FDA advisory. Traceback, inspection and sampling initiated.

Nine outbreaks are over, but the investigations remain open

Salmonella Newport (ref #1403): 119 sick, food not identified. Salmonella I 4,[5],12:i:- (ref #1402): 43 sick, food not identified. Cyclospora (ref #1398): 22 sick, food not identified. Cyclospora (ref #1392): 241 sick, food not identified. Salmonella Javiana (ref #1395): jalapeño peppers, see the FDA advisory. Listeria monocytogenes (ref #1379): 11 sick, food not identified. Cyclospora (ref #1390): iceberg lettuce, see the FDA advisory. Cyclospora (ref #1385): 38 sick, food not identified. Salmonella Oranienburg (ref #1387): 99 sick, food not identified.

The scorecard

Of the 15 investigations on FDA’s active list, a food has been linked in six – and one of those, the chicken wrap, is still only “suspect” – but, we know better. In the other nine, no food has been named. Those nine outbreaks alone account for 630 sick people.

Cyclospora stands out. Three of this summer’s Cyclospora outbreaks – 22, 38 and 241 sick, 301 people in all – have ended with no food identified, on top of the outbreak linked to Taylor Farms iceberg lettuce.

And there are two sprout outbreaks on the table at the same time, plus another raw milk cheese outbreak. None of this should surprise anyone. It is exactly why I have been pushing FDA for warning labels on raw sprouts and raw milk cheese.

CDC: 29 active multistate investigations

As of October 21, CDC reports 29 active multistate investigations: 18 Salmonella, 7 Shiga toxin-producing E. coli, 3 Listeria and 1 Campylobacter. CDC notes that it typically coordinates between 17 and 40 of these each week – and that not every investigation results in a public outbreak notice. Most do not. CDC’s count also does not include Cyclospora, which FDA tracks on its own table.

FSIS: one active outbreak, and no name

The FSIS outbreak table lists one active investigation: 2026-04, the E. coli O157:H7 outbreak tied to a “Ready-To-Eat Multi-ingredient wrap with chicken (suspect)” – the same outbreak as FDA #1421. FSIS’s entry says the wrap is past shelf-life and no longer for sale, and that FSIS is working with FDA to identify the contaminated ingredient and whether it was used in other products. There is no recall, no public health alert, no establishment name and no establishment number – and, we know better.

Compare that with FSIS’s other 2026 outbreaks, all now closed. For the E. coli O157:H7 outbreak linked to beef kofta (2026-02), FSIS issued a public health alert naming The Kebab Shop restaurant locations. For the Listeria outbreak linked to retail-sliced headcheese (2026-01), FSIS issued a public health alert for the headcheese deli meat products. For the Salmonella Enteritidis outbreak tied to chicken (suspect) at the Broome County Correctional Facility (2026-03), the table points to the local sheriff’s and health department’s update.

So, FSIS knows how to name names. FSIS says it posts outbreak data “prior to a specific product being identified” in the name of transparency. But 50 people are sick from a product containing chicken, and if you want to know more, FSIS’s own FAQ tells you to file a FOIA request.

Why names matter

FDA’s table says the agency will not publicly name a specific product “until there is sufficient evidence.” In practice, that means the firms involved in unsolved outbreaks are never named at all, and the companies, retailers and consumers downstream are left guessing.

That is why I have drafted citizen petitions asking FDA to stop treating the identity of outbreak-implicated firms as confidential and to publish retail consignee lists in Class I recalls. I am still taking comments before I file. If you would like a copy, email me – I’d like to hear from you before October 30.

Fifty people have been sickened with E. coli O157:H7 in a multistate outbreak that FDA and USDA’s Food Safety and Inspection Service are investigating together as reference #1421 (USDA 2026-04). The government knows the product. It knows the retailer. It knows who made it. Federal investigators have been inside the supply chain. Receipts have been collected. Genetic sequencing ties the sick together.

And the public investigation table still reads, in its entirety: “Multi-ingredient wrap with chicken (suspect).”

No brand. No retailer. No manufacturer. No states. No hospitalization count. No ingredient. No recall, no advisory, no public health alert. The public learned these were Trader Joe’s Tarragon Chicken Salad Wraps from a federal lawsuit my firm filed on October 15, Gottlieb v. Trader Joe’s Co., not from either agency charged with protecting us. 

Based on what I have learned in this case, the wraps were made for Trader Joe’s by F&S Fresh Foods of Vineland, New Jersey. F&S’s quality staff reached out directly to one of my clients. Neither FDA nor FSIS has said a word about F&S. Neither agency has said whether the contaminated ingredient went into other products F&S makes for other retailers.

Let me be blunt. The public’s right to know who made fifty people sick should not be left up to a lawyer on an island off the coast of Seattle filing a lawsuit. That is the government’s job.

The stated reason: the wraps were “proactively removed from the market” and are past shelf life (assuming none were frozen). Because the removal was never called a recall, it was never classified. Because it was never classified, no list of stores was ever published. A disclosure rule that attaches only to the word “recall” can be avoided simply by not using the word.

This is simply wrong. And it is not new.

The government has named names before – when it wanted to

FDA’s position is that the name of a company linked to an outbreak is confidential commercial information unless a recall attaches to it. Its own history says otherwise. In at least eight investigations since 2006, FDA, CDC or a partner agency named the farm, the processor or the brand after the product was already out of commerce or past shelf life:

In 2006, after the Dole spinach outbreak sickened at least 205 and killed at least three, the government named the processor, the ranch, the farming company, the growers of other fields and even the fertilizer maker, six months after the recall. In 2013 it named Taylor Farms de Mexico in a Cyclospora outbreak after the salad mix was likely gone. In April 2018 FDA named Harrison Farms of Yuma when the romaine was past its 21-day shelf life, and the field was in grass. In July 2018 it named Fresh Express when the package dates had passed. In December 2018 it named Adam Bros. Farming, which had not shipped romaine in weeks. In 2021 it named Josie’s Organics spinach and Simple Truth and Nature’s Basket salads after their best-by dates. In 2022 it named FreshKampo and HEB strawberries while saying they were past shelf life.

And here is the one that should sting most. In 2013, 33 people were sickened by E. coli O157:H7 in chicken salads made by Glass Onion Catering and sold at Trader Joe’s. CDC named both companies. FSIS published a recall listing the Trader Joe’s products by name. Same retailer. Same kind of product. Same pathogen. Same agencies. Thirteen years later: silence.

FSIS still names when it wants to. In May 2026 it issued a public health alert naming The Kebab Shop restaurants and the producer of beef kofta that had been made four months earlier and was no longer available. That is FSIS’s routine: when product is gone, issue an alert and name the establishment. In the chicken wrap investigation, it has issued nothing.

Meanwhile, silence has become the default on the produce side. In fall 2024, a romaine E. coli outbreak (#1280) sickened 89, hospitalized 36, put seven into kidney failure and killed one. FDA closed it with one word: romaine. The traceback documents, when finally released, showed it converged on a single processor and a single grower. The public got those names more than a year later, through records requests. In September 2026 FDA closed another romaine outbreak (#1382), 14 sick, past shelf life, no recall, no name. Yet the same year, in a Salmonella cantaloupe outbreak (#1366), FDA named the importer and two Guatemalan growers. The difference was not shelf life. It was whether a recall happened to attach.

When the decision whether to tell the public depends on the mood of the day and not a written rule, no one can predict it, no one can review it, and the public loses.

Two petitions to fix it

I have prepared two companion citizen petitions to FDA. They are not yet filed. I want more eyes and fingers on them first.

Petition One: Outbreak Firm Disclosure. This petition asks FDA to establish, by notice-and-comment rule, that the name and location of a firm implicated in a foodborne illness outbreak is not confidential commercial information when epidemiology implicates the food and traceback or lab evidence, including whole genome sequencing, points to the firm. In the same rule, it asks FDA to make a firm’s identity and distribution information disclosable whenever an outbreak food is pulled from commerce, whether the company calls it a recall, a market withdrawal, a stock recovery or a “proactive removal,” and whether it is past shelf life. It asks that the rule put the burden on a firm seeking secrecy to prove a real trade secret, in writing and on the record, while giving a firm one business day to correct factual errors and requiring a prominent public correction if a named firm is later cleared. It reaches the whole supply chain – grower, harvester, cooler, processor, manufacturer, distributor, importer and retailer – because lettuce in a restaurant salad has no brand on it. Until the rule is final, it asks FDA to use the authority it already has under section 705(b) of the Food, Drug, and Cosmetic Act to name firms now. It asks FDA to publish case counts, states, onset dates, hospitalizations and HUS cases for open investigations, and to name the suspect food – and, for a multi-ingredient product like a wrap, the ingredient under investigation – once traceback begins. And at closure, it asks FDA to say whether traceback converged and on whom, and to publish its outbreak summaries without redacting the names.

Petition Two: Recall Consignee Lists and Classification. Since a 2008 rule, USDA has published the names and locations of stores that received meat and poultry in Class I recalls. If you bought recalled ground beef, you could find out whether your store got it. If you bought recalled cheese, sprouts, cantaloupe or bagged salad, you usually cannot. Congress told FDA in 2011 to consider following USDA. FDA wrote guidance that binds no one and applies mainly to foods you cannot identify from the package. This petition asks FDA to require, by rule, publication of retail consignee lists in every Class I food recall, at the time of the announcement and updated as stores are identified; to extend those lists to restaurants, caterers, schools, hospitals, nursing homes and prisons; to classify every recall within ten days and publish the date; and to connect each recall record to the outbreak it is tied to. Critically, it asks FDA to confirm that pulling a food identified as the suspected vehicle of an outbreak is a recall under FDA’s own regulations, no matter what the company calls it. That closes the exact door Trader Joe’s wraps walked through.

States are already doing this. California named the forty-one San Diego County stores that received Happy Hens eggs this year. Washington named an implicated creamery and its cheeses during an open investigation. Federal silence protects no one. It just leaves a record that is incomplete and useless to a national buyer.

There is a pending petition from Stop Foodborne Illness on the same core question, and I support it. FDA’s July interim response said only that the issues were “complex.” The Senate has passed S. 4974, which would authorize disclosure but would not require it or say when. These petitions supply the written standard either way.

Why this matters to everyone, including industry

When the government names a commodity and stops, consumers avoid the whole commodity. Every grower and processor who did nothing wrong pays for the one who did. A firm-specific disclosure is the only thing that separates them. Disclosure is not punishment; it is prevention. It lets a buyer weigh a supplier’s history, an insurer price it, a doctor ask the right question, and a company find its problem before the next season. Withhold the name, and every outbreak looks like the first one anyone has ever had.

Read them. Tell me what you think.

I want comments from public health officials, the produce and retail industry, consumer advocates, lawyers, academics and anyone who has ever been sick and wanted to know why. If you would like to review either or both petitions before they are filed, email me at bmarler@marlerclark.com and ask for the petitions. I will send them to you. Please get your comments back to me before October 30, 2026, so I can incorporate them before filing.

Fifty people are sick. The government knows who made the wraps. The only people kept in the dark are the rest of us, unless a lawyer on Bainbridge Island happens to file suit. That is no way to run a food safety system. Let’s fix it.

Fifty people are sick with E. coli O157:H7 in an outbreak that the FDA and USDA’s Food Safety and Inspection Service (FSIS) are investigating together as FDA reference #1421 (USDA 2026-04). The government’s public investigation table lists the vehicle as a “Multi-ingredient wrap with chicken (suspect).” Status: active. Ongoing. Under “Recall,” nothing. Under “Public Health Advisory,” nothing.

No retailer. No brand. No manufacturer. No state.

The public did not learn that these were Trader Joe’s Tarragon Chicken Salad Wraps from the FDA or from FSIS. It learned it from a lawsuit. On October 15, my firm filed Gottlieb v. Trader Joe’s Co., No. 2:26-cv-12017, in the U.S. District Court for the Central District of California on behalf of a North Carolina woman who bought her wraps at the Trader Joe’s in Myrtle Beach, South Carolina, and a Massachusetts woman who bought hers at the Trader Joe’s in Allston, Massachusetts.

The genetics now tie my clients together – and to the outbreak

When we filed, the link between my two clients and the outbreak rested on epidemiology: same product, same retailer, same few days, same pathogen, and a North Carolina health department record that lists the source of my client’s illness as a “wrap from Trader Joe’s.” That is how most outbreaks are solved.

Now there is more. Clinical isolates from outbreaks are uploaded to the National Center for Biotechnology Information’s Pathogen Detection database, where whole genome sequences are placed on a public tree. My two clients’ isolates (highlighted in red below) sit in the same tight cluster, alongside roughly forty other clinical isolates collected from late summer through October 20, 2026. The cluster carries the CDC code 2609MLEXH-2. CDC’s case definition for it is an E. coli O157:H7 isolate within zero allele differences by core genome MLST. In plain English: these people were sickened by the same bug, from the same source.

Note the last entry: a clinical isolate collected on October 20, nearly two months after these wraps were sold, and well after the government says the product was past shelf life. Either reporting is lagging badly or people are still getting sick. The public deserves to know which.

What the government knew – and when

Public health records I obtained from the Massachusetts Department of Public Health make clear that federal and state officials knew exactly what this product was, and who sold it, weeks ago:

By mid-September, CDC was reporting 39 cases in 13 states, ages 3 to 87, two-thirds of them women, with roughly one in five hospitalized. Of 21 patients with shopping information, 20 (95%) shopped at Trader Joe’s. Of those 20, 16 (80%) ate a pre-made Trader Joe’s wrap, and 12 of those 16 specifically reported the Tarragon Chicken Wrap, with three more saying they possibly ate one.

Massachusetts officials recorded that, after a call with federal partners, Trader Joe’s pulled the tarragon chicken salad wraps from store shelves in the states that received them and production was halted. The records describe the wraps as coming from a commonly identified contract manufacturer. An FSIS investigator was at a Trader Joe’s in Newton, Massachusetts. A focused questionnaire built entirely around Trader Joe’s wraps and sandwiches was sent to every state. Receipts were collected.

And then this, from CDC’s summary to the states: CDC was “not planning public notification” because the product was past shelf life and no longer available for purchase.

Think about that. The government knew the retailer, knew the product, knew the manufacturer, had receipts and genetic matches – and decided that because the wraps were gone, you did not need to know.

We have done this before – and the government named names

This is not the first time Trader Joe’s has sold E. coli-contaminated chicken salads and wraps. In 2013, 33 people in four states were sickened by salads made by Glass Onion Catering and sold at Trader Joe’s. In that outbreak, CDC named both Glass Onion and Trader Joe’s, and FSIS announced a recall that listed the Trader Joe’s products by name. Same retailer. Same type of product. Same pathogen. Same agencies. Thirteen years later, silence.

Based on what I have learned in this case, I believe the wraps were made for Trader Joe’s by F&S Fresh Foods of Vineland, New Jersey. One of my clients was contacted directly by F&S Fresh Foods’ quality systems staff. Neither FDA nor FSIS has said a word about it.

Why it matters

“Past shelf life” is not the end of the public health story. Wraps get frozen. People who got sick and never connected it to a wrap deserve to know why. Doctors deserve to know what to ask. Other retailers that buy from the same manufacturer deserve to know. And both agencies have said they are still looking for a contaminated ingredient and whether it went into other products. If that ingredient is lettuce, or anything else that went beyond Trader Joe’s, naming the manufacturer is how you find it.

There is also a simple matter of accountability. A company that sells a product that sickens fifty people should not be able to make it disappear by pulling it quietly and calling it a “proactive removal.”

The petition

That is why I am preparing a citizen petition asking FDA to establish, by rule, that the identity of a firm implicated in a foodborne illness outbreak is not confidential commercial information; to disclose growers, processors, manufacturers, distributors and retailers whether or not there is a formal recall and whether or not the product is past shelf life; and, in the meantime, to use the authority it already has under section 705(b) of the Food, Drug, and Cosmetic Act to name names. The Trader Joe’s wrap outbreak is now Exhibit A.

The petition is not yet filed. I am still taking edits and comments, and I welcome them – from public health officials, industry, consumer groups and anyone else who thinks the public has a right to know what made them sick.

Fifty people know. The government knows. Trader Joe’s knows. The manufacturer knows. The only people kept in the dark are the rest of us.

On October 21, 2026, FDA’s outbreak investigation table marked reference #1403, a Salmonella Newport outbreak first posted August 26 with 84 sick, as ended at 119 cases. In 56 days the file never named a food, never drew an on-site inspection, never got an advisory, and never had a CDC notice, so the states, hospitalizations and ages of the 119 are not public. The same update ended an 11-person Listeria file posted July 22 with no food named and started an inspection and sampling in a 46-person Listeria outbreak that still has no food.

The file grew from 84 to 119 in eight weeks and closed with the product line still reading Not Yet Identified.

Here is the whole public life of #1403, taken week by week from FDA’s own What’s New entries. I wrote it up at 116 on September 29 and again on September 30, when it had sat at 116 for a week with sampling marked and nothing else.

Table stampCase countChangeWhat FDA marked
August 2684PostedTraceback initiated
September 297+13Traceback
September 10109+12Traceback
September 16111+2Traceback
September 23116+5Sample collection initiated
October 21119+3Outbreak has ended

Source: FDA CORE investigation table, What’s New entries at each stamp, read October 22, 2026. Check: 13 plus 12 plus 2 plus 5 plus 3 is 35, and 84 plus 35 is 119. August 26 to October 21 is 56 days.

That is a real outbreak. One hundred nineteen culture-confirmed, whole-genome-sequenced SalmonellaNewport infections, which at CDC’s own multiplier of roughly 29 undiagnosed infections for every one counted is somewhere above 3,000 people sick. It grew by a dozen a week through the first half of September, slowed, and stopped. FDA’s note says the outbreak has ended. It does not say why it ended, which is the same as saying nobody knows.

Traceback and sampling were marked; an inspection never was.

The table has four action columns: traceback, on-site inspection, sample collection and recall. For #1403 the first was checked on day one and the third was checked on day 28. The second and fourth were never checked. Traceback without an inspection means FDA had enough food histories to start drawing purchase records back through distributors, and sampling means it tested something, but it never walked a farm, a packinghouse or a plant. That is the sequence you get when the traceback does not converge: the product lists from the sick people point in several directions, no single firm emerges, and the samples come back negative or do not match. It is also the sequence you get when the food is a fresh produce item that was gone from the shelves before the first isolate was sequenced. FDA’s note does not say which.

CDC never posted a notice, so 119 people were counted and nobody was warned.

CDC’s current outbreaks page, re-stamped the same day, lists 18 active multistate Salmonella investigations and names none of them. CDC posts a public notice when it has a food to tell people to avoid; with no food, there is nothing to post, and the 119 people exist only as a number on FDA’s table and in the state health departments that interviewed them. No one outside those agencies knows which states they live in, how many were hospitalized, how old they are, or when the first and last of them got sick. The public record of a 119-person outbreak is one row in a table and six one-line notes.

FDA named a food for Salmonella Newport three times this year, just not this time.

The Closed 2026 section of the same page lists #1366, Salmonella Newport, cantaloupe, 70 sick; #1365, Salmonella Newport and Kentucky, moringa powder; and #1358, Salmonella Typhimurium, Newport and Richmond, moringa leaf powder, which closed at 131 sick in 38 states. Newport is a serotype FDA knows how to find. In 2020 it was red onions, and CDC’s count reached 1,127 people in 48 states. The 2026 file that got away is the largest Newport file on this year’s table.

Seven of the nine no-food files on the table are now marked ended, carrying 573 people.

RefPathogenPostedSickStatusInspected
1392CyclosporaJuly 22241EndedNo
1403Salmonella NewportAugust 26119EndedNo
1387SalmonellaOranienburgJuly 899EndedYes
1417ListeriamonocytogenesSeptember 2346OngoingYes, October 21
1402Salmonella I 4,[5],12:i:-August 1243EndedYes
1385CyclosporaJuly 838EndedNo
1398CyclosporaAugust 522EndedNo
1379ListeriamonocytogenesJuly 2211EndedYes
1415ListeriamonocytogenesSeptember 3011OngoingYes

Source: FDA CORE investigation table, stamped October 21, 2026, rows whose product column reads Not Yet Identified. Check: 241 plus 119 plus 99 plus 46 plus 43 plus 38 plus 22 plus 11 plus 11 is 630. The seven ended rows sum to 573 and the two ongoing rows to 57; 573 plus 57 is 630. Adding the 50-person chicken wrap file, whose product is marked suspect, makes 680.

When I counted this ledger on October 17 it stood at 626 across nine rows with five of them ended. Four days later it is 630 with seven ended. The Listeria file #1379 is the quiet one: posted July 22, standing at nine sick by August, inspected and sampled, inched to 11, and closed October 21 with no food. For Listeria, with its weeks-long incubation and its habit of living in a plant for years, an inspected-and-closed file with no food named is the one that should worry people most, because whatever FDA walked through is still running.

The 46-person Listeria file is the one to watch: FDA is now inside a facility.

Reference #1417 was posted September 23 at 40 sick, went to 44 a week later and 46 on October 15. On October 21 FDA marked an inspection and sampling initiated. An inspection in a Listeria outbreak means traceback produced a firm, and sampling means swabs are being taken off that firm’s drains, floors and equipment. If the swabs match the clinical isolates, FDA will have a food, a plant and a name, and the question will be how long it takes to say them out loud.

FDA should post the Newport abstract now, not after the file moves to Closed.

Last week FDA posted Executive Incident Summary Abstracts for three closed files, including the Midwest Poultry egg outbreak, and those abstracts are the most useful documents on the page: they say what the hypothesis was, what was sampled, where the traceback legs went and where they stopped. For #1403, that document would tell the public what food FDA suspected, how many states were involved, whether the samples it collected were from the suspected food or the sick people’s refrigerators, and why the traceback did not converge. None of that is a trade secret. The outbreak is over; the risk of a premature warning is gone; what remains is the record. Post it while the 119 people are still sick enough to remember what they ate.

Is there a Salmonella Newport recall right now?

No. FDA’s reference #1403 ended on October 21, 2026, with no food identified and no recall or advisory. There is no product to throw out, because FDA never named one.

What food caused the 119-person Salmonella Newport outbreak?

FDA has not said. The product column reads Not Yet Identified, traceback and sampling were marked but no on-site inspection, and CDC never posted a notice. Earlier Salmonella Newport outbreaks have been traced to red onions in 2020 and to cantaloupe and moringa powder in 2026.

What should I do if I have Salmonella symptoms?

See a doctor if you have diarrhea with a fever over 102, bloody stools, vomiting that keeps you from holding liquids, signs of dehydration, or diarrhea lasting more than three days, and ask for a stool culture. A cultured, sequenced isolate is the only way a case gets counted and matched to an outbreak.

On November 6, FDA will hold the second of its public meetings on what it calls Challenges and Solutions in Lot-Level Food Traceability. Anyone who wants to speak must register by October 26, six days from today, and no same-day registration is allowed. Written comments are due December 6 in Docket No. FDA-2014-N-0053. The meeting is billed as a chance to talk about implementation. Read the notice closely and it is something narrower: a conversation about how to make the rule’s core requirement, the lot code, easier to live without.

So here is where the Food Traceability Rule stands, how it got here, and why, more than fifteen years after Congress ordered it, FDA cannot spend a dollar enforcing a single line of it.

What the rule does

Section 204 of the Food Safety Modernization Act, signed in January 2011, told FDA to identify the foods most often tied to outbreaks and to require anyone who manufactures, processes, packs or holds them to keep more and better records. Those foods are on the Food Traceability List: leafy greens, tomatoes, cucumbers, peppers, melons, sprouts, fresh herbs, fresh-cut fruits and vegetables, shell eggs, nut butters, soft cheeses, finfish, crustaceans, some shellfish and ready-to-eat deli salads.

For those foods, the rule requires companies to record key data elements at critical tracking events, harvesting, cooling, initial packing, shipping, receiving and transformation, and to tie them together with a traceability lot code assigned when the food is first packed and carried down the chain. When FDA asks during an outbreak, a covered company must produce an electronic, sortable spreadsheet within 24 hours. FDA estimated the rule would reach more than 323,000 domestic businesses operating about 484,000 establishments, according to the Congressional Research Service.

Before the rule, most food handlers only had to know one step forward and one step back, and farms and restaurants did not have to keep even that. FDA’s own pilot projects, run by the Institute of Food Technologists in 2011 and 2012, found that one-up, one-down records often could not connect the restaurants and grocery stores where people got sick to the farm that grew the food. That is the gap the rule was written to close, and the lot code is what closes it.

The calendar

Congress gave FDA until January 2013 to propose the rule. FDA missed it. The agency did not deliver its report to Congress on the pilot projects until 2016. In 2018 the Center for Food Safety and the Center for Environmental Health sued, and a consent decree set the schedule FDA finally met: a proposed rule on September 23, 2020, and a final rule on November 21, 2022. It took effect January 20, 2023, with compliance set for January 20, 2026. That three-year runway was already a year longer than FDA had proposed, granted because industry asked for it, and at the time FDA said it would go no further. In September 2023 the agency added that it would not begin routine inspections until 2027.

In January 2024 the Government Accountability Office told FDA to finalize and document an implementation plan to hit the 2026 date. Two months later, Rep. Scott Franklin of Florida introduced H.R. 7563, which would have relieved retailers, restaurants and warehouses of the duty to keep and pass along lot codes and required more FDA pilot projects before any enforcement. It never got a vote. Its ideas went into House agriculture appropriations bills instead.

On March 20, 2025, FDA announced it intended to push compliance back 30 months, to July 20, 2028. I wrote at the time that FDA had again kicked the rule down the road. The agency’s stated reason was that even the companies ready for January 2026 depended on supply chain partners who were not, and it said plainly that the extension did not amend, and that it did not intend to amend, the requirements of the rule. The proposed rule to extend the date was published August 7, 2025. As far as I can find, it has never been finalized. It did not need to be.

Congress finished the job. On November 12, 2025, the bill that ended the government shutdown, H.R. 5371(Public Law 119-37), carried Section 780 of Division B, which says no funds appropriated by the Act may be used to administer or enforce the rule before July 20, 2028. The same section told FDA to meet quarterly with farms, restaurants, retailers and warehouses to identify and implement flexibilities for satisfying the lot-level tracking requirement, to give industry guidance on food waste recovery, reclamation, intracompany transfers and customer returns, and to test its own internal tracing system. As I explained in August, that distinction matters. A delay is an agency asking for patience. A funding bar is Congress taking away the agency’s ability to change its mind.

Why it has not been implemented

There are three honest answers, and they overlap.

The first is that part of industry asked for the delay, and its own filings say so. When I went through the federal lobbying disclosures in August, the International Foodservice Distributors Association described its fourth-quarter 2025 work on the rule as support for the 30-month extension and targeted flexibilities. The National Restaurant Association listed H.R. 5371 by number, for provisions regarding FDA traceability, in the quarter it became law. The National Retail Federation reported in 2024 that it sought support for H.R. 7563. Jessica Glenza at the Guardian named Publix among the companies lobbying on the rule.

The members of Congress who carried that ask should be named, because their names are on the record. Rep. Scott Franklin, a Florida Republican who lives in Lakeland, where Publix is headquartered, introduced H.R. 7563 and is vice chair of the House Appropriations Subcommittee on Agriculture, Rural Development, Food and Drug Administration. Rep. Sanford Bishop, a Georgia Democrat, was its lead cosponsor; he is the subcommittee’s ranking member and chaired it in the 117th Congress. Rep. Jimmy Panetta, a California Democrat whose district runs down the Monterey County coast, cosponsored it. And Rep. Andy Harris, a Maryland Republican, chairs the subcommittee whose fiscal 2025 bill and fiscal 2026 bill, H.R. 4121, carried H.R. 7563’s language. The fiscal 2026 version became Section 780. Harris also wrote the fiscal 2027 bill the House passed in June. Two Republicans and two Democrats, three of them sitting where FDA’s money gets written. The bill they introduced died. Its provisions did not; they became law through the one committee where they never needed a hearing, a floor debate or a vote of their own.

The Senate did not go along. In Senate Report 119-37, Senate appropriators directed that FDA may not use funds to delay enforcement beyond July 20, 2028, and that full compliance and enforcement begin by then. Section 780 is a House product.

The second answer is that the industry’s argument is not frivolous, and I should say so. Traceability only works when everyone in a chain is doing it. The 2024 Reagan-Udall Foundation roundtables found low awareness of the rule among small and foreign suppliers and nonchain restaurants, and distributors have real problems with mixed-lot pallets and pick slots. But Kroger, Albertsons and Walmart built programs to the rule before the delay was announced, and Western Growers says its members have collected this shipment data voluntarily for more than a decade. The associations that lobbied for the delay represented the ready and the unready alike. They spoke for the unready.

The third answer is that FDA is not ready either. Section 204 also directed FDA to build an internal system to receive and analyze traceability data. In January 2026 GAO reported that the system still does not exist. FDA told GAO in March 2025 it would be done by January 2026; after the delay, it moved that date to July 2028, too.

What happened while we waited

FDA has now closed its investigation into the largest Cyclospora outbreak in American history: 12,883 confirmed illnesses, 570 hospitalizations and two deaths in 21 states, linked to shredded iceberg lettuce from Taylor Farms de Mexico. Leafy greens are on the Food Traceability List. FDA held its first lot-level public meeting on June 15; CDC puts the first illness on June 14. A Michigan epidemiologist spent the first two weeks of July asking where the lettuce came from. In the meantime, lettuce sales fell, and California growers plowed under healthy crops that had nothing to do with the outbreak. That is what happens when the answer takes twelve days instead of one: the innocent pay for the guilty.

On August 12, eleven consumer, public health and labor organizations in the Safe Food Coalition asked congressional leaders to rescind Section 780. The International Fresh Produce Association says it opposes further delays, and Taylor Farms says it supports traceability legislation. Congress has not acted. The House passed its fiscal 2027 agriculture and FDA bill, H.R. 8646, on June 4 by a vote of 213 to 210, and bill summaries say it carries the same bar on enforcement before July 20, 2028. The Senate has not passed its version.

Where things stand today

On February 19, FDA announced a final exemption for certain cottage cheese, a draft question-and-answer guidance and a series of stakeholder sessions organized by the Partnership for Food Traceability, an industry membership nonprofit. The first session, on March 6, was open only to the partnership’s members.

On October 8, FDA issued draft guidance saying it would not enforce the rule against retail food establishments and restaurants whose average food sales over the previous three years are more than $250,000 but not more than $1 million, adjusted for inflation from 2020. Businesses at $250,000 and under were already exempt. FDA says the new carve-out covers only a small share of food sales while relieving many small operators. Maybe so. It is also the first time the agency has moved the rule’s boundary since Congress told it to look for flexibilities.

And then there is November 6. According to the Federal Register notice and Food Safety Magazine’s summary, FDA wants to hear about a “reasonable range” of traceability lot codes for distributors shipping to retailers; “inferred” lot codes, where a distribution center calculates rather than scans what it shipped; key data elements for individual items no longer in a case; returns and reclamations; food waste recovery; intracompany shipments; retailers that transform food and send it to other stores; and whether industry should settle on a data standard. FDA’s earlier discussion paper and the comments on it are in the docket.

Look at where every one of those topics sits. Distribution centers, grocery stores, restaurants, the back half of the chain, the same link H.R. 7563 tried to cut. The lot code is the rule. A “reasonable range” of lot codes is a range of possible farms, and a range of possible farms is what investigators have today.

Industry, it is your turn

The consumer, public health and labor groups have done their part. Eleven of them signed the August letter. They should not be the only ones asking.

The companies that are already ready have more to gain from this rule than anyone, and they have been far too quiet. So, by name. Kroger, Albertsons and Walmart built traceability programs before the delay was announced; you are the proof that the rule works, and Congress needs to hear it from you. The International Fresh Produce Association says it opposes further delays. Taylor Farms says it supports traceability legislation. Western Growers has already written its members a guidance document on how to comply. The California and Arizona Leafy Greens Marketing Agreements set the food safety rules for the crop at the center of this summer’s outbreak. Put your names on a letter to House and Senate leadership, and to Senators John Hoeven and Jeanne Shaheen, who lead the Senate appropriations subcommittee, asking that Section 780 be rescinded and kept out of the fiscal 2027 bill in conference.

To FMI and the National Grocers Association, which applauded the delay, and to the International Foodservice Distributors Association, the National Restaurant Association and the National Retail Federation, whose filings asked for it: your members include the companies that are ready. Let them speak for themselves on November 6, and do not ask FDA to carve the lot code out of the back half of the chain on their behalf.

And to everyone who grows, packs, ships or sells a food on the list: comply now. Nothing in Section 780 stops a company from keeping lot codes and producing that 24-hour spreadsheet tomorrow. Do it before the 2027 growing season and say so publicly. If the companies already doing this asked Congress to unwind the delay, the argument that industry cannot manage the rule would collapse, because it would be industry saying otherwise. California’s growers learned this summer what it costs when nobody can draw a line around one facility. This rule draws that line.

What I would say on November 6

If you care about this, register to speak before October 26 and file comments by December 6. Here is what I would ask for. No flexibility that lets the lot code stop at the distribution center door. Any flexibility FDA does adopt should first be tested in a real or simulated traceback, the same pilot-project standard the industry demanded of the rule itself. And FDA should repeat in public what it told Congress and the courts: that the full public health benefit of the rule depends on every covered entity complying.

And to Congress: rescind Section 780, keep it out of the fiscal 2027 bill, and let the Senate’s own language, full compliance and enforcement by July 20, 2028, and not a day later, survive conference this time.

Congress ordered this rule in January 2011 and set a deadline of January 2013. If nothing else slips, enforcement begins in July 2028. That is fifteen and a half years from deadline to enforcement. The records the rule requires already exist, in some form, in warehouses and distribution centers across the country. The only question left on November 6 is whether they will follow the food all the way to the people who eat it.

Where the recalled oysters went and where the 27 sick people live. Sources: VDH recall alert (Oct. 9), FDA safety alert and CDC notice (Oct. 19, 2026). Virginia’s 53 in 18 states is not broken out by state and cannot be mapped.

As of October 20, 2026, the Virginia Department of Health counts 53 people in 18 states sick with Salmonellaafter eating raw oysters, with illnesses beginning in late May and running to September 21. CDC’s October 19 notice and FDA’s safety alert, posted the same day, count 27 in 12 states, with five of 21 hospitalized and no deaths, tied to oysters Little Wicomico Oyster Company harvested from the Little Wicomico River. Virginia says the 27 are a genomic subgroup of the 53. Georgia’s Department of Agriculture says Publix sold the recalled oysters as “James River Oysters” through October 14, five days after the recall, and two of CDC’s 27 live in Colorado, where Marler Clark represents a resident who became ill after eating raw oysters.

Twenty-six sick more people are in Virginia’s count and missing from CDC’s and FDA’s.

Virginia’s outbreak page, updated today, says that as of October 14 there were 53 cases in 18 states with onsets from late May through September 21, and that CDC’s 27 cases in 12 states are “a genomic subgroup” within that total. The arithmetic is 53 minus 27: twenty-six people with Salmonella Telelkebir in the same window whose isolates fall outside the subgroup, in six states no federal page names. CDC’s notice and FDA’s safety alert, both posted October 19, five days after Virginia’s count date, carry only the 27 and do not mention the 53. Within the 27, ten reported eating raw oysters; tag and traceback records exist for seven; two of the seven ate oysters from a single Virginia source and five from several; and the company’s Little Wicomico River oysters were “the only oysters in common to the seven ill people included in traceback.” Nothing on any page says whether the other 26 ate oysters or what the sequencing showed. A genomic subgroup is a decision about how tightly to draw the circle. The people outside it are just as sick, and if they ate oysters, the water that made them sick is not in the recall.

The recalled oysters went to sixteen jurisdictions, and the cases from that harvest have not been counted yet.

The gap between the map’s blue states and its red ones is a calendar, not a contradiction. The recall covers oysters harvested September 18 through October 8. CDC’s last illness onset is September 14, four days before the first recalled harvest day. Every one of the 27 counted so far ate oysters harvested before the recall window, which is why I said yesterday that the recall could not help any of them. Anyone sickened by the recalled harvest would have fallen ill from late September on, and CDC says it takes three to four weeks for a stool culture to become a sequenced isolate that is matched to the outbreak and counted. Those people are in the pipeline now. Seven jurisdictions on the receiving list — California, the District of Columbia, Georgia, Missouri, North Carolina, Nevada and Texas — have no case yet because the oysters that went there are the ones whose illnesses are still being confirmed, and because the summer customers who ate the earlier harvest may not be the fall customers who got the recalled one. Expect the blue states to turn red.

The same lag explains part of the 53-versus-27 gap, and the serotype explains the rest. Virginia’s 53 is every Salmonella Telelkebir illness in the window reported to it as the harvest state through the shellfish-sanitation channel, as of October 14. CDC’s 27 is the set whose isolates sequence closely enough together to be called one strain, pulled at an earlier data cutoff and posted October 19. Telelkebir was the serotype in last year’s oyster outbreak too, 80 sick in 23 states with no harvest area ever found, so some of the 26 outside the subgroup may carry a related strain from other water, and five of the seven traced patients ate oysters from more than one source. None of that is in dispute. What is missing is the sentence that says so: that 53 are sick, 27 sequence together, the rest are under review, and more are coming. Virginia wrote half of it. The federal pages wrote none.

The Publix label said James River, not Little Wicomico.

Yesterday I wrote that the consignee list has not been published; every federal page still says only, “restaurants and retailers.” Georgia’s Department of Agriculture recall page, posted October 15, adds a block headed “Information regarding oysters sold at Publix affected by this recall”: product description “James River Oysters,” GTIN 29953900000, purchase window “9/27/2026 thru 10/14/2026,” discard and do not eat, with a link to Publix’s corporate recall notice. Georgia does not say which stores.

The purchase window runs five days past the recall date.

Virginia’s October 9 recall alert asked receiving states to verify that companies “have stopped selling, serving, and distributing the affected oysters.” Publix’s purchase window closes October 14. Neither Georgia’s page nor the Publix notice says when the dealer’s notice reached Publix or whether oysters stayed on sale after it arrived. A shopper who read Virginia’s alert, FDA’s or CDC’s would have found “Little Wicomico” in all three and “James River” in none; the harvest tag stays with the container, and the label goes home.

Colorado has two of the 27, and the oysters were shipped there.

CDC’s map puts two of the 27 in Colorado, and Colorado is on both receiving lists, so no one must reach for travel to explain them. Marler Clark represents a Colorado resident who became ill after eating raw oysters, and our epidemiologists have requested the state and local health department records. Indiana, Iowa and Kentucky, with one or two cases each, are on neither list; travel or the further distribution FDA mentions could explain that, and the agencies have not said which.

StateSickStateSick
Pennsylvania8Connecticut1
New York4Florida1
Virginia3Illinois1
Colorado2Iowa1
Indiana2Kentucky1
Maryland2New Jersey1

Source: CDC, Where People Got Sick, Salmonella outbreak linked to raw oysters, posted Oct. 19, 2026. Check: 8 + 4 + 3 + 2 + 2 + 2 = 21, plus six states with one case each = 27, matching CDC’s subgroup total; Virginia’s 53 in 18 states as of Oct. 14 is not broken out by state.

Virginia pulled 400 oysters from the river on October 13, and the results were due today.

Virginia collected 400 of the company’s oysters from cages in the river on October 13 for Salmonella testing, with results expected October 20; as I write, the page does not report them. Reopening requires three negative rounds, the second about October 21 and the third the week after, and the closure is expected to run 30 days. Pennsylvania’s positive distributor sample is still awaiting sequencing. Publish the 400-oyster result, the sequencing result and the sanitary survey of the river before anyone harvests there again.

The first retailer’s name came from a state agriculture page, ten days before the federal notices.

The first public word was Virginia’s October 9 alert, written for regulators. The first retailer’s name came six days later from a receiving state. The federal notices came four days after that, carrying half of Virginia’s count. Both of my pending citizen petitions ask FDA to publish the consignee list in every recall, so the next shopper does not have to depend on which state she lives in.

If you bought James River Oysters at Publix between September 27 and October 14, do not eat them.

Throw them out or return them. If you ate raw oysters since mid-September and have diarrhea, fever or stomach cramps, see a doctor, say that you ate oysters and ask for a stool culture; the culture is what lets a state laboratory sequence the isolate and count you. Restaurants and retailers should check shellstock tags for VA-1421-SP and harvest dates from September 18 through October 8.

How many people are sick from the Little Wicomico River oysters?

Virginia counts 53 in 18 states as of October 14; CDC’s October 19 notice counts 27 in 12 states, the genomic subgroup tied by traceback to the Little Wicomico River, with five of 21 hospitalized and no deaths. Both counts are expected to grow, since it takes three to four weeks to link a new case.

Were the recalled oysters sold at Publix?

Yes. Georgia’s Department of Agriculture posted on October 15 that Publix sold them as “James River Oysters,” GTIN 29953900000, purchased September 27 through October 14, 2026, and Publix has its own notice under that title.

Which oysters are recalled?

Whole shellstock oysters harvested by Little Wicomico Oyster Company (VA-1421-SP) from the Little Wicomico River and Little Wicomico River Lower between September 18 and October 8, 2026. Other Virginia growing areas are not included.

CDC announced today that a multistate outbreak of Salmonella Telelkebir infections has been traced to raw oysters harvested by the Little Wicomico Oyster Company of Heathsville, Virginia, from the Little Wicomico River, a small tributary of the Potomac on Virginia’s Northern Neck. As of October 19, 27 people in 12 statesare confirmed sick, five of the 21 with information available (24%) have been hospitalized, and no one has died. Illnesses began between May 29 and September 14, 2026. The company has recalled oysters harvested from September 18 through October 8, Virginia closed the river to shellfish harvesting on October 9, and the advice from CDC, FDA and Virginia is the same: do not eat, sell or serve recalled oysters from Little Wicomico Oyster Company (dealer certification VA-1421-SP).

What the agencies know, and how they know it

Of the 27 sick people, 13 have been interviewed, and 10 of them (77%) reported eating raw oysters, against a 1.6% background rate in CDC’s FoodNet Population Survey. Traceback was possible for seven of the ten; their oysters came from several harvest areas, and Little Wicomico River oysters from Little Wicomico Oyster Company were the only ones all seven had in common. Pennsylvania officials also sampled oysters at a distributor that supplied the restaurants where sick people ate; one sample harvested by the company from the Little Wicomico River was positive for Salmonella. Whole genome sequencing to determine whether it matches the outbreak strain is pending.

Where the sick people live: Pennsylvania 8, New York 4, Virginia 3, Colorado 2, Indiana 2, Maryland 2, and one each in Connecticut, Florida, Illinois, Iowa, Kentucky and New Jersey. When they got sick, by month of onset: one in May, one in June, 13 in July, eight in August and four in September, the last on September 14. Patients range in age from 1 to 86, with a median age of 41.

The recall and the closure

The Virginia Department of Health’s Division of Shellfish Safety and Waterborne Hazards issued a recall alerton October 9 for shellstock oysters harvested from the Little Wicomico River and Little Wicomico River Lower from September 18 through October 8. The recall was triggered by an outbreak declared by the Pennsylvania Department of Agriculture after patients were epidemiologically linked to the company’s oysters. Virginia lists distribution to Colorado, Connecticut, the District of Columbia, Florida, Georgia, Illinois, Maryland, Missouri, North Carolina, New Jersey, Nevada, New York, Pennsylvania, Texas and Virginia; FDA adds California and notes the oysters may have been further distributed. The same day, Virginia issued Emergency Condemnation 010A, closing the downstream portion of the river to all shellfish harvesting through November 7, which Food Safety News noted was eight days into Virginia’s fall oyster season. Oysters from other Virginia growing areas are not part of the recall.

What the dates tell us

First, every one of the 27 reported illnesses began before the recall window opened. The last reported onset is September 14; the first recalled harvest date is September 18. Salmonella symptoms begin six hours to six days after exposure, so none of the 27 could have eaten a recalled oyster. The oysters that made them sick were harvested in summer, sold and eaten months before anyone connected the cases to a river. The recall protects whoever would have eaten the next bag; it cannot do anything for the 27. Later illnesses may still surface, since linking a new case to an outbreak takes three to four weeks, and if any fall inside the window the recall will have earned its keep. None of this is a criticism of Virginia or of the company, which acted within a day of the Pennsylvania finding. It is a description of the system we have: the outbreak is over, or nearly so, before the recall exists.

Second, three of the twelve states with sick people, Indiana, Iowa and Kentucky, are not on the distribution list for the recalled oysters. Those patients may have traveled, the company’s summer customers may differ from its fall customers, or the oysters were further distributed, which FDA says may have happened. CDC and FDA have not said which. The consignee list, the distributors, restaurants and retailers that received these oysters, is what I have been pressing FDA to require in every recall. It has not been published here.

Third, the first public word of this outbreak was not a consumer notice. It was Virginia’s October 9 recall alert, written for receiving states and shellfish regulators. Food Safety News reported it on October 12. CDC’s and FDA’s consumer notices arrived today, October 19, almost five months after the first person got sick on May 29.

The second Telelkebir oyster outbreak in a year

Last December I wrote about a Salmonella Telelkebir outbreak linked to raw oysters that CDC closed on February 24, 2026: 80 sick in 23 states, 34 of 68 hospitalized (50%), with illnesses from June 21 to December 22, 2025. Traceback was done for 19 patients, no single common source was found and nothing was recalled. The map of that outbreak also had Pennsylvania (10), New York (7), Virginia (6) and New Jersey (6) at the top. CDC’s notice today does not say whether this year’s strain is related to last year’s. If the same uncommon serotype is back for a second summer in the same part of the country, the first question is where it lives between seasons.

Salmonella in an oyster is not Vibrio in an oyster

Vibrio is a natural resident of warm coastal water. Salmonella is not. It lives in the intestines of people, livestock, birds and wildlife, and it reaches an oyster bed in sewage, septic drainage, farm runoff and droppings. Under the National Shellfish Sanitation Program, growing waters are classified by sanitary survey and fecal coliform standards. A 2005 study in Applied and Environmental Microbiology tested 1,296 market oysters from 36 bays on all three U.S. coasts, all harvested from approved waters, and found Salmonella in 7.4% of them, concentrated in particular bays and far more common in summer than in winter. It found no relationship between fecal coliform levels and the presence of Salmonella, and it concluded that oyster meat should be tested for Salmonella regularly, in every bay open for harvest, rather than relying on coliforms. Twenty-one years later, growing areas are still classified by the indicator, not by testing for the pathogen. Virginia said when it closed the river that it was testing shellfish from the implicated area. Those results, the sanitary survey of the Little Wicomico and the pollution source it points to should be published before the river reopens on November 7, along with FDA’s sequencing result on the Pennsylvania sample.

If you ate raw oysters

If you have eaten raw oysters since mid-September and have diarrhea, fever and stomach cramps, see a doctor and ask for a stool culture; a culture is what connects a patient to an outbreak. Restaurants and retailers should check with their distributors for Little Wicomico Oyster Company (VA-1421-SP) oysters harvested September 18 through October 8 and dispose of them.

Salmonella

Salmonella sickens more than a million Americans every year and is the leading cause of hospitalizations and deaths among foodborne bacteria. Its reach is remarkable—it turns up in produce, poultry, pantry staples, and pet food alike. Marler Clark, The Food Safety Law Firm, is the nation’s leading firm representing victims of Salmonella outbreaks. Our Salmonella lawyers have represented thousands of victims in the only U.S. law practice devoted exclusively to foodborne illness, which has recovered more than $850 million for victims and families nationwide. We have tied Salmonella outbreaks to cantaloupe, tomatoes, ground turkey, salami, sprouts, cereal, peanut butter, and restaurant meals, and we have brought cases against Cargill, ConAgra, Peanut Corporation of America, Sheetz, Taco Bell, Subway, and Wal-Mart. The Peanut Corporation of America outbreak ended in federal criminal convictions, with the company’s owner sentenced to twenty-eight years in prison. We are also pressing the federal government to treat Salmonella as an adulterant on raw chicken, so that contaminated poultry can be kept off store shelves the way dangerous E. coli already is.

If you or a family member became ill with a Salmonella infection—including lasting complications such as reactive arthritis or irritable bowel syndrome (IBS)—after eating contaminated food, contact the Marler Clark Salmonella attorneys for a free case evaluation.

FAQ

What is Salmonella?

Salmonella is a group of bacteria behind one of the most common—and most deadly—foodborne infections in the United States, sickening more than a million people a year. Symptoms usually begin between 6 hours and 6 days after eating contaminated food and include diarrhea, fever, and stomach cramps that last four to seven days.

What foods cause Salmonella outbreaks?

Poultry, eggs, ground beef, produce, peanut butter, flour, and even pet food have all caused outbreaks. Salmonella can survive for months in dry, low-moisture foods.

Can a Salmonella infection cause long-term problems?

Yes. Some victims develop reactive arthritis—joint pain and swelling that can persist for months—or irritable bowel syndrome after the initial illness resolves.

Who is most at risk?

Young children, adults over 65, and people with weakened immune systems are the most likely to be hospitalized or to suffer severe, invasive infection.

Can I sue for a Salmonella infection?

If your illness is linked to a contaminated product or a recognized outbreak, you may have a claim against those in the chain of distribution. A stool culture matching the outbreak strain is powerful evidence.

Additional Resources:

First, a shout-out to Jerry Hagstrom, who has been covering farm and food policy in Washington longer than just about anyone, for his piece in The Fence Post on the International Fresh Produce Association’s push to get members to sign up for its Advocacy Action Network. Jerry reads the fine print so the rest of us don’t have to.

According to Jerry, IFPA’s new chair, Elyse Lipman of Lipman Family Farms, told members in Orlando that surveys show 88% of consumers lost confidence in fruits and vegetables after this year’s Cyclospora outbreak. Her pitch: join the network so the industry can be mobilized quickly to contact Washington on everything from the farm bill to tariffs to programs that increase consumption. “We need to advocate for fresh with one voice,” she said.

I agree. I have spent more than three decades cleaning up after foodborne illness outbreaks, and I want Americans eating more fruits and vegetables, not fewer. My firm represents many of the people sickened in this year’s Cyclospora outbreak, and I can tell you none of them want to be afraid of a salad.

But one line in the story stopped me. The framing was that the industry’s Cyclospora problem was more with consumers and social media than with government. With respect, the problem was with a parasite that made people sick. Consumers did not lose confidence because of TikTok. They lost it because they, or someone they knew, got sick, and because they were too often left guessing which product, which company and which store. IFPA hired a global crisis communications firm and stood up a Cyclospora Rapid Response Task Force. Fine. But you cannot message your way out of a food safety problem.

So, if IFPA is building one voice, here is what I would like to hear it say:

Bring back the Microbiological Data Program. This one should be first on the list, and IFPA is uniquely positioned to make it happen, because IFPA’s predecessors helped kill it.

A little history. In 2001, USDA’s Agricultural Marketing Service launched the Microbiological Data Program (MDP) to collect data on harmful bacteria in fresh produce. State agriculture labs tested fruits and vegetables pulled from more than 600 distribution sites for Salmonella, Listeria, Shigella and pathogenic E. coli. Sampling ran through 11 states representing roughly half the U.S. population, and MDP supplied close to 90 percent of all available bacterial pathogen data on produce and fed CDC’s PulseNet. It cost about $5 million a year.

It worked. MDP testing prompted at least 19 produce recalls in two years, and it helped pinpoint outbreak sources, including Salmonella Javiana in green onions in 2009. That was the problem, at least for some in the industry. United Fresh and other trade groups lobbied for years to eliminate the program, arguing it cost growers millions in recalls and unfairly targeted farmers. The FY2013 budget zeroed it out, and MDP shut down in December 2012, which, by Food Safety News’ analysis, eliminated more than 80 percent of public pathogen testing of produce. FDA never filled the gap. I called for MDP’s return in 2024, and I am calling for it again.

United Fresh and PMA are now IFPA. If the industry wants to tell consumers it is serious about safety, there is no more credible message than asking Congress to restore and fully fund the surveillance program it once lobbied to end, and to expand it to cover parasites like Cyclospora, which MDP never tested for. Independent, random testing is how you find problems before people get sick and how you show the public the produce aisle has nothing to hide.

Traceability, on time. IFPA says it is pushing for implementation of traceability requirements. Good. Say it loudly, and mean the FSMA 204 Food Traceability Rule, with no more delays. The faster an outbreak is traced, the shorter the hit to the entire category.

Transparency, not secrecy. Nothing kills consumer confidence like a public health notice about an “unnamed” product. I am finalizing citizen petitions asking FDA to stop treating the identity of outbreak-implicated firms as confidential and to require retail consignee lists in Class I recalls. If consumers know exactly what to avoid, they don’t have to avoid everything. I would welcome IFPA’s comments and support.

Fund the people who solve outbreaks. CDC, FDA and state and local public health labs are the industry’s best friends when something goes wrong. Cutting them is a false economy that the produce aisle pays for.

Prevention on the farm. Clean water, clean hands, and audits that actually mean something. The cheapest outbreak is the one that never happens.

The fastest way to win back that 88% is to make sure there is not a next time, and when there is, to tell people quickly and specifically what to throw out. If the Advocacy Action Network wants to carry that message to Washington, sign me up. My number has not changed.