Launcher

Overview

Trojan:Win32/Launcher is a generic classification for a critical architectural component of modern malware: the initial execution stub. A 'Launcher' (or Dropper/Loader) is a small, highly obfuscated executable whose *only* job is to evade initial antivirus detection, establish a foothold on the system, and then silently decrypt and start the main malicious payload (like ransomware or a RAT) in memory (`T1106`).

Understanding Launcher Components
To an end-user, a Launcher is invisible. They might double-click a fake invoice PDF, see nothing happen, and assume the file is broken. Meanwhile, the Launcher is executing in the background. For a SOC analyst, a Launcher detection is the tip of the iceberg. The critical question is not 'How do we remove the Launcher?', but rather, 'What payload did the Launcher execute before we caught it?'

Execution and Evasion Strategies
Launchers are heavily obfuscated and frequently repacked to defeat static signature scanning (`T1027.002`). Upon execution (often via phishing attachments), the launcher profiles the system to ensure it is not running in a sandbox (`T1497`). It often carries the secondary payload as an encrypted blob within its own resource section. To evade behavioral detection, the Launcher rarely writes the final payload to disk. Instead, it uses Native API calls (`T1106`) to create a suspended instance of a legitimate Windows process (like `svchost.exe`), unmaps its memory, and injects the decrypted malicious payload directly into that process (Process Hollowing) (`T1055.012`).

Indicators of Compromise (IoCs)
The most crucial IoCs are behavioral. EDR telemetry will show the initial execution, followed immediately by 'Suspicious Process Injection' or 'Process Hollowing'. A classic IoC is the Launcher executable spawning a legitimate Windows binary (like `notepad.exe` or `svchost.exe`) with no command-line arguments, and that child process subsequently making anomalous network connections. The hashes of the injected payloads must be extracted from memory.

MITRE ATT&CK Techniques

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

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_LAUNCHER_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Launcher"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "launcher" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Launcher (Ransomware) Execution & Triage
id: fdc5707a-eee5-5cc3-a872-0c7c9f655b9c
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Launcher 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/launcher
- 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.t1106
- attack.t1055_012
- attack.t1027_002
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_LAUNCHER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Launcher 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 = "launcher" 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. Isolate the endpoint immediately; if the Launcher executed successfully, a secondary, highly destructive payload is likely running in memory.
2. Capture a live memory image (RAM dump) *before* rebooting or shutting down the machine to extract the injected secondary payload.
3. Analyze the parent process (e.g., Outlook, Word) to determine the initial vector and prevent further phishing compromise.
4. Hunt for the behavioral patterns (e.g., suspicious child processes) across the network, rather than relying solely on the Launcher's file hash.

What to Avoid

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

1. Do not close the incident just because the AV deleted the initial 'Launcher' executable; you must verify the secondary payload is not active.
2. Avoid relying solely on file hashes to hunt for Launchers, as attackers constantly repack the binaries to generate new hashes.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Jyuqet
• Sipia
• Genericrxbu
• Inor
• Plugs
• Anserin
• Emmfaeuirscb
• Vake

Machine-readable

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