Shutdowner

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Forced System State Change: The script (often a simple batch file invoking `shutdown.exe -s -f -t 0` or a small compiled executable calling the `ExitWindowsEx` API) forces the operating system to immediately power down or reboot.
• Bypassing User Prompts: The "-f" flag (force) is almost universally used, meaning any unsaved work in open applications is instantly destroyed without prompting the user to save.
• Anti-Forensic Utility: Attackers sometimes deploy a Shutdowner script immediately after executing a primary payload (like dropping a backdoor). The forced reboot clears volatile memory (RAM), destroying potential forensic evidence of the initial infection vector before incident responders can capture it.

Threat Assessment

Incident Response and Remediation

• Investigate the Source (Critical): The primary focus must be determining *how* the script was executed. Check Windows Event Logs (specifically Security logs for logon events and System logs for scheduled tasks or service creations) to identify the attacker's entry point.
• Disable Scheduled Tasks/Run Keys: Check if the Shutdowner has established persistence (e.g., executing on every boot to create a permanent denial of service loop). Remove any associated registry keys or scheduled tasks.
• Assume Broader Compromise: Do not treat the shutdown as an isolated prank. Assume the attacker deployed other, stealthier malware before initiating the shutdown. A thorough forensic sweep of the endpoint is required.

Known aliases

Threat reports may refer to this family under multiple names:

• HackTool.Shutdowner
• Riskware.Shutdown
• Win32/DoS.Shutdown

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.
• T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

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_SHUTDOWNER_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Shutdowner"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "shutdowner" ascii wide nocase
        $s2 = "hacktool.shutdowner" ascii wide nocase
        $s3 = "riskware.shutdown" ascii wide nocase
        $s4 = "win32/dos.shutdown" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Shutdowner (Backdoor) Execution & Triage
id: a89f21f3-61e7-553e-aa13-22306d0e235d
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Shutdowner malware family. Detects proxy execution, reflective DLL loading,
  and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/shutdowner
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.backdoor
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1529
- attack.t1071_001
- attack.t1547_001
- attack.t1055
- attack.t1056_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

rule MALWARE_WIN_SHUTDOWNER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Shutdowner 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 = "shutdowner" 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. Immediately isolate the compromised host from internal LAN and WAN environments to cut off interactive remote shell sessions established by Shutdowner.
2. Inspect active socket listeners and outbound established network connections ('netstat -ano') to identify and sever covert TCP/UDP channels used by Shutdowner.
3. Scan Windows Services, Scheduled Tasks, and Startup folders to locate and eliminate persistent backdoor listeners configured by Shutdowner.
4. Invalidate all active VPN profiles, local administrator credentials, and session tokens that may have been harvested by the Shutdowner operator.
5. Re-image the affected host using a validated golden image prior to reconnecting it to enterprise network segments.

What to Avoid

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

1. Do not attempt to interact with or send messages through the Shutdowner remote terminal, as this alerts the attacker and may cause them to execute destructive anti-forensic commands.
2. Avoid relying solely on static file signatures, as Shutdowner payloads frequently execute reflectively in memory without writing binaries to disk.

References & External Analysis

• Search "shutdowner" on VirusTotal (External Analysis)
• Search "shutdowner" on Any.Run (Sandbox Sandbox)
• Search "shutdowner" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Backdoor)

Explore other documented threats in the same operational category:

• Doublefantasy
• Flux
• Xiclog
• Werpoapt
• Buterat
• Chopper
• Arcdoor
• Keydoor

Machine-readable

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