Msidrop

Overview

Behavior:Win32/Msidrop is a critical **Heuristic and Generic Detection** applied to malicious Windows Installer (`.msi`) packages. Attackers heavily utilize malicious MSI files to bypass security controls. Because `msiexec.exe` is a trusted, signed Microsoft binary designed to install software, many Application Control solutions (like AppLocker) and Endpoint Detection and Response (EDR) platforms implicitly trust it, allowing attackers to proxy the execution of their payloads undetected.

Understanding Msidrop (Proxy Execution)
To an end-user, executing a malicious `.msi` file usually looks like a standard software installation wizard, though it may run completely silently (`/qn`). For a security analyst, an Msidrop detection highlights the abuse of a legitimate system component (System Binary Proxy Execution - `T1218.007`). Attackers use malicious MSIs to drop Initial Access Brokers (like IcedID or Qakbot) or directly install Ransomware.

Execution and Evasion Mechanics
The `.msi` files are typically delivered via phishing emails (`T1566.001`) disguised as software updates or invoices. The malicious MSI package is authored using tools like WiX toolset to contain custom VBScript, JavaScript, or a compiled DLL (`CustomAction`). When the user clicks the file, `msiexec.exe` executes the embedded script or DLL in the context of the installer service, often resulting in privilege escalation (`T1548.002`). This process allows the malware to drop files into protected directories or establish persistence (`T1547.001`) while appearing as legitimate installation activity to security monitoring tools.

Indicators of Compromise & Impact
The impact depends on the dropped payload, but it is usually severe. Host-based IoCs include EDR alerts for `msiexec.exe` spawning suspicious child processes (like `powershell.exe`, `cmd.exe`, or `rundll32.exe`), or `msiexec.exe` making unexpected outbound network connections (`T1105`). The presence of randomly named executables or DLLs dropped into `C:\Windows\Installer` or `%AppData%` immediately following an MSI execution is a strong indicator.

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:

• T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
• 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_MSIDROP_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Msidrop"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "msidrop" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Msidrop (Ransomware) Execution & Triage
id: 6a5f9d28-4879-58f3-93be-01e655b83b5b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Msidrop 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/msidrop
- 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.t1218_007
- attack.t1105
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_MSIDROP_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Msidrop 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 = "msidrop" 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 to prevent the dropped payload from establishing C2 communication or moving laterally.
2. Analyze EDR telemetry to identify the specific `msiexec.exe` command line parameters and any child processes spawned during the installation.
3. Locate and extract the malicious `.msi` file from the `C:\Windows\Installer` cache for reverse engineering and IoC extraction.
4. Review AppLocker or WDAC policies to ensure that `.msi` execution is restricted and logged appropriately.

What to Avoid

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

1. Do not assume an installation is legitimate simply because `msiexec.exe` is a signed Microsoft binary.
2. Avoid relying solely on signature-based AV to detect malicious MSIs; behavioral monitoring of `msiexec.exe` child processes is essential.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Kelios
• Hiddentear
• Qmuabwpoobbg
• Xpyn
• Tvido
• Irplan
• Genericrxaz
• Harnig

Machine-readable

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