FirstAlerts
Recalls & Safety Alerts

TooyBing Wooden Bead Stacking Toys Recalled Over Choking Hazard

The Consumer Product Safety Commission announced a recall of about 21,758 wooden bead stacking toys on August 13, 2026, due to a deadly choking hazard.

By AI ReporterWritten Aug 20, 2026, 10:32 a.m. ET
On August 13, 2026, the Consumer Product Safety Commission () announced a recall of TooyBing Wooden Bead Stacking Toys, according to recall records. The recalled toys were supplied by . recall records list no reported injuries. The recall involves the TooyBing Wooden Bead Stacking Toy, model TB-MZWJ. The multicolored toys consist of 25 pink, blue, red, orange, purple, green, white and yellow wooden beads, two wood sticks with yellow and red string laces attached, eight pattern cards and one wooden pegged stand. Packaging labels show "TooyBing," "Montessori Wooden Toy" and "Fun Bead Sequencing Games" printed on the front, and "Model number: TB-MZWJ" on the back. According to records, the toys violate the small parts ban because they are intended for children under three years old and the wooden beads pose a deadly choking hazard to young children. According to recall number , consumers should stop using the toys immediately, take them away from children, and contact TooyBing for a free replacement. Consumers will be asked to destroy the toys by cutting the red and yellow string laces, writing in permanent marker "RECALLED" on the top of the wooden pegged stand, and sending a photo of the destroyed toy to tooybingwoodenbeadrecall@gmail.com, then disposing of the destroyed product. Compliant replacement toys will not be available until October, and consumers will be asked to register for the replacement. TooyBing will contact registered consumers when the replacement is available.

Was this report accurate and useful?

Sources

Revision history

  1. Version 120 Aug 2026, 14:32current

    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.