Developer creates a 100% valid ZIP file that doubles as a BIOS-bootable operating system
- ID
- 46936
- Status
- summarized
- Published
- 16 Nov 2026, 6:00 PM
- Fetched
- 16 Nov 2026, 6:20 PM
- Provider
- Tom's Hardware
- Category
- technology
- Original URL
- https://www.tomshardware.com/software/operating-systems/developer-creates-a-100-percent-valid-zip-file-that-doubles-as-a-bios-bootable-operating-system-hiding-bios-boot-flags-inside-uncompressed-files-and-turning-file-headers-into-cpu-instructions
- Source URL
- https://www.tomshardware.com/feeds/all
Summary
- Score
- 5.0
- Created
- 16 Nov 2026, 6:20 PM
- Tags
- Audience
- developersvibe_coders
What happened
A developer built a single file that is simultaneously a fully valid ZIP archive and a BIOS-bootable operating system image. The trick relies on hiding BIOS boot flags inside uncompressed ZIP entries and treating ZIP file headers as CPU instructions that execute at boot. The article's body text available here is mostly site navigation and paywall boilerplate, so specifics like the author's name, repo link, target architecture, or size limits are not present.
Why it matters
The concrete takeaway is that file-format validation based on magic bytes, extensions, or 'is this a valid ZIP?' checks can be satisfied by an artifact that is also executable at the firmware level — so any upload pipeline that unzips or previews user-supplied archives (avatars, datasets, plugin bundles) is trusting a parser, not a type check. If you build ingestion, decide now whether you sniff, re-encode, or sandbox archive handling rather than assuming 'valid ZIP' means 'inert data'.
Discussion angle
Polyglot files are a fun puzzle but a real input-validation problem: ask the room what their upload endpoints actually do with a ZIP — parse in-process, shell out to unzip, or re-encode — and whether a file that is valid to two different parsers at once would slip through.