{
  "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": [],
  "faq_count": 0,
  "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": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}