{
  "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": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Shutdowner and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Shutdowner is classified as a Backdoor. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments."
      }
    },
    {
      "@type": "Question",
      "name": "How does Shutdowner establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Shutdowner typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks."
      }
    },
    {
      "@type": "Question",
      "name": "What are the essential incident response steps for mitigating a Shutdowner compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Shutdowner should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups."
      }
    },
    {
      "@type": "Question",
      "name": "What remote administrative and surveillance capabilities does HackTool.Shutdowner provide to threat actors?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "As an interactive backdoor and remote access tool, HackTool.Shutdowner grants operators comprehensive control over the victim host. Common surveillance and management modules include real-time keystroke logging, desktop screen capture, remote VNC streaming, webcam and audio recording, arbitrary shell command execution, reverse proxy pivoting, and bidirectional file transfer capabilities."
      }
    },
    {
      "@type": "Question",
      "name": "How does HackTool.Shutdowner traverse firewalls and sustain resilient command-and-control (C2) connections?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "HackTool.Shutdowner establishes persistent outbound TCP or TLS connections back to threat actor infrastructure, effectively bypassing inbound firewall filtering. To maintain connection resilience against IP takedowns, variants frequently employ dynamic DNS services, fallback command servers, encrypted dead-drop resolvers on social platforms, or DNS over HTTPS (DoH) querying."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1529",
    "T1071.001",
    "T1547.001",
    "T1055",
    "T1056.001"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-10-15",
  "type": "Riskware / HackTool",
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "persistence",
    "command_and_control",
    "remote_access"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "mitre_attack_detail": [
    {
      "id": "T1529",
      "name": "System Shutdown/Reboot (Forcing a restart to trigger the unbootable state)",
      "tactic": "Impact"
    },
    {
      "id": "T1071.001",
      "name": "Application Layer Protocol: Web Protocols (C2 Communication)",
      "tactic": "Command and Control"
    },
    {
      "id": "T1547.001",
      "name": "Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder",
      "tactic": "Persistence"
    },
    {
      "id": "T1055",
      "name": "Process Injection",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1056.001",
      "name": "Keylogging",
      "tactic": "Credential Access"
    }
  ],
  "containment_steps": [
    "Immediately isolate the compromised host from internal LAN and WAN environments to cut off interactive remote shell sessions established by Shutdowner.",
    "Inspect active socket listeners and outbound established network connections ('netstat -ano') to identify and sever covert TCP/UDP channels used by Shutdowner.",
    "Scan Windows Services, Scheduled Tasks, and Startup folders to locate and eliminate persistent backdoor listeners configured by Shutdowner.",
    "Invalidate all active VPN profiles, local administrator credentials, and session tokens that may have been harvested by the Shutdowner operator.",
    "Re-image the affected host using a validated golden image prior to reconnecting it to enterprise network segments."
  ],
  "what_to_avoid": [
    "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.",
    "Avoid relying solely on static file signatures, as Shutdowner payloads frequently execute reflectively in memory without writing binaries to disk."
  ],
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows Server 2022",
    "Windows Server 2019"
  ]
}