Notebookcheck Logo

Phantomdrive: The USB drive that hides in plain sight

Hard coded file security
ⓘ Canva and o7-machinehum on GitHub -edits
Hard coded file security
Encryption protocols can quickly become dense and overwhelming, but Phantomdrive brings a sneaky "now you see it, now you don't" approach to USB storage privacy.

Encryption protocols can quickly become dense and overwhelming, but Phantomdrive brings a sneaky "now you see it, now you don't" approach to USB storage privacy. Built around the CH569W RISC-V microcontroller, which features native USB 3.0 controller logic and on-chip AES hardware encryption, this open-source project conceals a secondary encrypted partition directly at the hardware controller layer. When plugged into a host PC, the drive mounts like an ordinary, unencrypted flash drive. Standard disk management tools and operating systems see only the public volume, leaving the hidden partition completely undetected.

Fortunately, unlocking the hidden files doesn't require custom software or special scripts. Instead, the user simply saves a text file containing the user's secret passphrase onto the visible drive partition. The CH569W chip monitors file write operations, reads the password payload, unmounts the storage controller, and pulls AES-XTS keys in hardware to remount with the private partition exposed. While the project is explicitly experimental, its novel stealth mechanic is sure to throw off casual snoops and automated forensic scanners expecting standard encrypted volume headers. For makers interested in embedded security, Phantomdrive demonstrates how smart hardware design can create true physical stealth storage. For more information and instructions on building a Phantomdrive, kindly visit the resources below.

Google LogoAdd as a preferred source on Google
Mail Logo

No comments for this article

Got questions or something to add to our article? Even without registering you can post in the comments!
No comments for this article / reply

static version load dynamic
Loading Comments
Comment on this article
Stephen Pereyra, 2026-07-28 (Update: 2026-07-28)