Skip to main content
Mallory
MalwareUsed by 3 actorsExploits 1 CVE

SprySOCKS

SprySOCKS is a backdoor malware family previously documented as Linux malware and later observed in previously undocumented Windows variants named WIN_DRV and WIN_PLUS. ESET attributed the Windows variants with high confidence to the China-linked FishMonger espionage group, also tracked as Earth Lusca, TAG-22, Aquatic Panda, and Red Dev 10, and assessed FishMonger to be operated by the Chengdu-based contractor i-SOON under the broader Winnti umbrella. Observed activity occurred in 2023 and 2024 and primarily targeted government organizations in Honduras, Taiwan, Thailand, and Pakistan.

The Windows variants retain core elements of the Linux version, including hardcoded command-and-control configuration, message format, encryption keys and algorithms, and the HP-Socket communication framework. They support C2 over TCP, UDP, and WebSocket and implement more than 30 commands for system information collection, process enumeration and control, service management, file management, execution, and SOCKS proxying. Both variants were reported as DLLs with original name PrcsServer.dll, exporting a function named Stop, and creating a mutex named prcs-server-run during initialization.

Reported functionality includes keylogging of keystrokes, clipboard contents, and active window titles when enabled by %appdata%\Microsoft\Vault\lgf.dat. Logged data is stored in %appdata%\Microsoft\Vault\lg.dat and encrypted with single-byte XOR key 0x44.

WIN_DRV adds kernel-level stealth and rootkit-like capabilities. It uses a kernel driver named RawWNPF, loaded via a DriverLoader component, to hide network connections, processes, files, and registry keys, and to divert specially crafted TCP traffic received on any open port to the hidden backdoor port. Reported infection-chain details for WIN_DRV include DLL side-loading via ApphostRagistreationVerifier.exe, tpsvc.dll, and a malicious tpsvcloc.dll loader; AES-128-ECB decryption with hardcoded key uXQLESMXGaRMs6BL; injection into svchost.exe using process doppelgänging; persistence via a scheduled task named ApphostRagistreationVerifier and optionally Image File Execution Options for vds.exe; and loading of the RawWNPF driver from memory. ESET reported the DriverLoader driver was signed with a leaked certificate from the GitHub PastDSE project. A WIN_DRV archive was reportedly uploaded to VirusTotal in April 2024 as klelam00007.zip.

WIN_PLUS was described as a simpler backdoor variant. It used a first-stage loader named VSPMsg.dll installed as a Windows Print Processor under HKLM\SYSTEM\ControlSet001\Control\Print\Environments\Windows x64\Print Processors\VSPMsg, with an encrypted container stored at C:\Windows\System32\spool\drivers\color\config.dat. ESET reported a hardcoded C2 at 207.148.78[.]36 using ports 443/TCP, 53/UDP, and 80/WebSocket.

The malware family has also been described as based on the open-source Windows RAT Trochilus and as sharing characteristics with RedLeaves. Separate reporting cited code reuse linking SprySOCKS to the broader Winnti lineage, including PWNLNX, RedXOR, AzazelFork, and Melofee. ESET also noted limited indications that some SprySOCKS attack scenarios may have involved a UEFI bootkit component possibly exploiting CVE-2023-24932, although the available information does not establish that element conclusively.

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

EXPLOITED CVES

Vulnerabilities exploited

1 CVE Mallory has correlated with this family across public research and vendor advisories. Each row links to the full Mallory page for that vulnerability.

1 CVES
CVE-2023-24932Windows Boot Manager Secure Boot Security Feature Bypass

Cybersecurity researchers have flagged two previously undocumented Windows variants of what was believed to be a Linux-only backdoor called SprySOCKS. "The Windows variants discovered are internally marked as WIN_DRV and WIN_PLUS," ESET said.

via the hacker newsthehackernews.com
THREAT ACTORS

Groups observed using it

3 distinct threat actors attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
APT41

Cybersecurity researchers have flagged two previously undocumented Windows variants of what was believed to be a Linux-only backdoor called SprySOCKS. "The Windows variants discovered are internally marked as WIN_DRV and WIN_PLUS," ESET said.

