Sagecrypt
Table of Contents
Overview
Ransom:Win32/Sagecrypt (widely known as **Sage 2.0**) is a highly sophisticated ransomware family that gained prominence in 2017. It is notable for being heavily distributed by massive botnets (like the ones that delivered Locky and Cerber) and for its use of strong, unbroken encryption algorithms. It encrypts a victim's files, appends the `.sage` extension to them, and demands payment in Bitcoin via a dedicated Tor hidden service.
Understanding the Sage Ransomware Threat
To an organization, Sagecrypt is a devastating threat. It is designed for maximum damage, encrypting not just local files, but also aggressively scanning for and encrypting accessible network shares and removable drives. Security analysts note Sage 2.0 for its professional infrastructure; the payment portals are often translated into dozens of languages and feature live chat support to 'assist' victims in buying Bitcoin.
Execution and Encryption Mechanics
Sagecrypt is primarily delivered via massive phishing campaigns (`T1566.001`) utilizing weaponized ZIP files containing malicious JavaScript or Word macros. Once executed, it profiles the system (`T1082`) and uses `vssadmin.exe` and `wbadmin.exe` to delete Windows Volume Shadow Copies and backup catalogs, preventing simple recovery (`T1490`). It utilizes the ChaCha20 symmetric algorithm to encrypt the files rapidly, and an RSA public key to encrypt the ChaCha20 keys (`T1486`). This hybrid approach ensures the files cannot be decrypted without the attacker's private key. Sage drops a ransom note named `!Recovery_[random_chars].html`.
Indicators of Compromise & Impact
The primary impact is total data loss across the endpoint and accessible network shares. Host-based IoCs include EDR alerts for the execution of command-line tools aimed at inhibiting recovery (e.g., `vssadmin.exe Delete Shadows /All /Quiet`). The most obvious indicator is the mass renaming of files to include the `.sage` extension, accompanied by massive CPU and disk I/O spikes. Network IoCs include the malware attempting to resolve the attacker's Tor payment gateway domains via public DNS servers.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1566.001: Scan email attachments for malicious macros, scripts, or suspicious archive files.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-SDA | System Discovery Analysis | Detect | T1082 | Alert on rapid enumerations of systeminfo, hostname, and registry hardware trees in short intervals. |
D3-FAED | File Alteration Early Detection | Detect | T1486 | Deploy canary files and monitor mass rename/encryption I/O spikes to terminate ransomware threads immediately. |
D3-VSS | Volume Shadow & Snapshot Hardening | Harden | T1490 | Block execution of vssadmin.exe and wmic shadowcopy delete; maintain air-gapped immutable backup repositories. |
D3-FS | File Sandboxing (Attachment Detonation) | Isolate | T1566.001 | Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor. |
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_SAGECRYPT_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Sagecrypt"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "sagecrypt" 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 - Sagecrypt (Ransomware) Execution & Triage
id: d32f9be4-9f3d-5be8-92c7-01c617914608
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Sagecrypt 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/sagecrypt
- 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.t1566_001
- attack.t1082
- attack.t1486
- attack.t1490
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: criticalTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_SAGECRYPT_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Sagecrypt 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 = "sagecrypt" 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
}Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Immediately disconnect the infected endpoint from the network to halt the encryption of mapped network drives and SMB shares.
- Do not restart the machine, as this may trigger a wiper routine or destroy forensic artifacts in RAM that could contain the symmetric key.
- Identify the initial phishing vector and purge the malicious email from the Exchange server to prevent lateral spread.
- Initiate the corporate Incident Response plan and begin restoring data from offline, immutable backups.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not pay the ransom unless absolutely necessary for business continuity; payment does not guarantee data recovery and funds organized crime.
- Avoid reconnecting the infected machine to the network until it has been completely wiped and reimaged.
References & External Analysis
- Search "sagecrypt" on VirusTotal (External Analysis)
- Search "sagecrypt" on Any.Run (Sandbox Sandbox)
- Search "sagecrypt" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Sagecrypt and what threat category does it belong to?
Sagecrypt 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 Sagecrypt establish persistence and evade defensive controls?
Sagecrypt 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 Sagecrypt compromise?
Security teams responding to Sagecrypt 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 Sagecrypt employ during execution?
Sagecrypt 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 Sagecrypt, and what is the recommended recovery procedure?
Decryption availability for Sagecrypt 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 the Sagecrypt Ransomware from Windows?
Manual removal of Sagecrypt 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 Sagecrypt a virus or a Ransomware?
Sagecrypt is classified as a Ransomware. Unlike traditional viruses that infect files, modern malware like Sagecrypt typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Sagecrypt infection?
Symptoms of Sagecrypt 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 Sagecrypt 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/sagecrypt.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.