CPSC recall 06205
Lexar JumpDrive® FireFly and 1GB Secure II
- CPSC
- unknown
- Published 2024-07-01
On 2024-07-01 the CPSC announced a recall of Lexar JumpDrive® FireFly and 1GB Secure II by Lexar Media, citing the recalled JumpDrives® FireFly and Secure II products could overheat, posing a risk of burns to consumers and property damage.
| Agency | CPSC |
|---|---|
| Recall number | 06205 |
| Classification | Not classified |
| Status | unknown |
| Initiated | 2006-07-06 |
| Published | 2024-07-01 |
| Last updated | 2026-09-13 11:58 UTC |
| Company | Lexar Media |
| Distribution | US |
Product
Lexar JumpDrive® FireFly and 1GB Secure II | The recalled drives are high speed flash drives used to store, transfer and carry data from one computer to another. This recall only includes Lexar JumpDrive® FireFly which is sold in various colors, and Lexar JumpDrive® Secure II 1GB which has a metallic silver housing. "Lexar" is embossed on the front of the plastic housing and the capacity is marked on the back. The part number is located on the FireFly's packaging, and on the back of the Secure II 1GB drive. JumpDrive® FireFly Capacity Part Number 256MB (red) JDFF256-431RU JDFF256-264 JDFF256-445RU 512MB (lime green) JDFF512-431EM 1GB (blue) JDFF1GB-431TO 2GB (black) JDFF2GB-431BK JumpDrive® Secure II 1GB Part Number JDSE1GB-00-500 Rev H and 3052-1GBA-2006 JDSE1GB-00-500 Rev H and 3052-1GBA-2106 JDSE1GB-00-500 Rev H and 3052-1GBA-1906 JDSE1GB-00-500 Rev H and 3052-1GBA-1806
Reason
The recalled JumpDrives® FireFly and Secure II products could overheat, posing a risk of burns to consumers and property damage.
Status history
No status changes recorded since RecallRadar first saw this recall on 2026-09-13 11:58 UTC. Current status: unknown.
Source
Official record: https://www.cpsc.gov/Recalls/2006/Lexar-JumpDrive-Computer-Storage-Devices-Recalled-for-Burn-Hazard-Certain-Models-Involved
RecallRadar indexes public recall notices from the FDA, USDA FSIS, and CPSC. The official agency notice is the authoritative source. Always confirm details at the linked source before acting.