Hacking Tools

Doom-Poly : A Multi-Format Polyglot Executable Running Doom

Doom-Poly is a fascinating polyglot executable that combines the functionality of a PDF, DOS executable, and Windows PE executable to run the classic game Doom.

This innovative construction leverages Robert Xiao’s Universal Doom and Allen Ading’s Doom.PDF to create a file that operates seamlessly across these formats.

The project demonstrates the versatility of file formats and the creative possibilities of polyglot programming.

The polyglot construction involves embedding multiple file format signatures into a single file. Here’s how it is achieved:

  1. PDF and EXE Header Manipulation:
    The gap between the EXE header (up to byte 0x1B) and the PE header offset (at byte 0x3C) is utilized to insert a PDF signature (%PDF-1.x) and a stream object declaration.
    • This allows the file to be identified as a valid PDF while hiding the Doom executable content.
  2. Appending PDF Content:
    The body of the EXE/PE contains the Doom executable, while the end of the file includes additional PDF structures, such as closing the stream object and appending the rest of the Doom.PDF content.
  3. Rebuilding PDF Metadata:
    To ensure compatibility with Chrome’s PDF engine, an updated cross-reference (XREF) table and startxref pointer are added, along with adjustments to the trailer’s /Size property.

The resulting file can function as:

  • A playable Doom game when executed as an EXE or PE.
  • A readable PDF document when opened in Chromium-based browsers (with limited functionality).

The PDF payload only works under Chrome due to its limited implementation of JavaScript in PDFs. Additionally, performance constraints arise from rendering Doom in grayscale ASCII characters within a text field-based framebuffer.

This project showcases the potential of polyglot files in creative programming, security research, and file format exploration.

While primarily experimental, it highlights vulnerabilities in interpreting multi-format files, emphasizing the need for robust validation mechanisms

For more details or to explore this project, refer to Allen Ading’s GitHub repository for Doom.PDF.

Varshini

Varshini is a Cyber Security expert in Threat Analysis, Vulnerability Assessment, and Research. Passionate about staying ahead of emerging Threats and Technologies.

Recent Posts

Nginx Commands in Linux: Start, Stop, Reload, Test, and Log

Nginx is a high-performance web server and reverse proxy trusted by some of the largest…

3 days ago

ufw Command in Linux: Manage Firewall Rules with Examples

ufw (Uncomplicated Firewall) sits on top of iptables (or nftables on newer systems) and replaces…

3 days ago

who Command in Linux: Show All Logged-In Users and Sessions

When you share a server with a team or investigate unexpected activity, the first question…

3 days ago

file Command in Linux: Identify File Types Without Extensions

The file command inspects the actual contents of a file and reports its type — regardless of…

4 days ago

chattr Command in Linux: Set File Attributes with lsattr

chattr sets and removes special file attributes that operate at the filesystem level, separate from standard…

4 days ago

env Command in Linux: Show and Set Environment Variables

env prints the current environment, sets or removes variables for a single command, and can start…

4 days ago