{ "family": "loveletter", "sample_count": 1, "category": "ransomware", "description": "

Executive Summary

\nLoveletter (infamously known as the \"ILOVEYOU\" bug) is a historic, highly destructive mass-mailing worm that caused catastrophic global disruption in May 2000. While largely eradicated from modern environments, it serves as a foundational case study in social engineering and the abuse of native Windows scripting environments. The worm leveraged Microsoft Outlook and a VBScript payload to rapidly self-propagate while simultaneously overwriting and destroying millions of critical user files.\n\n

Infection Vector and Technical Capabilities

\nLoveletter's unprecedented spread was fueled by a perfectly executed social engineering lure:\n\n\n

Threat Assessment

\nWhile the original Loveletter worm is obsolete due to modern email filtering and macro security policies, the *techniques* it pioneered are still actively used today. File-overwriting is the precursor to modern ransomware, and utilizing native scripting languages (VBS, PowerShell) to \"live off the land\" remains a primary tactic for advanced threat actors.\n\n

Historical Remediation

\n", "cta": "Published by the SystemHelpdesk team.", "aliases": [ "VBS/LoveLetter", "Worm.ILoveYou", "VBS.LoveBug" ], "enrichment_level": "expert-seo", "faq": [ { "@type": "Question", "name": "What is Loveletter and what threat category does it belong to?", "acceptedAnswer": { "@type": "Answer", "text": "Loveletter is classified as a Ransomware. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments." } }, { "@type": "Question", "name": "How does Loveletter establish persistence and evade defensive controls?", "acceptedAnswer": { "@type": "Answer", "text": "Loveletter typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks." } }, { "@type": "Question", "name": "What are the essential incident response steps for mitigating a Loveletter compromise?", "acceptedAnswer": { "@type": "Answer", "text": "Security teams responding to Loveletter should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups." } }, { "@type": "Question", "name": "What cryptographic algorithms and file targeting techniques does VBS/LoveLetter employ during execution?", "acceptedAnswer": { "@type": "Answer", "text": "VBS/LoveLetter typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options." } }, { "@type": "Question", "name": "Are decryptors available for VBS/LoveLetter, and what is the recommended recovery procedure?", "acceptedAnswer": { "@type": "Answer", "text": "Decryption availability for VBS/LoveLetter depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups." } } ], "faq_count": 5, "mitre_attack": [ "T1566.001", "T1059.005", "T1485", "T1114.003" ], "cisa_advisory": null, "last_updated": "2026-10-15", "type": "Worm", "target_industries": [ "Healthcare", "Critical Infrastructure", "Enterprise" ], "motivation": "Financial Extortion", "threat_actors": [ "Unknown / Cybercriminal" ], "target_geographies": [ "Global" ], "attack_stage": [ "defense_evasion", "impact" ], "ecosystem": [ "windows_pe" ], "is_emerging": false, "mitre_attack_detail": [ { "id": "T1566.001", "name": "Phishing: Spearphishing Attachment", "tactic": "Initial Access" }, { "id": "T1059.005", "name": "Command and Scripting Interpreter: Visual Basic (VBScript within the ASP file)", "tactic": "Execution" }, { "id": "T1485", "name": "Data Destruction", "tactic": "Impact" }, { "id": "T1114.003", "name": "Email Forwarding Rule", "tactic": "Collection" } ], "containment_steps": [ "Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Loveletter from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.", "Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Loveletter symmetric encryption keys or uncompiled payload components may still reside in memory.", "Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Loveletter to inhibit recovery.", "Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.", "Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Loveletter binary and related persistence hooks are eradicated." ], "what_to_avoid": [ "Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Loveletter.", "Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.", "Do not connect clean backup drives or external storage to the affected network until Loveletter eradication is completely verified." ], "target_platforms": [ "Windows 11", "Windows 10", "Windows Server 2022", "Windows Server 2019" ] }