Autoruns

Category: hacktool · Aliases: HackTool:Win32/AutoRuns, VirTool:Win32/AutoRuns, Trojan:Win32/AutoRuns, Win32/AutoRuns, Tool:Win32/AutoRuns · Sample count (EMBER 2018): 21 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: HacktoolStatus: Automated SignaturePlatform: WINDOWS_PEStage: Discovery, Persistence, Privilege EscalationActor: Advanced Threat Groups & Post-Exploitation OperatorsIndustry: Enterprise Networks, Financial Institutions, Government, Critical InfrastructureMotivation: System Reconnaissance, Persistence Manipulation & Lateral Movement🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
AutoRuns (tracked in antimalware telemetry under signatures including HackTool:Win32/AutoRuns, VirTool:Win32/AutoRuns, and Trojan:Win32/AutoRuns) refers to weaponized, trojanized, or unauthorized redistributions of autostart enumeration and manipulation utilities.

Table of Contents

Overview

AutoRuns (tracked in antimalware telemetry under signatures including HackTool:Win32/AutoRuns, VirTool:Win32/AutoRuns, and Trojan:Win32/AutoRuns) refers to weaponized, trojanized, or unauthorized redistributions of autostart enumeration and manipulation utilities. While legitimate Sysinternals Autoruns is an industry-standard administrative utility, threat actors frequently recompile, wrap, or trojanize the tool to automate persistence auditing, locate and displace competitor malware on compromised systems, and forcibly install malicious services or registry run keys during lateral movement campaigns. Weaponized variants often incorporate embedded shellcode droppers, obfuscated command-line wrappers, or anti-EDR evasion hooks to hide unauthorized autorun modifications from security operations center (SOC) analysts.

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:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

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-BDABinary De-obfuscation & UnpackingAnalyzeT1027Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation.
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-SDASystem Discovery AnalysisDetectT1082Alert on rapid enumerations of systeminfo, hostname, and registry hardware trees in short intervals.
D3-SCMWindows Service Creation MonitoringDetectT1543.003Verify service binary image signatures and restrict standard users from creating or modifying service definitions.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

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_AUTORUNS_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Autoruns"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "autoruns" ascii wide nocase
        $s2 = "hacktool:win32/autoruns" ascii wide nocase
        $s3 = "virtool:win32/autoruns" ascii wide nocase
        $s4 = "trojan:win32/autoruns" ascii wide nocase
        $s5 = "win32/autoruns" ascii wide nocase
        $s6 = "tool:win32/autoruns" 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 - Autoruns (Hacktool) Execution & Triage
id: 19caca4f-64cd-5d1c-b117-4a373f75c28a
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Autoruns 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/autoruns
- 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.hacktool
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1547_001
- attack.t1543_003
- attack.t1082
- attack.t1027
- attack.t1059_003
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_AUTORUNS_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Autoruns 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 = "autoruns" 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. Terminate unauthorized instances of autorun auditing or manipulation executables.
  2. Verify the digital signature of Autoruns utilities to distinguish legitimate Sysinternals binaries from repackaged hacktools.
  3. Audit Windows Run registry entries, scheduled tasks, and services for unauthorized modifications.
  4. Deploy AppLocker or Windows Defender Application Control (WDAC) to enforce application whitelisting.
  5. Isolate machines where unauthorized hacktools have been executed to evaluate post-exploitation activity.

What to Avoid

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

  1. Do not allow arbitrary unsigned administrative utilities to run with elevated privileges.
  2. Do not assume all Autoruns executions are benign administrative activities without corroborating with IT operations.

References & External Analysis

Frequently Asked Questions

What is HackTool:Win32/AutoRuns?

HackTool:Win32/AutoRuns detects weaponized or trojanized versions of the Sysinternals Autoruns tool used maliciously by attackers.

How do adversaries misuse Autoruns utilities?

Adversaries use it to discover existing persistence mechanisms, eliminate competitor malware, and audit system autostart locations.

How does weaponized Autoruns differ from legitimate Sysinternals tools?

Weaponized versions embed malicious loaders, obfuscated wrappers, or shellcode execution hooks.

What persistence mechanisms are audited or modified by the tool?

It inspects and modifies Registry Run keys, Windows Services, Scheduled Tasks, Winlogon handles, and driver registrations.

How can unauthorized use of Autoruns be detected and controlled?

Enforce application allowlisting via AppLocker/WDAC, restrict admin execution privileges, and monitor process creation events.

How do I remove Autoruns from Windows?

Manual removal of Autoruns 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 Autoruns infection?

Symptoms of Autoruns 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 Hacktools

Want to prevent Autoruns and similar threats from compromising your organization? Read our comprehensive defensive guide: HackTool & Riskware Protection.

📣 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 Threat Intelligence Team.

Machine-readable

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