Turla

Category: advanced_threat · Aliases: Turla, Snake, Uroburos, Waterbug, Venomous Bear, KRYPTON · Sample count (EMBER 2018): 35 · Enrichment: curated_sourced · Updated: 2026-06-09
Category: Advanced_ThreatStatus: Automated SignaturePlatform: WINDOWS_PEStage: Persistence, Command And Control, Remote AccessFirst seen: 2007Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Turla (extensively documented in military and threat intelligence reporting under aliases such as Snake, Uroburos, Waterbug, and Venomous Bear) is an elite cyber espionage framework operated by the Russian Federal Security Service (FSB) 16th Center (Military Unit 71330).

Table of Contents

Overview

Turla (extensively documented in military and threat intelligence reporting under aliases such as Snake, Uroburos, Waterbug, and Venomous Bear) is an elite cyber espionage framework operated by the Russian Federal Security Service (FSB) 16th Center (Military Unit 71330). With roots tracing back to the landmark 2008 Agent.BTZ compromise of the US Department of Defense, Turla has conducted targeted cyber espionage for over 15 years against government ministries, embassies, military command facilities, and intelligence agencies across more than 50 countries. Turla is renowned for unprecedented technical sophistication: it pioneered high-altitude satellite internet downlink hijacking (intercepting unencrypted satellite DVB-S streams from commercial providers in Africa and the Middle East to mask its C2 servers), complex internal peer-to-peer (P2P) mesh communications between isolated subnet victim nodes, and kernel-level rootkits. In May 2023, the United States Department of Justice, the FBI, and intelligence partners across the Five Eyes alliance executed 'Operation MEDUSA'—a court-authorized operation that deployed the FBI-developed 'PERSEUS' tool to communicate with and remotely issue self-disabling commands to the FSB's flagship Snake implant network worldwide.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Agent.Btz

Known Derivatives & Downstream Variants: Snake / Uroburos Rootkit · Carbon · Epic Turla · Gazer · Mosquito · Tinyturla (2021)

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-KMCKernel Memory Integrity CheckingHardenT1014Enable Hypervisor-Protected Code Integrity (HVCI) and UEFI Secure Boot to prevent unsigned kernel driver execution.
D3-DIADLL Injection AnalysisDetectT1055.001Monitor remote thread creation (CreateRemoteThread) and unauthorized DLL loading into core Windows processes (svchost.exe, explorer.exe).
D3-OAAOutbound Network Traffic FilteringIsolateT1090.002Restrict outbound connections to known external proxy relays and enforce enterprise forward proxy authentication.
D3-FSFile Sandboxing (Attachment Detonation)IsolateT1566.001Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsSatellite Downlink Hijacking (TCP over DVB-S), HTTP, HTTPS, DNS Tunneling, P2P Subnet Mesh
Observed ports80, 443, 53
Infrastructure modelHigh-altitude satellite internet downlinks abusing unencrypted commercial satellite receivers, combined with multi-hop peer-to-peer internal network relays routing stolen intelligence through a single egress node.
Identifiable from traffic aloneUnrated

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

rule MALWARE_WIN_TURLA_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Turla"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "turla" ascii wide nocase
        $s2 = "turla" ascii wide nocase
        $s3 = "snake" ascii wide nocase
        $s4 = "uroburos" ascii wide nocase
        $s5 = "waterbug" ascii wide nocase
        $s6 = "venomous bear" ascii wide nocase
        $s7 = "krypton" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Turla (Advanced Threat) Execution & Triage
id: 47dedc18-c7f9-5f63-a2f9-0fe34f51a7ea
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Turla malware family. Detects proxy execution, reflective DLL loading,
  and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/turla
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1055
- attack.t1542_003
- attack.t1071_001
- attack.t1071_004
- attack.t1546_015
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_TURLA_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Turla tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "turla" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Assume total domain compromise. Turla operates with extreme stealth; if one endpoint is detected, they likely have entrenched rootkits across the network.
  2. Engage a Tier-1 Incident Response retainer immediately; standard internal SOC teams are rarely equipped to hunt a top-tier Russian FSB unit.
  3. Do NOT initiate remediation piecemeal; Turla will observe the cleanup efforts and deploy destructive wipers or deeper persistence mechanisms. Remediation must be coordinated and instantaneous.
  4. Perform deep memory forensics (RAM dumps) on critical servers to detect the presence of the Uroburos/Snake kernel-level rootkits.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not alert the attackers by attempting to block their C2 domains prematurely; monitor their traffic to understand the full scope of the breach before executing a coordinated eviction.
  2. Avoid relying on standard antivirus scans; Turla's tools operate below the OS layer and will return false negatives.

References & External Analysis

Frequently Asked Questions

What is Turla (Snake)?

Turla (also known as Snake or Uroburos) is a premier Russian state-sponsored cyber espionage framework operated by FSB Center 16 for long-term intelligence collection.

What was Operation MEDUSA in May 2023?

Operation MEDUSA was a court-authorized FBI operation that used custom tool PERSEUS to send commands to the FSB's Snake implant network worldwide, disabling the malware on victim hosts.

How did Turla use commercial satellite internet for C2?

Turla hijacked unencrypted commercial satellite downlinks, spoofing subscriber IP addresses so incoming C2 commands appeared from space without revealing the physical location of the server.

What targets does Turla typically focus on?

Turla focuses on high-value intelligence targets including NATO entities, ministries of foreign affairs, defense departments, and critical research institutions across more than 50 nations.

How can network defenders identify Turla activity?

Detect Turla by inspecting kernel driver signatures, monitoring unauthorized lateral SMB/RPC traffic between internal subnets, and deploying EDR rules detecting COM object hijacking.

How do I remove the Turla Advanced_Threat from Windows?

Manual removal of Turla is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

Is Turla a virus or a Advanced_Threat?

Turla is classified as a Advanced_Threat. Unlike traditional viruses that infect files, modern malware like Turla typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Turla infection?

Symptoms of Turla can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Advanced_Threats

Want to prevent Turla and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/turla.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.