Chapak
Table of Contents
Overview
TrojanDownloader:Win32/Chapak (widely cataloged across threat telemetry as Trojan.Chapak, Win32/Chapak, or Downloader.Chapak) is a high-volume, multi-stage trojan downloader engineered to establish covert persistence on Windows endpoints and download auxiliary malicious binaries. Propagated through malspam campaigns containing weaponized Microsoft Office documents, malicious PDF exploits, and trojanized utility bundles, Chapak initiates an evasive multi-step staging sequence. It queries system locale configurations, inspects CPU hypervisor artifacts to bypass sandbox detonation chambers, and resolves Win32 API functions dynamically. Once an authentic execution environment is verified, Chapak connects via encrypted HTTP GET/POST channels to remote command-and-control servers, downloading and executing secondary crimeware payloads including banking stealers, remote access trojans (RATs), and ransomware droppers directly into memory or staging directories.
Known aliases
Threat reports may refer to this family under multiple names:
Family Pedigree & Lineage
Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:
Derived From / Upstream Ancestry: Win32 Modular Downloader Lineage
Known Derivatives & Downstream Variants: Trojandownloader:Win32/Chapak.A · Trojandownloader:Win32/Chapak.B · Trojan.Win32.Chapak.Gen
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.
- T1566.001: Scan email attachments for malicious macros, scripts, or suspicious archive files.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-PBA | Process Spawn Analysis | Detect | T1059.003 | Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe. |
D3-WAF | Web Content Filtering & Inspection | Filter | T1071.001 | Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles. |
D3-SDA | System Discovery Analysis | Detect | T1082 | Alert on rapid enumerations of systeminfo, hostname, and registry hardware trees in short intervals. |
D3-SCA | System Call Analysis | Detect | T1106 | Leverage kernel-mode EDR sensors to detect unhooked direct system calls (Syscalls) designed to circumvent user-mode API monitoring. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
D3-FS | File Sandboxing (Attachment Detonation) | Isolate | T1566.001 | Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor. |
Indicators of Compromise
Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.
File hashes (SHA-256, sample)
Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.
a1b2c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f909876543210abcdef0123456789abcdef9876543210abcdef0123456789abcdef
Delivery vectors
Malspam phishing campaigns containing weaponized documentsTrojanized utility software installers and cracksSecondary payload drops from exploit kits
Persistence mechanisms
HKCU\Software\Microsoft\Windows\CurrentVersion\Run\ChapakUpdateWindows Scheduled Task registered to run at startup
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:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_CHAPAK_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Chapak"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "chapak" ascii wide nocase
$s2 = "chapak" ascii wide nocase
$s3 = "trojandownloader:win32/chapak" ascii wide nocase
$s4 = "trojan.chapak" ascii wide nocase
$s5 = "win32/chapak" ascii wide nocase
$s6 = "downloader.chapak" ascii wide nocase
$s7 = "trojan.win32.chapak" ascii wide nocase
$s8 = "chapak downloader" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}
Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Chapak (Downloader) Execution & Triage
id: 396d1ef0-8a9b-57ff-bdf8-df55a5c15333
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Chapak 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/chapak
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.downloader
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566_001
- attack.t1059_003
- attack.t1547_001
- attack.t1071_001
- attack.t1106
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
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_CHAPAK_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Chapak 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 = "chapak" 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.
- Isolate the host from the network immediately to prevent Chapak from successfully requesting and executing secondary, high-impact payloads (e.g., ransomware or banking trojans).
- Inspect proxy and DNS telemetry to identify the download URLs and staging infrastructure contacted by Chapak; block these indicators enterprise-wide.
- Audit temporary directories (%TEMP%, %APPDATA%, C:\ProgramData\) to locate and quarantine secondary executables or DLLs dropped by Chapak.
- Purge startup registry keys and scheduled tasks established to re-attempt payload retrieval.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the incident is resolved simply because an antivirus tool removed the initial Chapak dropper; always verify that secondary payloads and persistence hooks have been eradicated.
- Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Chapak until memory triage is complete.
- Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.
References & External Analysis
- Microsoft Defender Threat Encyclopedia - TrojanDownloader:Win32/Chapak
- Trend Micro Threat Encyclopedia - Trojan.Win32.CHAPAK
- Kaspersky Threat Intelligence - Downloader.Win32.Chapak
- Search "chapak" on VirusTotal (External Analysis)
- Search "chapak" on Any.Run (Sandbox Sandbox)
- Search "chapak" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Chapak malware?
Chapak is an evasive Trojan downloader that infiltrates Windows systems to retrieve, unpack, and launch secondary malicious payloads such as ransomware and banking stealers.
How does Chapak establish persistence on infected endpoints?
Chapak commonly establishes persistence by writing registry Run keys under HKCU/HKLM or by configuring scheduled tasks that re-launch the downloader upon user login.
How does Chapak evade antivirus and sandbox analysis?
The malware checks for virtual machine artifacts, uses dynamic API hashing to hide imported functions, and executes sleep timers before communicating with C2 servers.
What secondary payloads are typically delivered by Chapak?
Threat actors use Chapak to deploy infostealers, banking trojans, cryptocurrency miners, and corporate ransomware encryptors.
How can administrators remediate Chapak infections?
Administrators should isolate infected hosts, perform offline antivirus scans, inspect startup registry entries and scheduled tasks, and block associated C2 IP addresses.
How do I remove Chapak from Windows?
Manual removal of Chapak is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
What are the main symptoms of a Chapak infection?
Symptoms of Chapak can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Downloaders
Want to prevent Chapak and similar threats from compromising your organization? Read our comprehensive defensive guide: Downloader & Dropper Protection.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/chapak.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.