FDA Records Ongoing Class II Recall of LEADER Carbamide Peroxide 6.5% Ear Drops
An FDA enforcement report lists 5,471 units of the 0.5 fl oz product recalled nationwide as subpotent, with the action initiated June 25, 2026.
Was this report accurate and useful?
Sources
- https://api.fda.gov/food/enforcement.json?search=recall_number:%22D-0685-2026%22
- https://www.fda.gov/safety/industry-guidance-recalls/recalls-background-and-definitions
- https://dailymed.nlm.nih.gov/dailymed/drugInfo.cfm?setid=54515e9d-2225-4875-a1cf-a24a823300dd&audience=consumer
- https://dailymed.nlm.nih.gov/dailymed/drugInfo.cfm?setid=4b6fc00f-72d7-4675-9881-b763f27c06e3
- https://pubchem.ncbi.nlm.nih.gov/compound/Carbamide-Peroxide
- https://en.wikipedia.org/wiki/Hydrogen_peroxide%E2%80%93urea
Revision history
- Version 67 Aug 2026, 15:21current
Added direct source links for the FDA enforcement record, the Class II definition and the product background; text otherwise unchanged.
- Version 57 Aug 2026, 13:32
Added direct link to the FDA enforcement record and revised the product background to describe its regulated over-the-counter use in the ear and how the kit's bulb syringe is used; removed unsourced inactive-ingredient detail.
- Version 47 Aug 2026, 08:48
Replaced unsupported product-background details (Wikidata attribution, crystallisation method, labelled age directions) with the sourced composition, inactive ingredients and packaging description; added source URLs.
- Version 37 Aug 2026, 04:09
Quoted the assay figures as written in the record instead of correcting the expected value to 6.7%, quoted the quantity as recorded, and re-attributed the product background to DailyMed, Wikidata and a chemistry reference rather than PubChem and Wikipedia.
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.