via the hacker newsthehackernews.com
Fishmonger

Cybersecurity researchers have flagged two previously undocumented Windows variants of what was believed to be a Linux-only backdoor called SprySOCKS. "The Windows variants discovered are internally marked as WIN_DRV and WIN_PLUS," ESET said.

via the hacker newsthehackernews.com
Red Dev 10

ESET researchers have discovered two as-yet undocumented Windows variants of SprySOCKS, a previously Linux-only backdoor reportedly used by FishMonger... The Windows variants discovered are internally marked as WIN_DRV and WIN_PLUS.

via eset welivesecurity blogwelivesecurity.com
MITRE ATT&CK

Techniques & procedures

45 distinct techniques documented for this family, organized by ATT&CK tactic.

Reconnaissance

2 techniques
T1590.005IP AddressesEvidence1

SprySOCKS can collect information about the compromised device, including information about network interfaces and assigned IP addresses.

T1592.004Client ConfigurationsEvidence1

SprySOCKS can collect information about the compromised device, including: computer name, OS version, information about memory and CPU, current privileges, system language and version, current time, and more.

Resource Development

1 technique
T1587.001MalwareEvidence1

FishMonger has developed custom malware for its operations, including the SprySOCKS backdoor.

Execution

4 techniques
T1053.005Scheduled TaskEvidence2

The attack chain makes use of an as-yet-undetermined initial access pathway to drop a batch script, which then creates and executes a scheduled task responsible for triggering a DLL side-loading chain

T1059.003Windows Command ShellEvidence1

SprySOCKS can launch an interactive cmd.exe command shell, which allows the attackers to execute commands remotely on the compromised machine.

T1106Native APIEvidence1

FishMonger has used Windows APIs to execute code within a victim’s system.

T1569.002Service ExecutionEvidence1

SprySOCKS abuses system services for both one-time and persistent execution.

Persistence

4 techniques
T1053.005Scheduled TaskEvidence2

The attack chain makes use of an as-yet-undetermined initial access pathway to drop a batch script, which then creates and executes a scheduled task responsible for triggering a DLL side-loading chain

T1205.002Socket FiltersEvidence1

SprySOCKS uses the RawWNPF kernel driver to install packet filters capable of redirecting any inbound TCP traffic to the configured local port if a special magic value is detected in the packet.

T1546.012Image File Execution Options InjectionEvidence1

registering the %SystemRoot%\Fonts\ApphostRagistreationVerifier.exe application as a debugger for vds.exe by writing the application’s path into the registry value HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\vds.exe\debugger

T1547.012Print ProcessorsEvidence2

It leverages the Windows Print Spooler service ("spoolsv.exe") as a starting point to execute a first-stage loader that runs as a print processor.

Privilege Escalation

6 techniques
T1053.005Scheduled TaskEvidence2

The attack chain makes use of an as-yet-undetermined initial access pathway to drop a batch script, which then creates and executes a scheduled task responsible for triggering a DLL side-loading chain

T1055Process InjectionEvidence1

It's designed to inject and run a SprySOCKS loader into a newly created "svchost.exe" process to launch the backdoor.

T1055.013Process DoppelgängingEvidence1

the loader spawns a new svchost.exe process ... and injects the backdoor’s shellcode into the process by using the process doppelgänging technique.

T1134.002Create Process with TokenEvidence1

the loader spawns a new svchost.exe process using CreateProcessAsUserW with a token obtained from spoolsv.exe

T1546.012Image File Execution Options InjectionEvidence1

registering the %SystemRoot%\Fonts\ApphostRagistreationVerifier.exe application as a debugger for vds.exe by writing the application’s path into the registry value HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\vds.exe\debugger

T1547.012Print ProcessorsEvidence2

It leverages the Windows Print Spooler service ("spoolsv.exe") as a starting point to execute a first-stage loader that runs as a print processor.

Stealth

14 techniques
T1027.007Dynamic API ResolutionEvidence1

SprySOCKS components use dynamic API resolution.

T1027.013Encrypted/Encoded FileEvidence1

SprySOCKS components are stored in an AES-encrypted file on the victim’s drive.

T1055Process InjectionEvidence1

