BadPaw
- Type
- Loader
- Capabilities
- Defense evasionReconnaissance
- Delivery
- PhishingLure
- Platforms
- Windows
BadPaw, also known as CINDERBLOT, is a Windows malware loader implemented in .NET Framework 4.6. It establishes command-and-control communications to retrieve and deploy additional malicious components, including the MeowMeow backdoor. BadPaw has been used in Russian state-aligned phishing campaigns targeting Ukrainian organizations, with activity documented in early 2026.
Its delivery chain begins with phishing emails linking to ZIP archives containing disguised HTML Applications and Ukrainian-language border-crossing decoys. The initial scripts display a decoy document, perform environment checks, and establish scheduled-task persistence. A subsequent VBScript extracts the BadPaw executable from an image containing steganographically concealed payload data. BadPaw then contacts attacker infrastructure and reconstructs downloaded components for deployment.
BadPaw masquerades as a functional Windows Forms regular-expression testing utility. Its malicious logic is gated behind a specific launch parameter; execution outside the intended infection chain instead exposes benign-looking GUI behavior. Defensive measures include .NET Reactor obfuscation, anti-debugging and assembly-integrity checks, sandbox detection, timing and uptime checks, and runtime reconstruction of API names. It gathers hardware and operating-system information through WMI to generate a deterministic victim identifier. Its task-based command-and-control design uses HTTPS and cryptographic routines for payload protection and key exchange.
Associated threat actors
2 distinct threat actors Mallory has associated with this family across public reporting. Open in Mallory to see the full evidence chain and overlapping campaigns.
February – April 2026: BadPaw aka CINDERBLOT (.NET-based loader)
At the time of analysis, the file is recognized as malicious by only nine antivirus engines. We have named this malware “BadPaw”. Its primary objective is to establish communication with a Command and Control (C2) server to download additional malicious components.
Techniques & procedures
27 distinct techniques documented for this family, organized by ATT&CK tactic.
Initial Access
2 techniques
Initial Access
The attack chain initiates with a phishing email containing a link to a ZIP archive.
The email contained a cutt[.]ly shortened link redirecting to order.cyberflysystems[.]com.
Execution
7 techniques
Execution
BadPaw builds a comprehensive victim profile through seven WMI queries via the SOS class
To ensure persistence on the infected system, a scheduled task is created to execute the VBS file.
“…establishes persistence through a scheduled task.”
To ensure persistence on the infected system, a scheduled task is created to execute the VBS file.
“Once extracted, an initial HTA file displays a lure document…”
“Once extracted, an initial HTA file displays a lure document…”
"... link redirecting to a ZIP archive containing a Ukrainian border checkpoint permit that triggers the download of the BadPaw loader"
Persistence
2 techniques
Persistence
To ensure persistence on the infected system, a scheduled task is created to execute the VBS file.
“…establishes persistence through a scheduled task.”
Privilege Escalation
3 techniques
Privilege Escalation
To ensure persistence on the infected system, a scheduled task is created to execute the VBS file.
“…establishes persistence through a scheduled task.”
Process Injection Chain ... OpenProcess obtains a handle to the target, VirtualAlloc reserves memory, WriteProcessMemory writes the payload, and VirtualProtect flips the page to executable.
Stealth
11 techniques
Stealth
An additional layer of defense employed by BadPaw is the use of .NET Reactor, a commercial protection and obfuscation tool for .NET assemblies.
These scripts download PNG images, extract embedded ZIP archives from pixel data, and deploy executables.
Layer 5: API String Splitting -- Win32 API names are split across the .NET #US heap ... These are reassembled at runtime via Marshal.GetDelegateForFunctionPointer. Static string scanners see nothing.
The retrieved ZIP archive contains a file with an .html extension; however, this is a masquerade. Technical analysis reveals the file is actually an HTA (HTML Application).
Process Injection Chain ... OpenProcess obtains a handle to the target, VirtualAlloc reserves memory, WriteProcessMemory writes the payload, and VirtualProtect flips the page to executable.
The PE compilation timestamp is falsified to 2039, an anti-forensics measure.
Technical analysis reveals the file is actually an HTA (HTML Application). Upon execution, the HTA file drops and opens a decoy document...
Layer 4: Sandbox Detection -- The Sand class implements IsSandBox() for environment fingerprinting, CheckSleep() for timing-based detection ... and a Windows EventLog reader that checks for sandbox-indicator events. System uptime analysis rounds it out -- fresh VMs have short uptimes.
By querying this value, the malware calculates the "age" of the operating system. If the system was installed less than ten days prior to execution, the malware terminates.
CheckSleep() for timing-based detection (real machines have real sleep; emulated sleep is instant)
Layer 2: Anti-Debug -- A Debugger.IsAttached check fires early, with a reference to clrjit.dll suggesting JIT hook detection as a secondary measure.
Discovery
6 techniques
Discovery
Defender Reconnaissance Before any malicious activity, BadPaw queries the registry for the state of Windows Defender: HKLM\SOFTWARE\Microsoft\AMSI ... HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\PassiveMode ...
Before phoning home, BadPaw builds a comprehensive victim profile through seven WMI queries ... MAC address, Disk serial number, Motherboard serial, BIOS information, Computer system details, OS identity string, Process ID.
Layer 4: Sandbox Detection -- The Sand class implements IsSandBox() for environment fingerprinting, CheckSleep() for timing-based detection ... and a Windows EventLog reader that checks for sandbox-indicator events. System uptime analysis rounds it out -- fresh VMs have short uptimes.
By querying this value, the malware calculates the "age" of the operating system. If the system was installed less than ten days prior to execution, the malware terminates.
CheckSleep() for timing-based detection (real machines have real sleep; emulated sleep is instant)
Layer 2: Anti-Debug -- A Debugger.IsAttached check fires early, with a reference to clrjit.dll suggesting JIT hook detection as a secondary measure.
Command and Control
4 techniques
Command and Control
“Upon establishing command-and-control (C2) communication, the loader deploys MeowMeow…”
The Task-Based C2 ... GetTaskRequest() -- poll the C2 for pending commands ... Transport is HTTPS with custom User-Agent headers
Its primary objective is to establish communication with a Command and Control (C2) server to download additional malicious components.
The data received in the second stage consists of a standard HTML page containing a block of ASCII code... The identified ASCII block is decoded to reconstruct an additional malware component.
Exfiltration
1 technique
Exfiltration
SendResultRequest() -- exfiltrate task results
Observables
19 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.
Recent activity
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.