Adwind
Table of Contents
Overview
Adwind (classified in antivirus detection telemetry under designations including Trojan:Win32/Adwind, Trojan.Win32.Adwind, and Win32/Adwind) is a multi-stage trojan engineered to disguise itself as legitimate software, execute unauthorized commands, and coordinate with external command-and-control infrastructure. Disseminated across enterprise networks and consumer workstations via social engineering, phishing attachments, malicious drive-by downloads, or weaponized software cracks, Adwind executes an initial reconnaissance phase upon system ingress. The binary evaluates host privileges, detects active hypervisors and sandbox environments to evade behavioral analysis, and establishes resilient autostart persistence by configuring registry keys under HKCU\Software\Microsoft\Windows\CurrentVersion\Run or registering background Windows services. Operational mechanics characteristic of this family include deceptive executable masquerading, registry run key autostart, system telemetry gathering, and remote C2 beaconing. Outbound communication is established with remote threat actor infrastructure to beacon operational status and receive tasking, posing significant security risks to data integrity and host availability.
Known aliases
Threat reports may refer to this family under multiple names:
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 |
|---|---|---|---|
T1056.001 | Input Capture: Keylogging | Collection | ATT&CK ↗ |
T1566.001 | Phishing: Spearphishing Attachment | Initial Access | ATT&CK ↗ |
T1071.001 | Application Layer Protocol: Web Protocols (C2 Communication) | Command and Control | ATT&CK ↗ |
T1125 | Video/Audio Capture | Collection | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
- T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.
- T1125: Restrict access to local camera or microphone APIs. Utilize endpoint protection that monitors hardware access.
- 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-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
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-HAC | Hardware Device Access Control | Isolate | T1125 | Enforce Group Policy hardware access restrictions on integrated webcams and microphones. |
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_ADWIND_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Adwind"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "adwind" ascii wide nocase
$s2 = "trojan:win32/adwind" ascii wide nocase
$s3 = "trojan.win32.adwind" ascii wide nocase
$s4 = "win32/adwind" 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 - Adwind (Trojan) Execution & Triage
id: b1ffbd42-93f0-5870-bdbd-983db0c1d85b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Adwind malware family. Detects suspicious execution from temporary user
directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/adwind
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_003
- attack.t1027
- attack.t1547_001
- attack.t1071_001
- attack.t1105
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \cscript.exe
- \wscript.exe
CommandLine|contains:
- AppData\Local\Temp
- -WindowStyle Hidden
- /e:jscript
- bitsadmin /transfer
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_ADWIND_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Adwind 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 = "adwind" 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 isolate the endpoint from the network to sever the attacker's interactive control session.
- Force a password reset for all corporate accounts used on the machine, as the keylogger likely captured them.
- Verify the infection vector (usually email) and purge the malicious `.jar` attachment from all corporate inboxes to prevent lateral spread.
- Consider uninstalling the Java Runtime Environment (JRE) from all endpoints that do not strictly require it for business operations.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume macOS or Linux endpoints are immune; Adwind's primary strength is its ability to infect any OS with Java installed.
- Avoid relying solely on file hashes, as Adwind builders allow attackers to easily generate unique, obfuscated `.jar` files.
References & External Analysis
Frequently Asked Questions
What is Trojan:Win32/Adwind?
Adwind is a trojan threat designed to infiltrate Windows systems and execute unauthorized operations without user consent.
How does Adwind compromise target systems?
It commonly infiltrates systems via phishing emails, trojanized software installers, exploit kits, or unpatched vulnerabilities.
What persistence mechanisms does Adwind utilize?
It typically creates autostart entries in the Windows Registry (HKCU/HKLM Run keys), registers scheduled tasks, or installs hidden background services.
What risks does Adwind pose to an enterprise?
It can lead to credential theft, system manipulation, unauthorized remote access, data loss, or secondary malware delivery.
How can administrators detect and eliminate Adwind?
Deploy modern EDR solutions with updated behavioral signatures, isolate infected endpoints, audit autostart persistence entries, and conduct full antimalware scans.
How do I remove Adwind from Windows?
Manual removal of Adwind 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 Adwind infection?
Symptoms of Adwind 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 Trojans
Want to prevent Adwind and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.
📣 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/adwind.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.