It's designed to inject and run a SprySOCKS loader into a newly created "svchost.exe" process to launch the backdoor.

T1055.013Process DoppelgängingEvidence1

the loader spawns a new svchost.exe process ... and injects the backdoor’s shellcode into the process by using the process doppelgänging technique.

T1070.004File DeletionEvidence1

The SprySOCKS loader removes original files from the deployment directory after copying them and setting up persistence.

T1070.009Clear PersistenceEvidence1

SprySOCKS loader removes a service registry value associated with the previously installed malicious minifilter driver after executing the driver.

T1134.002Create Process with TokenEvidence1

the loader spawns a new svchost.exe process using CreateProcessAsUserW with a token obtained from spoolsv.exe

T1140Deobfuscate/Decode Files or InformationEvidence1

SprySOCKS loader decrypts the SprySOCKS backdoor from an encrypted file. Additionally, most of the strings in the SprySOCKS components are encrypted.

T1205.002Socket FiltersEvidence1

SprySOCKS uses the RawWNPF kernel driver to install packet filters capable of redirecting any inbound TCP traffic to the configured local port if a special magic value is detected in the packet.

T1497Virtualization/Sandbox EvasionEvidence1

SprySOCKS uses several anti-emulation techniques to prevent automated analysis by emulators or sandboxes.

T1564Hide ArtifactsEvidence1

WIN_DRV has also been found to utilize kernel drivers to conceal the malware's network connections, processes, files, and registry keys.

T1564.001Hidden Files and DirectoriesEvidence1

WIN_DRV has also been found to utilize kernel drivers to conceal the malware's network connections, processes, files, and registry keys.

T1564.009Resource ForkingEvidence1

WIN_DRV has also been found to utilize kernel drivers to conceal the malware's network connections, processes, files, and registry keys.

T1622Debugger EvasionEvidence1

SprySOCK’s RawWNPF driver uses the KdDisableDebugger function to disable the kernel debugger, if active.

Credential Access

1 technique
T1056.001KeyloggingEvidence1

SprySOCKS implements a keylogger.

Discovery

9 techniques
T1007System Service DiscoveryEvidence2

This includes collecting system information, launching an interactive console, enumerating processes, getting C2 communication details, listing all services...

T1010Application Window DiscoveryEvidence1

SprySOCKS retrieves the active foreground window name as a part of its keylogging functionality.

T1057Process DiscoveryEvidence1

the Windows versions support more than 30 commands to facilitate system information collection, process enumeration, service management, and file system operations.

T1082System Information DiscoveryEvidence2

the Windows versions support more than 30 commands to facilitate system information collection, process enumeration, service management, and file system operations.

T1083File and Directory DiscoveryEvidence2

the Windows versions support more than 30 commands to facilitate system information collection, process enumeration, service management, and file system operations.

T1124System Time DiscoveryEvidence1

SprySOCKS can collect information about the compromised device, including current system time.

T1497Virtualization/Sandbox EvasionEvidence1

SprySOCKS uses several anti-emulation techniques to prevent automated analysis by emulators or sandboxes.

T1614.001System Language DiscoveryEvidence1

SprySOCKS can collect information about the compromised device, including system language.

T1622Debugger EvasionEvidence1

SprySOCK’s RawWNPF driver uses the KdDisableDebugger function to disable the kernel debugger, if active.

Collection

2 techniques
T1056.001KeyloggingEvidence1

SprySOCKS implements a keylogger.

T1115Clipboard DataEvidence1

SprySOCKS logs clipboard data, along with the captured keystrokes, as a part of its keylogging functionality.

Command and Control

12 techniques
T1008Fallback ChannelsEvidence1

In addition to the TCP communication channel, SprySOCKS can contact its C&C using UDP and WebSocket channels.

T1071Application Layer ProtocolEvidence1

Both come with a hard-coded C&C [command-and-control] configuration and support communication over TCP, UDP, and WebSocket protocols.

T1090.001Internal ProxyEvidence1

the variant enables TCP traffic diversion that allows the malware operators to send commands to the backdoor through a random TCP port on the victim's device without exposing the backdoor's actual listening port in the network traffic.

