Autohk

Overview

The "AutoHK" malware family refers to a broad category of malicious programs that utilize AutoHotkey (AHK), a legitimate and open-source scripting language designed for keyboard shortcuts and Windows automation. Attackers frequently abuse AutoHotkey to create, bundle, and execute malicious scripts while attempting to evade detection by security software. By packaging malicious AHK scripts with the AutoHotkey interpreter into a single executable file, attackers can obfuscate their code and bypass simple signature-based antivirus detection. These scripts are often used for keylogging, taking screenshots, and data exfiltration.

Known aliases

Threat reports may refer to this family under multiple names:

• AutoHotkey.Trojan
• Trojan.AutoHK
• Win32/AutoHK
• AHK.Stealer
• Malware.AutoHK

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Autohotkey_Scripting_Engine

Known Derivatives & Downstream Variants: Autohk.Gen · Ahk_Loader · Ahk_Keylogger

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:

• 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.
• T1059.005: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
• 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):

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.

• c3e4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4
• d4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5

Delivery vectors

• Phishing campaigns delivering weaponized Office documents exploiting CVE-2017-11882
• Deceptive automation scripts and gaming macro downloads

Persistence mechanisms

• HKCU\Software\Microsoft\Windows\CurrentVersion\Run\AutoHotkeyLoader
• Scheduled Task running compiled AHK payload from %LOCALAPPDATA%\Temp

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:

rule MALWARE_WIN_AUTOHK_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Autohk"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "autohk" ascii wide nocase
        $s2 = "autohotkey.trojan" ascii wide nocase
        $s3 = "trojan.autohk" ascii wide nocase
        $s4 = "win32/autohk" ascii wide nocase
        $s5 = "ahk.stealer" ascii wide nocase
        $s6 = "malware.autohk" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Autohk (Trojan) Execution & Triage
id: a686d958-b7be-525b-a597-cc2a0ebf5ff0
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Autohk 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/autohk
- 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_005
- attack.t1056_001
- attack.t1055
- attack.t1547_001
- attack.t1027
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

rule MALWARE_WIN_AUTOHK_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Autohk 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 = "autohk" 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.

1. Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Autohk from retrieving secondary stage payloads.
2. Capture process memory triage to detect and terminate malicious threads injected by Autohk into legitimate system processes such as explorer.exe or svchost.exe.
3. Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Autohk persistence hooks.
4. Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
5. Rotate all credentials, domain user passwords, and session cookies active on the system during the Autohk execution timeframe.

What to Avoid

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

1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Autohk dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Autohk until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

• Trend Micro - Abuse of AutoHotkey in Cybercrime Campaigns
• NIST National Vulnerability Database - CVE-2017-11882
• Search "autohk" on VirusTotal (External Analysis)
• Search "autohk" on Any.Run (Sandbox Sandbox)
• Search "autohk" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Trojan)

Explore other documented threats in the same operational category:

• Rockrat
• Indigorose
• Winreg
• Ou0Bsubcbkhb
• Bancobras
• Dnschanger
• Virledi
• Possiblemalware

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/autohk.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.