Snake
Snake, also referred to as Uroburos, is a highly sophisticated cyber-espionage malware platform associated with the Russian FSB, specifically Center 16, and publicly linked to the Turla/Secret Blizzard intrusion set. It has been described as a premier long-term intelligence collection tool and has been used against sensitive targets and Western interests. Public reporting states that Snake implants have existed for Windows, Linux, and macOS.
The malware is notable for a covert global peer-to-peer architecture in which compromised machines can act as relay nodes to proxy traffic and disguise operator communications. Its command-and-control uses custom protocols over TCP, UDP, and ICMP, with encrypted and fragmented communications designed to hinder detection and collection. Reported cryptographic features include a Diffie-Hellman key exchange combined with a pre-shared key for the top C2 layer. Uroburos/Snake also used DNS-like encoding tricks by adding extra characters to encoded strings to mimic legitimate DNS requests.
On Windows, Snake/Uroburos has been reported to use a kernel-mode component and a user-mode component, with named pipes used to move data between them. It uses a custom packer. Configuration material for its kernel driver and loader can be stored in an encrypted blob in the Registry, commonly under HKLM\SOFTWARE\Classes.wav\OpenWithProgIds, which contains material such as an AES key, IV, and paths for the kernel driver and loader. Reporting also states that Uroburos can query this Registry location to decrypt and load its kernel driver and kernel driver loader. The Uroburos Queue file has been described as containing embedded executables, key material, communication channels, and modes of operation.
Operational artifacts and behaviors associated with Snake in the provided content include creation of a WerFaultSvc service pointing to Werfault.exe under WinSxS for persistence, creation of comadmin.dat in %WINDIR%\System32\Com as part of installation involving a kernel driver and custom DLL, and creation of GUID-like .crmlog files in %WINDIR%\Registration. Splunk detections in the content specifically tie these artifacts to Snake malware activity.
The malware has been the subject of major public reporting and disruption efforts, including Operation MEDUSA and CISA hunting guidance published in 2023. The content consistently links Snake/Uroburos to Turla/Secret Blizzard and to Russian state espionage operations.
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.
Groups observed using it
1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
The cyberspies have been associated with a wide array of attacks against Western interests over the years, including the Snake cyber-espionage malware botnet that was recently disrupted in an international law enforcement operation titled Operation MEDUSA.
Techniques & procedures
29 distinct techniques documented for this family, organized by ATT&CK tactic.
Initial Access
3 techniques"IRON HUNTER tactics include strategic web compromises..."
"IRON HUNTER tactics include... fake software update files..."
"IRON HUNTER tactics include... themed spearphishing lures..."
Execution
2 techniquesDuring the 2016 Ukraine Electric Power Attack, Sandworm Team used the xp_cmdshell command in MS-SQL. During the 2025 Poland Wiper Attacks, the adversaries leveraged PsExec to run cmd.exe commands on multiple victim machines. Numerous malware families and groups are described as using cmd.exe, cmd /c, Windows command shell, or command-line interfaces to execute commands, payloads, reconnaissance, persistence, cleanup, and ransomware actions.
The following analytic detects the creation of a new service named WerFaultSvc with a binary path in the Windows WinSxS directory... This behavior is significant because it indicates the presence of Snake malware, which uses this service to maintain persistence by blending in with legitimate Windows services.
Persistence
3 techniquesMany malware families store configuration, payloads, encryption keys, C2 addresses, or other operational data in Registry keys, such as QakBot storing configuration in a randomly named subkey under HKCU\Software\Microsoft and PolyglotDuke writing encrypted JSON configuration files to the Registry. | The content repeatedly describes threat actors and malware modifying, creating, deleting, or storing data in Windows Registry keys and values for persistence, configuration storage, defense evasion, credential access, privilege escalation, and execution.
“Sandworm Team used an arbitrary system service to load at system boot for persistence for Industroyer… replaced the ImagePath registry value of a Windows service with a new backdoor binary… [multiple groups/malware] creating a service / installing as a service / modifying service configurations for persistence.”
Privilege Escalation
2 techniques“Sandworm Team used an arbitrary system service to load at system boot for persistence for Industroyer… replaced the ImagePath registry value of a Windows service with a new backdoor binary… [multiple groups/malware] creating a service / installing as a service / modifying service configurations for persistence.”
Stealth
8 techniquesThe content repeatedly describes payloads, strings, configuration files, scripts, URLs, and binaries being obfuscated or encoded using Base64, XOR, RC4, AES, RSA, hex encoding, custom algorithms, and other methods across many malware families and threat actors.
"Sandworm Team used UPX to pack a copy of Mimikatz"; "APT38 has used several code packing methods such as Themida, Enigma, VMProtect, and Obsidium"; "Lazarus Group packed malicious .db files with Themida to evade detection."
Description Generated datasets for Windows Possible Turla Snake Malware Installer in attack range. MITRE ATT&CK Techniques Environment Details Datasets The following datasets were collected during this attack simulation: Snapattack Path: /datasets/attack_techniques/T1027.009/snapattack/snaattack.log
Examples throughout the content include 'encrypted payloads decrypted and executed in memory,' 'encrypts its configuration file,' 'AES-encrypted resource,' 'RC4 encrypted embedded scripts,' and 'payload includes an encrypted main component.'
The content repeatedly describes threat actors and malware deleting files, tools, scripts, logs, droppers, staged data, and artifacts from compromised systems to cover tracks, remove evidence, or self-delete.
The content repeatedly describes malware and threat actors decoding, decrypting, or deobfuscating payloads, strings, configuration data, commands, and C2 traffic prior to execution or use, e.g., 'APT28 macro uses the command certutil -decode to decode contents of a .txt file storing the base64 encoded payload' and 'Action RAT can use Base64 to decode actor-controlled C2 server communications.'
Defense Impairment
1 techniqueMany malware families store configuration, payloads, encryption keys, C2 addresses, or other operational data in Registry keys, such as QakBot storing configuration in a randomly named subkey under HKCU\Software\Microsoft and PolyglotDuke writing encrypted JSON configuration files to the Registry. | The content repeatedly describes threat actors and malware modifying, creating, deleting, or storing data in Windows Registry keys and values for persistence, configuration storage, defense evasion, credential access, privilege escalation, and execution.
Credential Access
1 technique"Those tools include password stealers"
Discovery
4 techniquesThe content repeatedly describes malware and threat actors querying, enumerating, searching, reading, or checking Windows Registry keys and values, e.g., "ADVSTORESHELL can enumerate registry keys," "APT41 queried registry values to determine items such as configured RDP ports and network configurations," and "Reg may be used to gather details from the Windows Registry of a local or remote system at the command-line interface."
The content repeatedly describes malware and threat actors obtaining lists of running processes, using utilities such as tasklist, ps, WMI, Get-Process, CreateToolhelp32Snapshot, EnumProcesses, and similar APIs/commands to enumerate active processes on victim systems.
The content repeatedly describes malware and threat actors collecting host details such as OS version, hostname, architecture, CPU, memory, BIOS, domain, language, and other configuration data; e.g., "APT41 uses multiple built-in commands such as systeminfo and net config Workstation to enumerate victim system basic configuration information."
"...has a command to retrieve metadata for files on disk as well as a command to list the current working directory." / "...can list files and directories." / "...used the following commands... to obtain information about files and directories: dir c:\ >> %temp%\download ..."
Collection
1 techniqueCommand and Control
6 techniques"By infiltrating Turla's network of hacked machines and sending the malware a command to delete itself"
The content repeatedly describes threat actors, malware, and campaigns using HTTP and/or HTTPS for command and control, including examples such as BlackEnergy communicating with C2 over HTTP POST requests and many other families using HTTP/S for C2.
During the 2025 Poland Wiper Attacks, the adversaries utilized Tor nodes for C2. APT28 has routed traffic over Tor and VPN servers to obfuscate their activities. A backdoor used by APT29 created a Tor hidden service to forward traffic from the Tor client to local ports 3389 (RDP), 139 (Netbios), and 445 (SMB) enabling full remote access from outside the network.
"Anchor has used ICMP in C2 communications." / "COATHANGER uses ICMP for transmitting configuration information..." / "PHOREAL communicates via ICMP for C2." / "Regin ... can use ICMP to communicate between infected computers." / "Cobalt Strike can be configured to use TCP, ICMP, and UDP for C2 communications."
"The operators can download specialized tools onto an infected system, adding any functionality they want by including it in the encrypted file system"
Multiple malware families and intrusion sets are described as encrypting C2 traffic using SSL/TLS/HTTPS (e.g., "used HTTPS for command and control", "encrypts C2 communications with TLS", "uses SSL for encrypting C2 communications", "TLS-encrypted WebSocket Protocol (WSS) for C2").
Exfiltration
1 techniqueMany entries state malware or actors can upload, transfer, send, or exfiltrate files from compromised hosts to command-and-control servers or attacker infrastructure.
IOCs tracked for this family
30 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
IPs, domains, and DNS infrastructure linked to this family.
Recent activity
51 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A highly complex espionage rootkit/backdoor associated with Turla, also referred to as Snake in some reporting.
Cited as an example of genuinely complex malware with the sophistication associated with top-tier espionage operations.
Snake is referenced as possible Turla-associated malware using a covert store registry key technique in a Windows attack simulation dataset.
Snake is referenced as a possible Turla-associated malware installer used in this attack simulation dataset.
The version that knows your environment.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.