← MALWARE HISTORY LAB INTERACTIVE EXPERIENCE · AVAILABLE

INCIDENT RESPONSE RECONSTRUCTION · MAY 2000

Love Letter Incident Lab

EMAIL, TRUST & AUTOMATION — A SAFE HISTORICAL RECONSTRUCTION

Step into a fictional year-2000 workstation and examine why a deceptively named attachment and a familiar-looking message could scale so quickly. Every state is synthetic, local to this page, and reversible.

Safe historical reconstruction · browser only

This exhibit uses fictional contacts, counters, files, and system states. It does not open attachments, access visitor files or contacts, transmit messages, or make network requests. Choosing “open” begins a clearly labelled visual reconstruction—no code is executed.

YEAR 2000 WORKSTATION

Museum Mail 2000

SAFE HISTORICAL RECONSTRUCTIONBROWSER ONLY
01 INBOX02 MESSAGE03 INSPECT04 DECIDE05 INCIDENT06 SPREAD07 RESPONSE08 DEBRIEF

▣ MUSEUM MAIL 2000
✉ New↩ Reply⌕ FindSIMULATION
1 message · simulated local mailboxOFFLINE DEMONSTRATION
Reset clears all fictional incident states and scheduled visual transitions.
SAFE

Safe source explorer

This conceptual flow is intentionally non-executable. It describes categories of historical behavior without offering original code, real automation interfaces, or reproduction-ready logic.

MESSAGE RECEIVED
      ↓
USER OPENS ATTACHMENT
      ↓
SCRIPT ENVIRONMENT STARTS
      ↓
[ LOCAL ACTION CONCEPT ]
      ↓
[ FICTIONAL CONTACT CONCEPT ]
      ↓
[ MESSAGE GENERATION CONCEPT ]
      ↓
PROPAGATION

Why we do not display the original code here

The museum focuses on understanding historical mechanisms and defensive lessons without distributing or reproducing operational malicious code.

Historical context

ILOVEYOU / Love Letter · May 2000. It became one of the most widely known mass-mailing malware incidents of the early internet era, affecting organizations and users worldwide. Email, social engineering, deceptive attachment naming, scripting automation, and rapid propagation combined into global operational disruption.

This reconstruction is inspired by those mechanisms, not a claim that every recipient, configuration, or organization experienced the incident in exactly the same way.

CURATORIAL BOUNDARY NO LIVE ACTIVITY
FICTIONAL DATA ↓ BROWSER STATE ↓ VISUAL LESSON ↓ RESETTABLE