A previously unseen Windows backdoor called Sleepwalker hides silently in memory and waits for a single specially crafted network packet before it will accept commands, according to a technical analysis by malware researcher Dominik Reichel published this week and reported by The Register on 2026-08-24. Unlike typical malware that repeatedly calls home to a command server, Sleepwalker stays passive, making it harder for security tools that watch for suspicious outbound connections to spot.
Sleepwalker's design, which includes a custom 23-instruction command language, AES-256-CCM encryption, and disguise as a legitimate Windows DPAPI component, points to a targeted, well-resourced operation rather than mass-distributed malware, per Reichel's analysis.
Key takeaways
- Sleepwalker is a passive Windows backdoor that stays dormant until it receives a specific 'magic packet' over the network.
- It masquerades as dpapi.dll, a legitimate Windows component, and side-loads into ESET Management Agent's ERAAgent.exe process.
- Once triggered, it decrypts AES-256-CCM-protected commands from a 23-instruction language covering data theft, in-memory code execution, and payload delivery.
- The malware can communicate over TCP, UDP, ICMP, SMB named pipes, and VMware VMCI, with an inactive DNS trigger mechanism also present.
- Researcher Dominik Reichel has released IOCs, a YARA rule, and a read-only PowerShell scanner for defenders to check for the known sample.
Affected
What is the Sleepwalker Windows backdoor?
Sleepwalker is a passive Windows backdoor documented by malware researcher Dominik Reichel and reported by The Register on 2026-08-24. Unlike beaconing malware that repeatedly checks in with a command server, Sleepwalker sits quietly in memory and only reacts once it receives a specific, specially crafted network packet, described as a 'magic packet', that tells it to wake up.
Once triggered, the backdoor decrypts attacker instructions using AES-256-CCM and executes them through a custom 23-instruction command language. Per the analysis, these commands cover moving data off the machine, receiving additional malware, and running code directly in memory rather than dropping traditional files to disk.
Why it matters for detection
Most detection approaches flag malware by watching for an infected machine repeatedly contacting a suspicious external address. Sleepwalker's passive design sidesteps that pattern: it produces no regular outbound traffic to monitor until the trigger packet arrives, so a compromised host can look clean on a network dashboard for an extended period.
Reichel told researchers Sleepwalker's engineering is more consistent with a targeted, well-funded operation than malware spread widely for opportunistic infection, though no attribution has been confirmed.
How does the dpapi.dll disguise work?
The backdoor ships as a 64-bit Windows DLL named dpapi.dll, the same filename as a legitimate Microsoft Windows Data Protection API component, which can make the malicious copy harder to distinguish from a genuine system file at a glance.
Sleepwalker also embeds fake metadata claiming it belongs to ESET Management Agent and uses DLL side-loading: it checks whether it has been loaded by ERAAgent.exe, the legitimate ESET Management Agent executable, and stays inactive if it isn't running inside that process. When the check passes, it spawns a background process, allocates memory for incoming instructions, and begins monitoring traffic for the activation packet.
- Supports TCP, UDP, and ICMP as trigger channels
- Can communicate via SMB named pipes for lateral movement
- Includes VMware VMCI support for guest-to-host communication inside virtual machines
- Contains an inactive DNS-based trigger mechanism not enabled in the analyzed sample
Who is affected and what is not yet known?
Only one Sleepwalker sample has been analyzed to date, and researchers have not identified confirmed victims, targeted sectors, or specific countries affected. The sample reportedly contains several weaknesses, suggesting it may be an early or still-developing version of the malware rather than a mature, widely deployed tool.
Because the sample requires ESET Management Agent's ERAAgent.exe process to activate, organizations running that legitimate security tool alongside unmanaged or unverified DLLs in the same directory face a plausible, though not yet confirmed, exposure path.
How can security teams detect Sleepwalker?
Reichel has released indicators of compromise, a YARA detection rule, and a read-only PowerShell scanner to help defenders check for the specific Sleepwalker sample analyzed so far. Security teams can run the scanner against endpoints, particularly those running ESET Management Agent, to check for the malicious dpapi.dll and its side-loading behavior.
- Search for dpapi.dll files outside the expected system location or with mismatched signing
- Run the published YARA rule against endpoint file repositories
- Use the PowerShell scanner to identify the known sample
- Monitor ERAAgent.exe process loads for unexpected DLL side-loading
What should IT teams watch next?
Because only a single sample exists and it appears to be an early build, further Sleepwalker variants could emerge with the DNS trigger enabled or with the identified weaknesses fixed. Defenders should watch for updated research from Reichel or other analysts, and revisit their DLL side-loading detection coverage generally.
Timeline
Impact & actions
Sleepwalker lets an attacker run code, exfiltrate data, and pull in extra payloads on a compromised Windows host while producing almost none of the outbound beaconing that network monitoring tools normally flag.
Security: Because Sleepwalker avoids regular command-and-control callbacks, detection tools that rely on spotting recurring outbound connections to a suspicious server are less likely to catch an infected host before the attacker sends the activation packet.
Privacy: Once active, the 23-instruction command set can move data off the infected machine, giving an attacker access to whatever files or information the compromised account can reach.
Recommended actions · Medium urgency
- 1Run Dominik Reichel's published YARA rule against endpoints, especially those running ESET Management Agent
- 2Use the read-only PowerShell scanner to check for the known Sleepwalker sample
- 3Check IOCs released with the research against network and endpoint logs
- 4Review integrity of dpapi.dll and ERAAgent.exe on systems where ESET Management Agent is deployed
Technical details
- Attack vector
- DLL side-loading: a malicious dpapi.dll is planted so that ERAAgent.exe (ESET Management Agent) loads it instead of, or alongside, a genuine Windows component; the backdoor stays passive until a specially crafted 'magic packet' arrives over the network.
- Affected versions
- Microsoft Windows (64-bit)
Mitigations
- Verify the integrity and signing of dpapi.dll on systems running ESET Management Agent
- Monitor for unexpected DLL side-loading into ERAAgent.exe
Response
Customer guidance
Reichel's published IOCs, YARA rule, and read-only PowerShell scanner let defenders check whether the specific analyzed Sleepwalker sample is present on their systems, though only one sample has been examined so far.
FAQ
What is the Sleepwalker Windows backdoor?
Sleepwalker is a previously undocumented Windows backdoor that disguises itself as dpapi.dll and stays dormant in memory until it receives a specially crafted 'magic packet' over the network.
How does Sleepwalker avoid detection?
Instead of repeatedly contacting a command server like typical malware, it passively monitors network traffic and only activates its encrypted command channel after receiving a specific trigger packet.
How does Sleepwalker get onto ESET Management Agent processes?
It uses DLL side-loading, planting a malicious dpapi.dll that ERAAgent.exe loads; the backdoor checks that it is running inside ERAAgent.exe before it stays active.
Which network protocols can Sleepwalker use?
The analyzed sample can communicate over TCP, UDP, ICMP, SMB named pipes, and VMware VMCI, with an inactive DNS-based trigger mechanism also found in the code.
Do we know who is behind Sleepwalker or who it targeted?
No. Researchers have analyzed only one sample and have not identified the operators, victims, sectors, or countries involved.
How can defenders check for Sleepwalker?
Researcher Dominik Reichel published IOCs, a YARA rule, and a read-only PowerShell scanner that can identify the specific analyzed sample.
The bottom line
Sleepwalker is a newly documented passive Windows backdoor that hides as a fake dpapi.dll inside ESET Management Agent's ERAAgent.exe and only responds after a hidden network trigger.
What happens next
What to do






