Mummy

Mummy belongs to a tradition that predates DOS: the horror aesthetic. Before virus names became strings of numbers and technical descriptors, they were theater. They were invocations. Mummy was a threat delivered in character, and the character was ancient, undead, reanimated. It was 1991. Horror movies still mattered. Tapes circulated. The metaphor worked.

This EXE infector, lurking at 1364 bytes, carried a payload that understood visual language. Most viruses corrupted silently or cryptically. Mummy announced itself with ASCII art: a mummy, rendered in blocky characters, shambling across your screen. Below it, a message. The context matters here. Floppies were still primary distribution. Systems were still text-based. A hand-drawn corpse in ASCII had weight. It felt real.

The naming impulse reveals the author's mindset. Why mummy? The creature that rises from the dead to consume and corrupt. The entity that, once disturbed, cannot be easily defeated. The infection that spreads slowly but inevitably, reanimating dormant code. The mummy in virus culture was not just a visual theme; it was a metaphor for dormant threat. The virus slept in your executables until conditions awakened it. Then it moved, corrupted, and replicated.

The trigger mechanism was less precise than some of its peers. Mummy fired not on a specific date but after a certain threshold of infections. This made it unpredictable for the user and harder to pinpoint for the analyst. You never knew when your system had crossed the threshold. You never knew which executable would be the one to trigger the payload. The uncertainty was the point. Mummy did not announce its feast. It simply decided you had fed it enough.

When the payload fired, the ASCII mummy appeared, twitching across your screen in blocky pixels. The message accompanied it, a curse or mockery, something to read before the corruption began. Then random sectors on your active drive would get overwritten. Not organized destruction like Maltese Amoeba's surgical overwrite. Random. Chaotic. Mummy's method was to ravage, not to erase cleanly. The data would be damaged beyond recovery, but not arranged, not poetic. Just gone.

The infection vector was narrow: EXE files only. This limited its spread compared to generalist infectors, but it also made it persistent. Most machines of the era ran executable files constantly. Once Mummy lodged in even one EXE, it had a strong chance of replicating through the system. Batch files, system utilities, games, development tools: all vectors of dissemination.

What earned Mummy its aesthetic rating (a 4 out of 5 in the museum's assessment) was its commitment to theme. The ASCII art was deliberately crude, fitting the horror aesthetic. The mummy did not look sophisticated or threatening in a clinical sense. It looked cursed. The message felt taunted. The author had invested in atmosphere. In an era of code mostly written for technical demonstration or system access, Mummy's author wanted to create an experience. The visual payload suggested someone who understood that malware could be art, or at least could be a statement.

The Internet Archive Malware Museum preserved Mummy as a specimen of DOS-era visual culture. Its rating remains moderate in fame but high in aesthetic intent. It never caused the panic of the Morris Worm or the headlines of Michelangelo. But in the underground circles where code and culture collided, Mummy represented a lineage: viruses as narrative, as threat theater, as something that emerged from the dead to deliver a message and then corrupted what remained.

The ancient curse, rendered in ASCII. The creature that rose from dormant files to consume your data. Mummy was the virus author's chance to be a storyteller, and they took it.