Snake
Snake, also known as Uroburos, is a highly sophisticated cyber-espionage malware platform associated with the Russia-linked Turla threat actor and publicly attributed by CISA to Center 16 of Russia’s Federal Security Service (FSB). It has been used in long-running espionage operations against Western interests, including sensitive government and military organizations, and was described as part of the Snake cyber-espionage botnet disrupted in Operation MEDUSA. Public reporting also notes uncertainty around its historical infection vector.
The malware is notable for stealth, persistence, encrypted communications, and multi-component architecture. Uroburos/Snake has registered a Windows service, typically named WerFaultSvc, to decrypt and locate a kernel driver and kernel driver loader for persistence. It can query the Windows Registry, including HKLM:\SOFTWARE\Classes.wav\OpenWithProgIds, to retrieve the key and path needed to decrypt and load its kernel driver and loader. Configuration information for its kernel driver and loader components can be stored in an encrypted blob in that same registry location. Uroburos can move data between kernel-mode and user-mode components using named pipes.
For command and control, Uroburos can use a custom HTTP-based protocol for large data communications designed to blend with normal traffic by riding on standard HTTP. Its top-layer C2 communications have used a Diffie-Hellman key exchange combined with a pre-shared key for encryption. The malware can also use implants on multiple compromised machines to proxy communications through a worldwide peer-to-peer network. The Uroburos Queue file contains embedded executable files along with key material, communication channels, and modes of operation.
The content also places Snake/Uroburos within Turla’s broader malware ecosystem and long-term operations, including reporting that ComRAT developers attempted to disguise links between ComRAT, the Uroburos rootkit, and Agent.BTZ. Snake/Uroburos is repeatedly cited in public technical reporting as one of the more advanced espionage toolsets associated with Turla.
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.
Known historically for its tight ties to Russia’s Federal Security Service (FSB) and its development of the Snake implant, Turla has leveraged STOCKSTAY to target sensitive government and military organizations.
Techniques & procedures
27 distinct techniques documented for this family, organized by ATT&CK tactic.
Initial Access
3 techniques
Initial Access
Execution
1 technique
Execution
During 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.
Persistence
3 techniques
Persistence
Many 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.
Privilege Escalation
2 techniques
Privilege Escalation
Stealth
8 techniques
Stealth
The 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.'
Defense Impairment
1 technique
Defense Impairment
Many 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
Credential Access
Discovery
4 techniques
Discovery
The 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."
The content repeatedly describes malware and threat actors listing files and directories, enumerating drives, searching for files by extension/name/path, retrieving file metadata, and browsing file systems (for example: "APT28 has used Forfiles to locate PDF, Excel, and Word documents during collection" and "cmd can be used to find files and directories with native functionality such as dir commands").
Command and Control
5 techniques
Command and Control
"By infiltrating Turla's network of hacked machines and sending the malware a command to delete itself"
The content repeatedly describes threat actors and malware using HTTP and HTTPS for command and control, such as: "Sandworm Team used BlackEnergy to communicate between compromised hosts and their command-and-control servers via HTTP post requests."
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."
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
58 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Turla-developed implant referenced as part of the group's historical malware toolkit.
Keylogger family delivered through the same infrastructure in related campaigns.
Advanced malware referenced for its hidden virtual filesystem used to conceal artifacts from forensic analysis.
A highly complex espionage rootkit/backdoor associated with Turla, also referred to as Snake in some reporting.
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.