{
  "family": "banpak",
  "sample_count": 12,
  "category": "trojan",
  "description": "Banpak (classified in antivirus detection telemetry under designations including Trojan:Win32/Banpak, Trojan.Win32.Banpak, and Win32/Banpak) is a multi-stage trojan engineered to disguise itself as legitimate software, execute unauthorized commands, and coordinate with external command-and-control infrastructure. Disseminated across enterprise networks and consumer workstations via social engineering, phishing attachments, malicious drive-by downloads, or weaponized software cracks, Banpak executes an initial reconnaissance phase upon system ingress. The binary evaluates host privileges, detects active hypervisors and sandbox environments to evade behavioral analysis, and establishes resilient autostart persistence by configuring registry keys under HKCU\\Software\\Microsoft\\Windows\\CurrentVersion\\Run or registering background Windows services. Operational mechanics characteristic of this family include deceptive executable masquerading, registry run key autostart, system telemetry gathering, and remote C2 beaconing. Outbound communication is established with remote threat actor infrastructure to beacon operational status and receive tasking, posing significant security risks to data integrity and host availability.",
  "cta": "Published by the SystemHelpdesk Threat Intelligence Team.",
  "aliases": [
    "Trojan:Win32/Banpak",
    "Trojan.Win32.Banpak",
    "Win32/Banpak"
  ],
  "enrichment_level": "curated_sourced",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Trojan:Win32/Banpak?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Banpak is a trojan threat designed to infiltrate Windows systems and execute unauthorized operations without user consent."
      }
    },
    {
      "@type": "Question",
      "name": "How does Banpak compromise target systems?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "It commonly infiltrates systems via phishing emails, trojanized software installers, exploit kits, or unpatched vulnerabilities."
      }
    },
    {
      "@type": "Question",
      "name": "What persistence mechanisms does Banpak utilize?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "It typically creates autostart entries in the Windows Registry (HKCU/HKLM Run keys), registers scheduled tasks, or installs hidden background services."
      }
    },
    {
      "@type": "Question",
      "name": "What risks does Banpak pose to an enterprise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "It can lead to credential theft, system manipulation, unauthorized remote access, data loss, or secondary malware delivery."
      }
    },
    {
      "@type": "Question",
      "name": "How can administrators detect and eliminate Banpak?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Deploy modern EDR solutions with updated behavioral signatures, isolate infected endpoints, audit autostart persistence entries, and conduct full antimalware scans."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1059.003",
    "T1027",
    "T1547.001",
    "T1071.001",
    "T1105"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-10-16",
  "mitre_attack_detail": [
    {
      "id": "T1027.002",
      "name": "Obfuscated Files or Information: Software Packing",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1055",
      "name": "Process Injection (Process Hollowing)",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1497.001",
      "name": "Virtualization/Sandbox Evasion: System Checks",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1547.001",
      "name": "Boot or Logon Autostart Execution: Registry Run Keys",
      "tactic": "Persistence"
    },
    {
      "id": "T1105",
      "name": "Ingress Tool Transfer",
      "tactic": "Command and Control"
    }
  ],
  "containment_steps": [
    "Instantly isolate the endpoint; if Banpak executed successfully, a highly capable banking trojan is likely active in memory.",
    "Enforce immediate enterprise-wide password resets for the affected user, assuming all credentials typed since infection have been captured via web-injects.",
    "Capture a full forensic memory image (RAM dump) to extract the injected payload and identify the specific banking trojan family and its C2 configuration.",
    "Perform a complete bare-metal wipe and reinstall of the operating system, as memory-resident malware can leave extremely sophisticated persistence hooks."
  ],
  "what_to_avoid": [
    "Do not close an incident simply because the initial Banpak dropper was deleted; the true payload is already running injected in memory.",
    "Avoid relying solely on file hashes for detection, as packing services generate unique hashes for every campaign."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "execution",
    "persistence"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "sources": [
    {
      "name": "Microsoft Defender Threat Encyclopedia - Trojan:Win32/Banpak",
      "url": "https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?Name=Trojan:Win32/Banpak"
    },
    {
      "name": "Kaspersky Threat Intelligence - Trojan.Win32.Banpak",
      "url": "https://threats.kaspersky.com/en/threat/"
    },
    {
      "name": "MITRE ATT&CK - Enterprise Techniques",
      "url": "https://attack.mitre.org/techniques/T1059.003/"
    }
  ],
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows 7"
  ]
}