{
  "family": "zafi",
  "sample_count": 5,
  "category": "advanced_threat",
  "description": "Worm:Win32/Zafi is a classic, historically significant mass-mailing computer worm that caused widespread disruption in the mid-2000s. Zafi (particularly variants like Zafi.B and Zafi.D) was notorious for its aggressive social engineering tactics, sending localized spam emails in multiple languages (often masquerading as Christmas greeting cards or urgent legal notices) to rapidly infect global networks.<br><br><b>Understanding the Zafi Worm</b><br>To an end-user, a Zafi infection results in immediate system slowdowns, disabled security tools, and the computer silently sending out thousands of spam emails to everyone in their address book. For a network administrator, Zafi represents a massive disruption event capable of crashing internal email servers due to the sheer volume of generated traffic, and causing the organization's IP address to be blacklisted.<br><br><b>Execution and Spreading Mechanics</b><br>Zafi propagates primarily via email (`T1566.001`). When a user executes the malicious attachment (often a `.pif`, `.scr`, or `.zip` file disguised as an image), the worm drops itself into the Windows `System32` directory with a randomized name (`T1204.002`). It establishes persistence via the Registry Run keys (`T1547.001`). To ensure its survival, Zafi aggressively attempts to terminate processes associated with popular antivirus and firewall software (`T1562.001`). The worm then harvests email addresses from the local hard drive (checking `.WAB`, `.HTM`, `.TXT` files) (`T1114.001`). Finally, it utilizes its own internal SMTP engine to blast copies of itself to all harvested addresses, frequently spoofing the 'From' address to make the emails appear legitimate (`T1098.002`).<br><br><b>Indicators of Compromise & Impact</b><br>The impact is severe network congestion, IP blacklisting, and the potential destruction of local security tools. Host-based IoCs include EDR alerts for a standard user process making thousands of outbound connections on port 25 (SMTP). Users may report that they cannot open Task Manager or Registry Editor, as Zafi often disables them. Network IoCs are dominated by massive spikes in outbound SMTP traffic originating from workstations rather than the corporate mail server.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Zafi and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Zafi is classified as a Advanced Threat. 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 Zafi establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Zafi 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 Zafi compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Zafi 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 lateral movement and credential access tactics does Zafi leverage in enterprise intrusions?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Zafi frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers."
      }
    },
    {
      "@type": "Question",
      "name": "How does Zafi maintain covert communications and evade perimeter network monitoring?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Zafi often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1566.001",
    "T1114.001",
    "T1098.002",
    "T1562.001"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1566.001",
      "name": "Phishing: Spearphishing Attachment",
      "tactic": "Initial Access"
    },
    {
      "id": "T1114.001",
      "name": "Email Collection: Local Email Collection (Harvesting address books)",
      "tactic": "Collection"
    },
    {
      "id": "T1562.001",
      "name": "Impair Defenses: Disable or Modify Tools (Terminating AV processes)",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1098.002",
      "name": "Account Manipulation: Additional Email Delegate Permissions (Spoofing emails via internal SMTP)",
      "tactic": "Credential Access"
    }
  ],
  "containment_steps": [
    "Immediately isolate the infected endpoint from the network to stop the massive outbound email flood and prevent the IP from being blacklisted.",
    "Block outbound port 25 (SMTP) traffic from all endpoints at the perimeter firewall, allowing only the designated corporate email servers to send mail.",
    "Run specialized AV removal tools, as Zafi actively monitors and terminates standard Task Manager and AV processes, making manual removal difficult.",
    "Notify email administrators to monitor the corporate mail queues, as internal worms can cause massive backlogs and potential server crashes."
  ],
  "what_to_avoid": [
    "Do not allow standard workstations direct outbound access to the internet on port 25; this is the primary enabler for mass-mailing worms.",
    "Avoid opening unexpected attachments, even if they appear to come from known contacts, as Zafi relies entirely on spoofing sender addresses."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "execution",
    "persistence"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows Server 2022",
    "Windows Server 2019"
  ]
}