Daws
Table of Contents
Overview
TrojanDownloader:Win32/Daws (cataloged across security vendors as Trojan.Daws or Ransom.Daws) is a persistent Windows trojan downloader and stage-one ransomware delivery mechanism engineered to breach endpoint perimeters and orchestrate the automated deployment of secondary extortion payloads. Operating through heavily packed executables dropped into temporary system directories (%Temp%), Daws establishes scheduled tasks and modifies registry Run keys to ensure persistence. Once a machine profile is established, Daws initiates encrypted HTTPS beacons to remote C2 infrastructure, pulling down secondary ransomware binaries that systematically traverse local and mapped network drives, encrypt target document and database extensions, delete Volume Shadow Copies via vssadmin, and display ransom notes demanding cryptocurrency payments.
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.
- Cybercrime Ransomware Affiliates High confidence
Basis:
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: Daws.A Downloader · Daws Ransomware Stage · Daws Scheduled Task Variant
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1486 | Data Encrypted for Impact | impact | ATT&CK ↗ |
T1105 | Ingress Tool Transfer | command-and-control | ATT&CK ↗ |
T1053.005 | Scheduled Task | persistence | ATT&CK ↗ |
T1027 | Obfuscated Files or Information | defense-evasion | ATT&CK ↗ |
T1071.001 | Web Protocols | command-and-control | ATT&CK ↗ |
T1547.001 | Registry Run Keys / Startup Folder | persistence | ATT&CK ↗ |
T1490 | Inhibit System Recovery | impact | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.
- T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
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-BDA | Binary De-obfuscation & Unpacking | Analyze | T1027 | Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation. |
D3-STM | Scheduled Task Creation Analysis | Detect | T1053.005 | Audit task creation targeting system and hidden service directories; verify task author credentials. |
D3-WAF | Web Content Filtering & Inspection | Filter | T1071.001 | Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles. |
D3-NTI | Network Traffic Inspection | Detect | T1105 | Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols. |
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-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
Exploited Vulnerabilities (CVEs)
This malware family is documented weaponizing the following common vulnerabilities and exposures:
- CVE-2017-0199 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
- CVE-2017-11882 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
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.
| Protocols | HTTPS, HTTP |
|---|---|
| Observed ports | 443, 80, 8080 |
| Identifiable from traffic alone | Medium |
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.
2e3f4a5b6c708192a3b4c5d6e7f8091a2b3c4d5e6f708192a3b4c5d6e7f811229a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a22
Delivery vectors
malspam_weaponized_archivesexploit_kit_landing_pages
Persistence mechanisms
Windows Task Scheduler Job CreationHKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
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_DAWS_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Daws"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "daws" ascii wide nocase
$s2 = "daws" ascii wide nocase
$s3 = "trojandownloader:win32/daws" ascii wide nocase
$s4 = "trojan.daws" ascii wide nocase
$s5 = "win32/daws" ascii wide nocase
$s6 = "daws downloader" ascii wide nocase
$s7 = "ransom.daws" ascii wide nocase
$s8 = "trojan:win32/daws" 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 - Daws (Ransomware) Execution & Triage
id: a8fd07ee-2644-5316-b236-feb515c96579
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Daws 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/daws
- 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.t1105
- attack.t1053_005
- attack.t1027
- attack.t1071_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_DAWS_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Daws 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 = "daws" 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 infected machines from internal networks to stop active ransomware spreading across shared drives.
- Audit Windows Task Scheduler and delete unauthorized tasks executing binaries from %Temp% or AppData folders.
- Verify the integrity of immutable offline backups before attempting system restoration.
- Deploy security updates patching Microsoft Office Equation Editor vulnerability CVE-2017-11882.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not pay ransom demands, as payment finances criminal operations and offers no guarantee of decryption.
- Avoid allowing endpoints to execute scripts or unsigned binaries directly out of %Temp% directories.
- Never neglect monitoring unauthorized vssadmin executions targeting Volume Shadow Copies.
References & External Analysis
- Microsoft Security Intelligence: TrojanDownloader:Win32/Daws Technical Guidance
- Trend Micro Threat Encyclopedia: Trojan.Daws Analysis
- NIST National Vulnerability Database CVE-2017-11882
- Search "daws" on VirusTotal (External Analysis)
- Search "daws" on Any.Run (Sandbox Sandbox)
- Search "daws" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Daws malware?
Daws is a persistent Trojan downloader and ransomware staging tool that establishes system persistence to deploy file-encrypting extortion payloads.
How does Daws deploy ransomware onto compromised endpoints?
Daws communicates over encrypted HTTPS channels to download secondary ransomware binaries, which execute and encrypt files across local and network drives.
How does Daws maintain persistence on Windows?
Daws drops randomized executables into the %Temp% directory and creates hidden Windows Scheduled Tasks and registry Run keys.
What vulnerabilities were exploited in Daws distribution?
Daws campaigns leveraged Microsoft Office vulnerabilities including CVE-2017-0199 and CVE-2017-11882 in weaponized email attachments.
How can administrators mitigate a Daws ransomware infection?
Isolate infected hosts immediately, terminate suspicious scheduled tasks, block outbound C2 network connections, and restore encrypted data from offline backups.
How do I remove Daws from Windows?
Manual removal of Daws 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 Daws infection?
Symptoms of Daws 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 Daws 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/daws.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.