T1090.003Multi-hop ProxyEvidence1

initialising a SOCKS proxy

T1095Non-Application Layer ProtocolEvidence1

SprySOCKS uses nonstandard protocols to communicate with the C&C.

T1105Ingress Tool TransferEvidence1

uploading/downloading files

T1132.001Standard EncodingEvidence1

SprySOCKS uses base64 encoding in its custom C&C communication protocol.

T1205.002Socket FiltersEvidence1

SprySOCKS uses the RawWNPF kernel driver to install packet filters capable of redirecting any inbound TCP traffic to the configured local port if a special magic value is detected in the packet.

T1219Remote Access ToolsEvidence1

This includes collecting system information, launching an interactive console... initialising a SOCKS proxy, uploading/downloading files, and running existing files.

T1571Non-Standard PortEvidence1

SprySOCKS uses nonstandard ports to communicate with the C&C.

T1573.001Symmetric CryptographyEvidence1

SprySOCKS encrypts data sent to, and decrypts data received from, the C&C with 128-bit AES.

T1665Hide InfrastructureEvidence1

SprySOCKS’s RawWNPF driver hides the backdoor’s active connections from being enumerated when using network tools such as netstat.exe.

Exfiltration

1 technique
T1041Exfiltration Over C2 ChannelEvidence1

SprySOCKS can upload various files from the compromised system to the C&C.

Other

1 technique
T1562.004Disable or Modify System FirewallEvidence1

SprySOCKS adds a firewall rule allowing any inbound traffic sent to the backdoor’s listening port.

INDICATORS OF COMPROMISE

IOCs tracked for this family

3 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.

View more in app
Network
2 tracked

IPs, domains, and DNS infrastructure linked to this family.

Other
1 tracked

Other indicator types observed in public reporting.

TypeValueLatest sighting
ip.v4●●●●●●●●●●●●View more in apptoday
cidr.v4●●●●●●●●●●●●View more in apptoday
ip.v4●●●●●●●●●●●●View more in apptoday
ACTIVITY FEED

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

the hacker newsNews
Jun 16, 2026
China-Linked SprySOCKS Backdoor Expands to Windows with Driver-Based Stealth

A cross-platform backdoor originally documented as Linux-only, now observed in Windows variants. It supports more than 30 commands for system information collection, process enumeration, service management, file system operations, interactive console access, SOCKS proxy initialization, file upload/download, and command execution. The WIN_DRV variant uses kernel drivers for stealth and TCP traffic diversion, while WIN_PLUS uses the Windows Print Spooler service and process injection to launch the backdoor.

Read more
govinfosecurityNews
Jun 16, 2026
Chinese Hacking Firm Upgrades With New Windows Backdoor

A cross-platform backdoor originally identified on Linux and now observed in undocumented Windows variants. It provides extensive command-and-control functionality, supports TCP, UDP, and WebSocket communications, and uses a kernel-level rootkit/driver to hide network connections, processes, files, and registry keys while enabling covert command delivery through random TCP ports.

Read more
bleeping computerNews
Jun 16, 2026
Windows version of SprySOCKS Linux malware used to attack govt orgs

SprySOCKS is a backdoor malware family linked in the content to Earth Lusca/FishMonger. The Windows variants support TCP, UDP, and WebSocket communications, more than 30 C2 commands, system information collection, process and service management, file operations, SOCKS proxying, client/server operation, and logging of keystrokes, clipboard content, and active window titles. The WIN_DRV variant adds kernel-level stealth and rootkit-like capabilities, including hiding processes, network connections, files, and Registry persistence entries, plus TCP traffic diversion to conceal the real listening port.

Read more
eset welivesecurity blogNews
Jun 16, 2026
FishMonger’s arsenal upgraded: SprySOCKS for Windows

A cross-platform backdoor used for cyberespionage that supports TCP, UDP, and WebSocket C2, system information collection, process and service management, file operations, SOCKS proxying, keylogging, clipboard capture, and command execution. The WIN_DRV variant adds kernel-driver-based stealth to hide files, processes, registry keys, and network connections, and can divert TCP traffic to a hidden listening port.

Read more
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching3

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution3

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities1

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping45

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.