{
  "family": "msidrop",
  "sample_count": 3,
  "category": "ransomware",
  "description": "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.<br><br><b>Understanding Msidrop (Proxy Execution)</b><br>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.<br><br><b>Execution and Evasion Mechanics</b><br>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.<br><br><b>Indicators of Compromise & Impact</b><br>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.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Msidrop and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Msidrop is classified as a Ransomware. 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 Msidrop establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Msidrop 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 Msidrop compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Msidrop 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 cryptographic algorithms and file targeting techniques does Msidrop employ during execution?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Msidrop typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options."
      }
    },
    {
      "@type": "Question",
      "name": "Are decryptors available for Msidrop, and what is the recommended recovery procedure?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Decryption availability for Msidrop depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1566.001",
    "T1218.007",
    "T1105"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1218.007",
      "name": "System Binary Proxy Execution: Msiexec",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1566.001",
      "name": "Phishing: Spearphishing Attachment",
      "tactic": "Initial Access"
    },
    {
      "id": "T1105",
      "name": "Ingress Tool Transfer (Msiexec downloading secondary payloads)",
      "tactic": "Command and Control"
    }
  ],
  "containment_steps": [
    "Isolate the endpoint to prevent the dropped payload from establishing C2 communication or moving laterally.",
    "Analyze EDR telemetry to identify the specific `msiexec.exe` command line parameters and any child processes spawned during the installation.",
    "Locate and extract the malicious `.msi` file from the `C:\\Windows\\Installer` cache for reverse engineering and IoC extraction.",
    "Review AppLocker or WDAC policies to ensure that `.msi` execution is restricted and logged appropriately."
  ],
  "what_to_avoid": [
    "Do not assume an installation is legitimate simply because `msiexec.exe` is a signed Microsoft binary.",
    "Avoid relying solely on signature-based AV to detect malicious MSIs; behavioral monitoring of `msiexec.exe` child processes is essential."
  ],
  "target_industries": [
    "Healthcare",
    "Critical Infrastructure",
    "Enterprise"
  ],
  "motivation": "Financial Extortion",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "defense_evasion",
    "impact"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows Server 2022",
    "Windows Server 2019"
  ]
}