Troldesh

Category: ransomware · Aliases: Troldesh, Shade, Trojan.Troldesh, Ransom.Shade, Win32/Troldesh · Sample count (EMBER 2018): 14 · Enrichment: curated_sourced · Updated: 2026-06-09
Category: RansomwareStatus: Automated SignaturePlatform: WINDOWS_PEStage: Defense Evasion, ImpactFirst seen: 2014Actor: Unknown / CybercriminalIndustry: Healthcare, Critical Infrastructure, EnterpriseMotivation: Financial Extortion🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Troldesh (widely tracked across the intelligence community as Shade or Encrypter.JPHP) is a notorious Russian-speaking ransomware family first active in late 2014.

Table of Contents

Overview

Troldesh (widely tracked across the intelligence community as Shade or Encrypter.JPHP) is a notorious Russian-speaking ransomware family first active in late 2014. Troldesh earned international attention for its idiosyncratic behavior: its ransom notes often contained Russian poetry and philosophical passages, and it cycled through numerous distinctive file extensions including `.crypted`, `.xtbl`, `.ytbl`, and `.breaking_bad`. Troldesh utilized AES-256 in CBC mode to encrypt victim data, protecting the key with asymmetric RSA-2048 encryption. In April 2020, the operators of Troldesh executed an extraordinary and voluntary exit: they published a public apology on GitHub and hacker forums ('We are the team which created a trojan-encryptor known as Shade, Troldesh... we made a decision to put an end to this story and to publish the rest of decryption keys'), releasing over 750,000 private decryption keys. Security vendors including Kaspersky Lab and Group-IB verified the keys and updated the free 'ShadeDecryptor' utility, allowing all remaining historical victims worldwide to recover their encrypted data free of charge.

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:

Known Derivatives & Downstream Variants: Troldesh V1.0 (.Crypted) · Troldesh V2.0 (.Xtbl) · Troldesh V3.0 (.Breaking_Bad) · Encrypter.Jphp (Master Key Release)

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-OAAOutbound Network Traffic FilteringIsolateT1090.003Restrict outbound connections to known external proxy relays and enforce enterprise forward proxy authentication.
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-FAEDFile Alteration Early DetectionDetectT1486Deploy canary files and monitor mass rename/encryption I/O spikes to terminate ransomware threads immediately.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.
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.

ProtocolsHTTP, HTTPS, Tor Onion Routing, AES-256 with RSA-2048
Observed ports80, 443
Infrastructure modelCompromised WordPress websites acting as reverse proxies to Tor hidden services (.onion) for ransom communication; decommissioned voluntarily by the authors in April 2020.
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_TROLDESH_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Troldesh"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "troldesh" ascii wide nocase
        $s2 = "troldesh" ascii wide nocase
        $s3 = "shade" ascii wide nocase
        $s4 = "trojan.troldesh" ascii wide nocase
        $s5 = "ransom.shade" ascii wide nocase
        $s6 = "win32/troldesh" 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 - Troldesh (Ransomware) Execution & Triage
id: 7334566f-9392-5a2a-b536-e248b80280af
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Troldesh malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/troldesh
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1486
- attack.t1490
- attack.t1071_001
- attack.t1566_001
- attack.t1547_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_TROLDESH_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Troldesh 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 = "troldesh" 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. Instantly isolate the endpoint from the network to prevent the ransomware from enumerating and encrypting shared network drives (SMB shares) and to sever C2 communications.
  2. Do NOT pay the ransom. Navigate to the 'No More Ransom' project; a universal, free decryptor (Shade Decryptor by Kaspersky) is available for all variants of Troldesh.
  3. Use EDR or Process Explorer to terminate the active Troldesh encryption process before utilizing the decryptor.
  4. Perform a deep system scan after decryption, as Troldesh frequently downloaded secondary infostealers and botnet components.

What to Avoid

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

  1. Do not delete the encrypted files or the original ransom notes, as the free decryption tools often require information from the ransom note to identify the correct key.
  2. Avoid restarting the computer if the encryption process is actively running, as this can corrupt files currently being processed.

References & External Analysis

Frequently Asked Questions

What was Troldesh (Shade) ransomware?

Troldesh (also called Shade) was a prominent Russian ransomware active from 2014 to 2020 that encrypted files using AES-256 and RSA-2048.

How did Troldesh end in April 2020?

In April 2020, the authors published a public apology on GitHub and released over 750,000 decryption keys, allowing Kaspersky to create a free universal decryptor.

What file extensions did Troldesh append to encrypted files?

Troldesh used extensions including .crypted, .xtbl, .ytbl, .breaking_bad, and .heisenberg.

How was Troldesh delivered to victims?

Troldesh was primarily distributed through phishing emails with weaponized attachments and exploit kits leveraging Flash and Office vulnerabilities.

Is there a free decryptor available for Troldesh?

Yes, Kaspersky's free ShadeDecryptor tool uses the authors' published 750,000 master keys to decrypt all versions of Troldesh.

How do I remove the Troldesh Ransomware from Windows?

Manual removal of Troldesh 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 Troldesh a virus or a Ransomware?

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

What are the main symptoms of a Troldesh infection?

Symptoms of Troldesh 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 Ransomwares

Want to prevent Troldesh and similar threats from compromising your organization? Read our comprehensive defensive guide: Ransomware Containment & Incident Response.

📣 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/troldesh.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.