Fantom

Overview

Executive Summary

Infection Vector and Technical Capabilities

• The Fake Windows Update Overlay: When executed, Fantom immediately displays a full-screen overlay that perfectly mimics the legitimate "Configuring critical Windows Updates" screen (complete with a progress counter). This screen blocks access to the desktop, preventing the user from interrupting the process.
• Background Encryption: While the fake update screen is displayed, the ransomware silently scans all local drives and network shares in the background, encrypting documents, images, and databases using strong cryptography (AES-128/RSA). It typically appends the `.fantom` extension to encrypted files.
• Volume Shadow Copy Deletion: It executes commands (`vssadmin.exe`) to destroy local system backups and recovery points, ensuring the victim cannot easily restore their files.
• Ransom Note Generation: Once encryption is complete, the fake update screen disappears, and the desktop wallpaper is replaced with a ransom note instructing the victim to contact an email address for payment instructions.

Threat Assessment

Incident Response and Remediation

• Immediate Network Severance: If the fake update screen is observed, physically disconnect the endpoint from the network and power it down immediately to halt the encryption process (at the risk of corrupting files currently being written).
• Do Not Pay the Ransom: Paying the ransom is strongly discouraged and does not guarantee data recovery.
• Eradication and Restoration: The only reliable remediation strategy is a complete bare-metal wipe of the infected systems and a full restoration from secure, air-gapped backups.

Known aliases

Threat reports may refer to this family under multiple names:

• Ransom.Fantom
• Trojan-Ransom.Win32.Fantom
• Win32/Filecoder.Fantom

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:

• T1036.003: Monitor for executable files running from unusual paths or with deceptive names. Use EDR to detect process masquerading.

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_FANTOM_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Fantom"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "fantom" ascii wide nocase
        $s2 = "ransom.fantom" ascii wide nocase
        $s3 = "trojan-ransom.win32.fantom" ascii wide nocase
        $s4 = "win32/filecoder.fantom" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Fantom (Ransomware) Execution & Triage
id: 65a08ea5-16c0-57db-b5c4-f657d4b97403
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Fantom 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/fantom
- 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.t1486
- attack.t1490
- attack.t1036_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_FANTOM_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Fantom 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 = "fantom" 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 Fantom 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 Fantom 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 Fantom 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 Fantom 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 Fantom.
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 Fantom eradication is completely verified.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Betkrypt
• Mdrop
• Xdisccorp
• Yiwanzhushou
• Rogan
• Serveradmin
• Patpoopy
• Mi0Ax8Mhb4Ji

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/fantom.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.