Loveletter

Overview

Executive Summary

Infection Vector and Technical Capabilities

• The "LOVE-LETTER-FOR-YOU.TXT.vbs" Lure: The worm arrived via email with the subject line "ILOVEYOU." It contained an attachment masquerading as a text file but was actually a malicious Visual Basic Script (.vbs). At the time, default Windows settings hid file extensions, leading users to believe it was a harmless text document.
• Mass-Mailing Propagation: Upon execution, the VBScript utilized Windows Scripting Host (WSH) to interact with the Microsoft Outlook MAPI interface. It automatically sent a copy of itself to every single contact in the victim's Windows Address Book, causing exponential network congestion and email server crashes worldwide.
• Destructive Payload (File Overwriting): Beyond spreading, Loveletter was highly destructive. It recursively scanned local and mapped network drives, searching for files with extensions like `.jpg`, `.jpeg`, `.vbs`, `.vbe`, `.js`, `.css`, `.mp3`, and `.mp2`. It overwrote these files with a copy of its own malicious code and appended `.vbs` to the filename, effectively destroying the original data.
• Password Theft (Barok Trojan): In some variants, the script also attempted to download and execute a secondary payload known as the "Barok" trojan, designed to steal cached RAS (Remote Access Service) passwords.

Threat Assessment

Historical Remediation

• Mail Gateway Blocking: The immediate response involved configuring corporate firewalls and email gateways to outright block incoming emails containing the subject line "ILOVEYOU" or attachments ending in `.vbs`.
• Disable Windows Scripting Host: Many organizations temporarily disabled the Windows Scripting Host (`wscript.exe`) entirely via Group Policy to prevent the payload from executing, a tactic still utilized during severe "fileless" malware outbreaks today.

Known aliases

Threat reports may refer to this family under multiple names:

• VBS/LoveLetter
• Worm.ILoveYou
• VBS.LoveBug

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1059.005: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
• T1566.001: Scan email attachments for malicious macros, scripts, or suspicious archive files.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

rule MALWARE_WIN_LOVELETTER_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Loveletter"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "loveletter" ascii wide nocase
        $s2 = "vbs/loveletter" ascii wide nocase
        $s3 = "worm.iloveyou" ascii wide nocase
        $s4 = "vbs.lovebug" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Loveletter (Ransomware) Execution & Triage
id: a7ed52be-b7a9-5cb5-8125-4efd9fb297f4
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Loveletter malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/loveletter
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566_001
- attack.t1059_005
- attack.t1485
- attack.t1114_003
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

rule MALWARE_WIN_LOVELETTER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Loveletter tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "loveletter" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

1. 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.
2. 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.
3. 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.
4. 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.
5. 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

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

1. 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.
2. Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
3. Do not connect clean backup drives or external storage to the affected network until Loveletter eradication is completely verified.

References & External Analysis

• Search "loveletter" on VirusTotal (External Analysis)
• Search "loveletter" on Any.Run (Sandbox Sandbox)
• Search "loveletter" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Winload
• Protector
• Genericrxbx
• Chistudi
• Piker
• Tosthin
• Phnu
• Crcf

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/loveletter.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.