{
  "family": "shutdowner",
  "sample_count": 1,
  "category": "backdoor",
  "description": "<h3>Executive Summary</h3>\nShutdowner refers to a class of malicious scripts, utilities, or \"HackTools\" explicitly designed to force a computer to shut down, restart, or log off the current user aggressively. While system administrators utilize legitimate shutdown commands, threat actors weaponize these tools to induce immediate denial of service (DoS), disrupt business operations, or as a crude anti-forensic measure to halt security monitoring tools from analyzing a concurrent attack.\n\n<h3>Infection Vector and Technical Capabilities</h3>\nShutdowner tools are not self-propagating viruses. They are tactical utilities deployed *after* an attacker has gained a foothold, typically used as a disruptive payload or executed via remote access tools (RATs) or web shells.\n\nIts execution is straightforward but highly disruptive:\n<ul>\n<li><strong>Forced System State Change:</strong> 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.</li>\n<li><strong>Bypassing User Prompts:</strong> The \"-f\" flag (force) is almost universally used, meaning any unsaved work in open applications is instantly destroyed without prompting the user to save.</li>\n<li><strong>Anti-Forensic Utility:</strong> 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.</li>\n</ul>\n\n<h3>Threat Assessment</h3>\nThe execution of a \"Shutdowner\" script is a significant security incident resulting in immediate loss of availability and potential data loss for the user. More importantly, it strongly indicates an active, hands-on-keyboard adversary is present in the environment and may be attempting to cover their tracks or disrupt incident response efforts.\n\n<h3>Incident Response and Remediation</h3>\n<ul>\n<li><strong>Investigate the Source (Critical):</strong> 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.</li>\n<li><strong>Disable Scheduled Tasks/Run Keys:</strong> 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.</li>\n<li><strong>Assume Broader Compromise:</strong> 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.</li>\n</ul>",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [
    "HackTool.Shutdowner",
    "Riskware.Shutdown",
    "Win32/DoS.Shutdown"
  ],
  "enrichment_level": "insufficient_information",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1529"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-07-02T07:12:52Z",
  "type": "Riskware / HackTool",
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}