Hacker gets Doom running on a USB flash drive's built-in LCD, played by copying files
- ID
- 46968
- Status
- summarized
- Published
- 16 Nov 2026, 6:30 PM
- Fetched
- 16 Nov 2026, 8:27 PM
- Provider
- Tom's Hardware
- Category
- technology
- Original URL
- https://www.tomshardware.com/video-games/retro-gaming/hacker-gets-doom-running-on-a-usb-flash-drives-built-in-lcd-played-by-copying-files-hacker-dumps-firmware-from-chip-with-scrubbed-markings-through-an-open-debug-port-then-gets-the-game-running-with-ai-help
- Source URL
- https://www.tomshardware.com/feeds/all
Summary
- Score
- 4.0
- Created
- 16 Nov 2026, 8:29 PM
- Tags
- Audience
- developersvibe_coders
What happened
A hacker got Doom running on the small built-in LCD of a USB flash drive, with gameplay driven by copying files onto the drive. The firmware was extracted from a chip whose markings had been scrubbed, via an open debug port on the device, and the game was then brought up with help from AI. The available text is only the headline and page boilerplate — no chip model, firmware details, file-copy mechanics, or tooling specifics are given.
Why it matters
The only concrete takeaway here is a security one: a commodity USB drive shipped with an open, undocumented debug port and an unlabelled MCU, which is exactly the kind of exposed interface that lets someone dump and reflash firmware. If you ship hardware, decide whether your debug port is locked or fused off before volume production — this device's wasn't. Beyond that, the text gives no measurements, timings, or reproducible method, so don't treat it as a tutorial for AI-assisted firmware porting.
Discussion angle
If a $10-ish peripheral ships with an open debug port and a scrubbed chip, what's the realistic blast radius — and would locking the port have stopped this, or just slowed it down?