SLEEPWALKER Backdoor Activates on Windows via Single Custom Encrypted Packet

SLEEPWALKER is a backdoor for Windows designed to remain inactive until it receives a single custom encrypted network packet. When the packet arrives, the implant decrypts and executes its own bytecode, reducing network footprint and complicating detection.

The backdoor follows an unusual approach on Windows: it does not call home, does not maintain a persistent channel, and avoids the typical beaconing that often reveals malware families. It stays silent, resident in memory, and only activates when it receives one specially crafted network packet. That trigger is enough to start the implant and execute actions without any prior communication from the infected system.

The core of the design lies in how it interprets commands. Instead of text commands or easily inspectable structures, the packet carries a small program in bytecode belonging to a proprietary language with 23 instructions. This mini language allows chaining tasks, moving data, receiving additional stages, and executing code in memory. The goal is to minimize network indicators until the last moment and move logic into a format less obvious to traditional inspection tools.

The camouflage also focuses on discretion. The analyzed sample presents itself as a 64-bit DLL that impersonates dpapi.dll and exports the same seven functions expected from the name, while also falsifying version metadata to appear legitimate, including an appearance linked to ESET. The implant seeks to load via DLL side-loading inside ERAAgent.exe, the executable of the ESET Management Agent used in ESET PROTECT and ESET PROTECT On-Prem deployments. To strengthen control, it only wakes if the host process matches the expected one.

Internal configuration is protected with AES-256-CCM and, in the described case, reduces to a bootstrap instruction that orders indefinite monitoring of network interfaces. From there it can inspect traffic in promiscuous mode and evaluate packets at raw content level, allowing the trigger to be hidden inside IP traffic that might appear routine. An alternative channel for transporting triggers via DNS queries exists but was not activated in the sample.

The backdoor supports several transports for communication and task delivery, including TCP, UDP, ICMP, SMB named pipes, and a VMware VMCI channel between guest and host. A delicate detail: to facilitate unauthenticated access to named pipes, the malware can modify Windows registry values such as EveryoneIncludesAnonymous and NullSessionPipes, lowering the host's security posture. These changes require local administrator privileges, and the analyzed code does not itself confirm a privilege-escalation path.

No confirmed victims, sectors, countries, or attributed infrastructure have been identified, and the public analysis is based on a single sample without associated incident telemetry. Nevertheless, the approach fits targeted operations: it reduces network footprint, avoids dependence on a fixed C2, and can wait for the right moment to activate.

Immediate defensive measures include auditing endpoints with ESET Management Agent and checking for an unexpected dpapi.dll in the same directory as ERAAgent.exe. Analysts should also look for dpapisvc.dll next to the executable, a name that does not correspond to a standard Windows component. Researchers have published YARA rules and read-only scanning utilities to confirm matches by hash and characteristic artifacts. If activity is suspected, review and correct the values of EveryoneIncludesAnonymous and NullSessionPipes against a baseline. Hardening DLL loading and trimming the side-loading surface with directory integrity controls and policies that limit loads from unexpected paths are also recommended.