Donex

Category: ransomware · Aliases: None known · Sample count (EMBER 2018): 7 · Enrichment: expert-seo · Updated: 2026-06-09
Category: RansomwareStatus: Automated SignaturePlatform: WINDOWS_PEStage: Defense Evasion, ImpactActor: 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
Ransom:Win32/Donex is a destructive ransomware family that targets both individual users and enterprise networks, utilizing strong cryptographic algorithms to encrypt valuable files and demand payment for their release.

Table of Contents

Overview

Ransom:Win32/Donex is a destructive ransomware family that targets both individual users and enterprise networks, utilizing strong cryptographic algorithms to encrypt valuable files and demand payment for their release. Like many modern ransomware variants, it is designed to cause maximum operational disruption to force swift payment from the victim.

Understanding Donex Ransomware
To an infected user, the outcome is catastrophic: documents, databases, and critical files are suddenly inaccessible, their filenames often appended with a specific extension. A ransom note (usually an HTML or TXT file dropped in every directory) demands cryptocurrency. For a security operations center (SOC), a Donex detonation often represents the final stage of a prolonged network compromise, indicating that attackers have successfully bypassed endpoint defenses and potentially moved laterally across the network.

Execution and Encryption Mechanics
Donex is distributed via various vectors, including spear-phishing (`T1566`), malicious spam attachments, or manually deployed by attackers via compromised Remote Desktop Protocol (RDP) (`T1133`). Upon execution (`T1204.002`), it often attempts to terminate critical database and backup services (like SQL Server or Veeam) (`T1489`) to ensure those files are unlocked and vulnerable. It executes commands to delete Windows Volume Shadow Copies (`T1490`) using `vssadmin.exe` to prevent easy restoration. It then traverses the file system and mapped network drives, encrypting files using strong cryptography (`T1486`).

Indicators of Compromise & Impact
The impact is severe operational downtime and potential permanent data loss. The primary IoC is the massive, rapid modification of files across the hard drive and network shares. Host-based IoCs include EDR alerts for the mass deletion of shadow copies (`vssadmin delete shadows`) and the sudden termination of critical services. Network logs may show the initial command-and-control (C2) check-in to exchange the public encryption keys.

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

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-FEAFile Execution AnalysisHardenT1204.002Enforce AppLocker and Windows Defender Application Control (WDAC) to block executable launches from temporary and user-writable directories.
D3-FAEDFile Alteration Early DetectionDetectT1486Deploy canary files and monitor mass rename/encryption I/O spikes to terminate ransomware threads immediately.
D3-SPPService Protection PoliciesHardenT1489Configure strict DACLs on Windows Service Control Manager to prevent unauthorized termination of antivirus and backup services.
D3-VSSVolume Shadow & Snapshot HardeningHardenT1490Block execution of vssadmin.exe and wmic shadowcopy delete; maintain air-gapped immutable backup repositories.

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_DONEX_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Donex"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "donex" 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 - Donex (Ransomware) Execution & Triage
id: 0692d0fc-9388-5ba8-8da0-051141263ef3
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Donex 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/donex
- 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.t1489
- attack.t1490
- attack.t1204_002
- attack.t1486
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_DONEX_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Donex 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 = "donex" 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 infected endpoint from the network to halt the encryption process, explicitly disconnecting it from mapped network shares.
  2. Do NOT reboot the machine immediately; capture a live memory dump (RAM) first, as forensic analysis may recover the encryption keys from memory.
  3. Check for publicly available decryption tools on 'No More Ransom'; some older ransomware variants have known cryptographic flaws.
  4. Wipe the infected systems and restore data from secure, immutable offline backups.

What to Avoid

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

  1. Do not pay the ransom. Paying funds criminal enterprises, and there is no guarantee the attackers will provide a working decryption tool.
  2. Avoid reconnecting the machine to the network until a full forensic investigation has identified the initial entry vector (e.g., compromised RDP).

References & External Analysis

Frequently Asked Questions

What is Donex and what threat category does it belong to?

Donex is classified as a Ransomware. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.

How does Donex establish persistence and evade defensive controls?

Donex typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.

What are the essential incident response steps for mitigating a Donex compromise?

Security teams responding to Donex should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.

What cryptographic algorithms and file targeting techniques does Donex employ during execution?

Donex typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options.

Are decryptors available for Donex, and what is the recommended recovery procedure?

Decryption availability for Donex depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups.

How do I remove Donex from Windows?

Manual removal of Donex 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.

What are the main symptoms of a Donex infection?

Symptoms of Donex 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 Donex 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/donex.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.