{
  "family": "unpacked",
  "sample_count": 3,
  "category": "ransomware",
  "description": "Trojan:Win32/Unpacked is a critical **Heuristic Detection** flagged by modern endpoint security solutions. It is not a specific malware family, but rather a behavioral alert triggered when an executable file attempts to decrypt, decompress, or 'unpack' a hidden payload directly into memory at runtime. This behavior is a massive red flag, as it is the primary technique used by advanced malware to evade static antivirus signatures.<br><br><b>Understanding Unpacked (Software Packing)</b><br>To an end-user, an Unpacked alert simply means the AV caught a virus. For a security analyst, this detection indicates that the endpoint encountered sophisticated malware utilizing Defense Evasion (`T1027.002`). Malware authors use tools like UPX, Themida, or custom cryptors to scramble their code. The resulting file looks benign on the hard drive. However, when the user double-clicks it, a small 'stub' of code runs first, unscrambling the true malicious payload in memory and executing it without ever touching the disk.<br><br><b>Execution and Evasion Mechanics</b><br>The infection usually begins with user execution (`T1204.002`) of a seemingly harmless file (e.g., a PDF reader crack or a disguised email attachment). Once executed, the packer stub allocates memory, decrypts the true payload, and uses techniques like Process Hollowing (`T1055.012`) to inject the malicious code into a legitimate Windows process (like `svchost.exe`). Modern EDR solutions use memory scanning and API hooking to detect this transition; when they see an executable trying to run code from a dynamically allocated memory space that doesn't match the file on disk, they trigger the 'Unpacked' heuristic and terminate the process.<br><br><b>Indicators of Compromise & Impact</b><br>The impact depends on what payload was being unpacked (ransomware, trojan, spyware). Host-based IoCs include the quarantined 'packed' file and EDR telemetry detailing anomalous memory allocation (`VirtualAllocEx`) or suspicious process creation. Because the malware attempts to run in memory, a live RAM dump is often the only way to retrieve the true, unpacked payload for reverse engineering.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Unpacked and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Unpacked 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 Unpacked establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Unpacked 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 Unpacked compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Unpacked 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 Unpacked employ during execution?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Unpacked 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 Unpacked, and what is the recommended recovery procedure?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Decryption availability for Unpacked 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": [
    "T1055.012",
    "T1027.002",
    "T1204.002"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1027.002",
      "name": "Obfuscated Files or Information: Software Packing",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1055.012",
      "name": "Process Injection: Process Hollowing",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1204.002",
      "name": "User Execution: Malicious File",
      "tactic": "Execution"
    }
  ],
  "containment_steps": [
    "Isolate the endpoint immediately to prevent the potentially unpacked payload (which could be a worm or ransomware) from spreading.",
    "Extract the quarantined file and submit it to a dynamic malware analysis sandbox to observe its behavior and identify the true payload.",
    "Review EDR telemetry to determine if the unpacking process was fully blocked, or if the malware managed to execute any commands before termination.",
    "Ensure the endpoint's EDR agent is fully up to date, as memory scanning capabilities are frequently updated to counter new packing techniques."
  ],
  "what_to_avoid": [
    "Do not assume the threat is minor because it has a generic name; 'Unpacked' often hides the most devastating, zero-day malware variants.",
    "Avoid releasing the file from quarantine until a thorough sandbox analysis confirms it is benign."
  ],
  "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"
  ]
}