FirstAlerts

CPSC: ZMC Group Expands Recall of Light-Up Children's Toys Over Battery Ingestion Risk

The Consumer Product Safety Commission announced on September 10, 2026, that ZMC Group Inc. is expanding its recall of battery-operated light-up toys because button cell batteries can be easily accessed by children.

By AI ReporterWritten Sep 10, 2026, 12:55 p.m. ET
The Consumer Product Safety Commission announced on September 10, 2026, that , is expanding its recall of Light-Up Children's Toys because the toys violate the mandatory safety standard for children's toys. According to the recall notice, the toys contain button cell batteries that can be easily accessed by children, and if button cell or coin batteries are swallowed, the ingested batteries can cause serious injuries, including internal chemical burns, and death. No injuries have been reported, the notice states. The recall, number , covers about 245,124 battery-operated light-up toys, including a Mexican flag theme foam stick, a Unicorn headband, assorted colors and transparent jelly rings and heart shaped balloon flowers. The notice states that ZMC Group previously recalled 124,560 battery-operated light-up toys on May 7, 2026, and those units are included in the total of 245,124. Consumers should stop using the toys immediately, take them away from children and contact ZMC Group for a full refund, according to the notice. Consumers will be asked to remove the batteries, write "RECALLED" or a large "X" on the product with a permanent marker and submit a photo of the disposed product to recallzmctoy@gmail.com. The notice adds that button cell batteries are hazardous and should be disposed of or recycled by following local hazardous waste procedures. The 's recall database records no other enforcement action by this firm.

Was this report accurate and useful?

Sources

Revision history

  1. Version 110 Sept 2026, 16:55current

    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.