News: 0185142266

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Windows Backdoor 'Sleepwalker' Hides in Memory Until Activated by a 'Magic Packet' (theregister.com)

(Tuesday August 25, 2026 @11:00AM (BeauHD) from the never-before-seen dept.)


"The Register has a story about a Windows backdoor that [1]waits silently in memory for a 'magic packet' before springing into action ," writes Slashdot reader [2]fred133 . "No outgoing traffic, just waiting..." From the report:

> Like a sleeper cell awaiting activation, a never-before-seen Windows backdoor dubbed Sleepwalker waits silently in memory for one specifically crafted network packet to wake it up and deliver commands using the malware's 23-instruction language. The commands can do everything from running code directly in memory to moving data off the computer. Malware researcher Dominik Reichel discovered the passive backdoor, which also has its own command language, and detailed Sleepwalker in a technical analysis on Monday. "What makes it worth writing up is what that packet carries: not a readable command, but a short program written in a command language of the backdoor's own design," Reichel [3]said . "Its 23 instructions cover scheduling, several ways to move data, staged file delivery and running code directly in memory. Recovering the encryption key is not enough to understand one of these programs. The internal command language must be reverse engineered as well."

>

> In addition to having its own command language, it's also notable that the remote host can be a VMware VMCI target instead of a normal network address. "Taken as a whole, the approach here is consistent with a targeted, well-resourced operation rather than an opportunistic one," Reichel wrote. The malware, hidden inside a 64-bit Windows DLL file, impersonates Microsoft's dpapi.dll, part of Windows' data protection API for protecting sensitive data. It exports the same seven functions as the real dpapi.dll, but attempts to forward calls to a file named dpapisvc.dll, which is not a real Windows component. The file also has a forged ESET Management Agent version resource, and loads via side-loading into ERAAgent.exe, the Windows executable for ESET Management Agent. After confirming that its host process is named ERAAgent.exe, Sleepwalker goes to sleep inside the computer's memory, which also helps it remain hidden from traditional anti-virus tools.

>

> Unlike most backdoors, which call back to an attacker-controlled command-and-control (C2) server and start receiving commands, Sleepwalker lies in wait, checking every packet that passes through the network looking for a specific pattern - this is called a magic packet. Once it sniffs out a packet that matches the exact pattern, the backdoor decrypts the data and treats it as a command. "Because the backdoor never sends anything out on its own and does not open any obvious listening port by default, tools that watch for connections to known-bad domains or unusual outbound traffic will not see anything unusual," Reichel wrote. "The absence of outbound connections to known-bad infrastructure does not rule out an infection, either. A machine can be fully compromised by this backdoor while producing nothing at all for a network monitor to flag."



[1] https://www.theregister.com/security/2026/08/24/you-dont-want-this-sleepwalker-backdoor-on-your-windows-machine/5292021

[2] https://slashdot.org/~fred133

[3] https://r136a1.dev/2026/08/24/sleepwalker-a-passive-backdoor-with-its-own-command-language/#conclusion



Help Me Understand (Score:2)

by SlashbotAgent ( 6477336 )

It sounds very similar to how a Wake-on-LAN trigger works. Based on how that works, it requires another machine on the LAN with a foothold to send the magic packet?

So, we're looking for the machine with the foothold and anything that even vaguely related to that PoS ESET?

Re:Help Me Understand (Score:5, Informative)

by Errol backfiring ( 1280012 )

Maybe, maybe not. Wake-on-LAN works from a remote system, without an outgoing request first. If this malware is so sophisticated, it could wait for any other program to call to the outside world. If the attacker has access to the network, it can inject something in the answer, thus bypassing a firewall. This could trigger the action and be otherwise seen as a defective network package, which is just asked for again. Nobody would notice a defective network package. This sounds quite scary.

Re:Help Me Understand (Score:4, Informative)

by Bert64 ( 520050 )

This.

It doesn't need to be a special packet, it could be a specific pattern hiding inside any packet received by the host. You don't need the ability to send traffic directly to the target, just the ability to interact with a traffic flow in or out of the system.

Re:Help Me Understand (Score:4, Informative)

by clovis ( 4684 )

> It sounds very similar to how a Wake-on-LAN trigger works. Based on how that works, it requires another machine on the LAN with a foothold to send the magic packet?

> So, we're looking for the machine with the foothold and anything that even vaguely related to that PoS ESET?

The real problem here is the eternal Windows problem of dll side-loading.

That allows a system dll to be impersonated and evade sfc scannow protection. How it gets activated is by far less of a problem than that the bad code is already resident in memory waiting for instruction.

Also, there's the problem that someone has gotten the privilege to put it there.

Backdoor is badly used term (Score:3)

by evanh ( 627108 )

A backdoor implies it is designed into the system. Ie: It was M$'s doing, and they wanted it there.

I'm curious. (Score:4, Interesting)

by fuzzyfuzzyfungus ( 1223518 )

This sounds like it was written by someone who actually knows what they are doing, so I assume that they know better than I; but I am surprised to hear that it is impersonating a system dll; since (in all comparatively recent windows versions) system components are signed. Absolutely tons of fuckery you can do to them and around them; but if dpapi.dll doesn't have a signature that checks out the mechanisms that try to keep OSes up and running on marginal hardware subject to random power loss will likely eventually object and attempt a repair, even if there isn't any more paranoid EDR tooling in place.

Is the on-disk copy of dpapi.dll untouched and only the in-memory instance tampered with?

Re: (Score:3)

by sabbede ( 2678435 )

It's sideloaded, in that the fake dpapi.dll is placed in ESET's folder next to the executables so they use it instead of the one in system32. It doesn't look like it's signed, but instead has vendor info in there to trick ESET.

Sideloading is the same trick Reshade uses to inject shaders.

so (Score:2)

by awwshit ( 6214476 )

You get infected by running ESET?

Still looking for the glorious results of my misspent youth. Say, do you
have a map to the next joint?