Moonpie

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Covert C2 Communications: Moonpie frequently utilizes encrypted, custom protocols or hides its command-and-control (C2) traffic within legitimate protocols (like HTTPS or DNS tunneling) to evade network intrusion detection systems (NIDS).
• Interactive Shell and File System Access: The backdoor provides the remote operator with full, interactive command-line access. The attacker can silently browse the file system, upload/download files, and execute arbitrary commands with the privileges of the compromised user or system account.
• Evasion and Persistence: Moonpie often employs techniques like DLL side-loading, process hollowing, or rootkit-like API hooking to hide its presence from local task managers and standard antivirus solutions.

Threat Assessment

Incident Response and Remediation

• Immediate IR Activation: A Moonpie infection requires a full-scale Incident Response investigation. Standard remediation (simply deleting the file) is insufficient, as the attackers have likely established multiple fallback persistence mechanisms.
• Network Isolation and Forensic Capture: Isolate the affected host but keep it powered on to capture volatile memory (RAM). Memory forensics is crucial for extracting the decrypted payload, active C2 connections, and potentially identifying lateral movement vectors.
• Enterprise-Wide Credential Reset: Assume all credentials, including domain administrator accounts, have been compromised. Force a global password reset and heavily monitor Active Directory for the creation of unauthorized accounts.

Known aliases

Threat reports may refer to this family under multiple names:

• Backdoor.Moonpie
• APT.Moonpie
• Win32/Moonpie

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:

• T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.
• T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.

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

title: SystemHelpDesk Detection - Moonpie (Trojan) Execution & Triage
id: f4fd7c84-d176-5f27-aa11-14bb585efa6f
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Moonpie malware family. Detects suspicious execution from temporary user
  directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/moonpie
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_003
- attack.t1071_001
- attack.t1573
- attack.t1055
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

rule MALWARE_WIN_MOONPIE_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Moonpie 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 = "moonpie" 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. Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Moonpie from retrieving secondary stage payloads.
2. Capture process memory triage to detect and terminate malicious threads injected by Moonpie into legitimate system processes such as explorer.exe or svchost.exe.
3. Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Moonpie persistence hooks.
4. Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
5. Rotate all credentials, domain user passwords, and session cookies active on the system during the Moonpie execution timeframe.

What to Avoid

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

1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Moonpie dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Moonpie until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Trojan)

Explore other documented threats in the same operational category:

• Laqma
• Mansabo
• Staser
• Peepviewer
• Synrat
• Krepper
• Qadars
• Sefnit

Machine-readable

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