SmokeLoader Backdoor/Loader: Process Hollowing Injection into explorer.exe with Anti-VM/Anti-Debug Evasion (Smoky Spider)
SmokeLoader Backdoor/Loader (TL-2026-2482), also tracked as Smoke Bot, is a high-severity malware campaign, first published 2026-09-13. It is attributed to SMOKY SPIDER (Russia) with medium confidence, affects Microsoft Windows (all supported desktop versions), maps to 11 MITRE ATT&CK techniques (T1027.013, T1053.005, T1055.012), and is covered by 9 detection rules and 29 indicators of compromise.
Key facts for TL-2026-2482
- Threat ID
- TL-2026-2482
- Also known as
- Smoke Bot, Dofoil, Sharik, Smoke Loader
- Severity
- HIGH
- Status
- ACTIVE
- Category
- MALWARE
- First published
- 2026-09-13
- Last reviewed
- 2026-09-13
- Attribution
- SMOKY SPIDER
- Attribution confidence
- MEDIUM
- Nation-state nexus
- Russia
- Motivation
- FINANCIAL
- Target sectors
- finance, government administration, critical infrastructure, retail, general enterprise
- Target regions
- ukraine, Europe, North America, taiwan
- Detection rules
- 9
- Indicators of compromise
- 29
Malware and tooling in SmokeLoader Backdoor/Loader
Malware and tooling: Smoke Loader - S0226, SmokeLoader
SmokeLoader is a modular backdoor/loader, developed and operated by the financially motivated Smoky Spider group since 2011, that injects into explorer.exe via classic process hollowing (ZwUnmapViewOfSection + VirtualAlloc + ZwWriteVirtualMemory) and layers anti-VM, anti-debug, and code-obfuscation checks before establishing HTTP-based C2 to download and execute additional payloads. A 2022 technical writeup by REXor documents the injection chain in detail alongside a live C2 IP/domain list and ten sample SHA256 hashes.
How SmokeLoader Backdoor/Loader works
SmokeLoader (aliases: Smoke Bot, Dofoil, Sharik) is a criminal loader/backdoor that has been sold and operated on underground forums since 2011 by the developer tracked by CrowdStrike as SMOKY SPIDER, a financially motivated actor believed to operate out of the Russian Federation / Eastern Europe. The malware's core value proposition to its operator and its criminal customers is delivery-as-a-service: SmokeLoader itself has limited built-in capability, and instead focuses on reliably landing on a host, evading analysis, and pulling down whichever second-stage modules (information stealers, ransomware, banking trojans, or additional loaders) the operator or a paying third party wants executed.
The infection chain documented in the primary source begins with a dropper delivered via phishing attachments, drive-by downloads, exploit kits, or bundled with cracked/pirated software (a common PPI "pay-per-install" monetization channel for this actor). On execution, the initial-stage binary spawns a second copy of itself in a suspended state using CreateProcessInternalA/W with the CREATE_SUSPENDED flag, then performs textbook process hollowing against the suspended process image: it calls ZwUnmapViewOfSection to remove the original (legitimate) image from the process's address space, VirtualAlloc/VirtualAllocEx to reserve fresh memory in the target, ZwWriteVirtualMemory/WriteProcessMemory to write the malicious PE image into that space, and ResumeThread to resume execution of the now-hollowed process. In observed builds, explorer.exe is the preferred hollowing target, letting the malicious code execute under a trusted, always-running system process to blend into normal endpoint telemetry.
Before and during this injection sequence, SmokeLoader runs a battery of anti-analysis checks: anti-VM/sandbox detection (T1497.001-class system fingerprinting to identify virtualized analysis environments), anti-debugger checks to detect attached debuggers, and code obfuscation techniques including hidden/indirect call constructions and abuse of the RET instruction to break static disassembly and control-flow-graph reconstruction. Packed sections with abnormally high entropy further frustrate static signature detection. API resolution is deferred at runtime via LoadLibrary + GetProcAddress rather than static import-table linking, denying analysts an easy API-call inventory from the PE header alone.
Once injected and running inside explorer.exe, SmokeLoader establishes command-and-control over HTTP(S), historically favoring encoded/encrypted request and response bodies and, in many campaigns, decoy traffic to legitimate high-reputation domains (e.g., microsoft.com, bing.com) that return HTTP 404 while carrying disguised C2 data in the response body — a technique intended to blend malicious egress into background enterprise web traffic and defeat simple domain-reputation network controls. The 2022 sample set analyzed here communicated with a defined set of C2 IPs and a rotating pool of throwaway domains registered across cheap/free TLDs (.top, .tk, .ga, .ml, .tw, .ru, .co.ug) consistent with the bulletproof-hosting and disposable-domain patterns typical of SMOKY SPIDER's infrastructure.
SmokeLoader's downstream module ecosystem (documented broadly across the vendor/community corpus, not solely this sample) has historically included credential-stealing modules targeting browser-stored credentials and files containing unsecured credentials, local email collection, and the ability to fetch/execute follow-on payloads including information stealers (Lumma, RedLine, Vidar reported in later campaigns) and other loaders. Persistence in documented builds is commonly achieved through Registry Run key / Startup folder placement and, in some builds, Scheduled Task creation, ensuring re-execution across reboots without relying on the injected explorer.exe process alone.
Attribution: MITRE ATT&CK catalogs SmokeLoader as Software S0226; CrowdStrike attributes its development and criminal operation to SMOKY SPIDER, active since at least 2011, financially motivated, distributing the loader itself and reselling execution slots to third-party criminal customers. Malpedia additionally cross-references the UAC-0006 activity cluster (a financially motivated group targeting Ukrainian entities) as an observed operator/user of SmokeLoader builds.
MITRE ATT&CK techniques used in TL-2026-2482
Defense Evasion
T1027.013 Encrypted/Encoded File; T1055.012 Process Hollowing; T1140 Deobfuscate/Decode Files or Information; T1497.001 System Checks
Persistence
T1053.005 Scheduled Task; T1547.001 Registry Run Keys / Startup Folder
Execution
Command and Control
Collection
T1114.001 Local Email Collection
Credential Access
T1552.001 Credentials In Files; T1555.003 Credentials from Web Browsers
Affected products and versions in SmokeLoader Backdoor/Loader
- Microsoft — Windows (all supported desktop versions)
Vulnerable versions: Windows 7 and later, x86/x64
Remediation for SmokeLoader Backdoor/Loader
Immediate actions
- Block the documented C2 IPs (216.128.137.31, 8.209.71.53) and domains at perimeter firewall/DNS layer
- Add the ten published SHA256 hashes to EDR/AV blocklists and hunt for prior execution
- Hunt for explorer.exe processes exhibiting anomalous outbound HTTP connections or unexpected child processes/memory regions inconsistent with the legitimate binary
- Isolate and reimage any host confirmed to have executed a matching sample
Workarounds
- Block outbound access to newly-registered/low-reputation TLDs (.top, .tk, .ga, .ml, .co.ug) commonly abused for disposable SmokeLoader C2 domains where not required for business function
Longer-term hardening
- Deploy EDR with kernel-level API hooking/ETW-based detection for ZwUnmapViewOfSection, NtWriteVirtualMemory, and VirtualAllocEx sequences targeting explorer.exe or other long-lived system processes
- Enable memory-scanning/behavioral detection for process hollowing patterns (RWX memory allocation in a process whose original image was unmapped)
- Deploy network detection for HTTP beacons disguised as traffic to high-reputation domains returning anomalous 404 response bodies
- Restrict execution of unsigned binaries from user-writable directories (Temp, Downloads, AppData) via application control policy
Timeline of SmokeLoader Backdoor/Loader
- SmokeLoader (Smoke Bot) first made available for sale on underground criminal forums by its developer, later tracked by CrowdStrike as SMOKY SPIDER.
- Malwarebytes Labs publishes 'Smoke Loader - downloader with a smokescreen still alive,' documenting continued active use of the loader years after initial release.
- CrowdStrike's 2020 Global Threat Report names SMOKY SPIDER as the criminal developer/operator behind SmokeLoader (Smoke Bot).
- Ten SHA256 sample hashes and associated C2 infrastructure (2 IPs, 15 domains across .top/.tk/.ga/.ml/.tw/.ru/.co.ug TLDs) disclosed alongside the technical writeup.
- REXor publishes a technical analysis of a SmokeLoader sample detailing its process-hollowing injection into explorer.exe, anti-VM/anti-debug checks, and a live C2 IP/domain list with ten SHA256 sample hashes.
- TL-Intel Harness compiles cross-referenced research on the sample, corroborating IOCs, ATT&CK mapping (S0226), and Smoky Spider/UAC-0006 attribution against MITRE, Malpedia, CrowdStrike, and Huntress sources.
Sources cited for SmokeLoader Backdoor/Loader
- SmokeLoader
- Quick-Analysis: SmokeLoader.md
- Smoke Loader, Software S0226
- SmokeLoader (Malware Family)
- SMOKY SPIDER (Threat Actor)
- Smoky Spider Adversary Profile
- SmokeLoader Malware: Analysis, Detection, Removal
- Smoke Loader - downloader with a smokescreen still alive
- NJCCIC Threat Profile: Smoke Loader
- Deep Analysis of SmokeLoader
More in malware
- Compromised HBO Max Reddit Account Distributes ClickFix Malware in "PasteSwitch" Cross-Platform Malvertising Campaign
- Multi-Stage Cobalt Strike Loader Deploys Stageless Beacon via Anti-Sandbox .NET Chain
- Access-Code-Gated Phishing Chain Delivers Vidar Infostealer via DocuSign Impersonation
- ScarfaceStealer: Electron-Delivered Infostealer with Sandbox-Scoring Evasion and Smart-Contract C2
- Gigabud Android Banking Trojan Clones Banking Apps via Hidden Work Profile (Vwork/GoldFactory)
Detection coverage for TL-2026-2482
As of 2026-09-13, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2482 across Splunk SPL, Microsoft KQL and Sigma, covering 29 indicator(s) of compromise. The whole corpus is readable without an account; a free account unlocks full detection query text in Splunk SPL, Microsoft KQL and Sigma; paid tiers add raw indicator values, correlation and the MCP server. Threadlinqs MCP server · View plans.