Powerun

Overview

Executive Summary

Technical Architecture and Exploitation

• Execution Policy Bypass: By default, Windows restricts the execution of unsigned PowerShell scripts. Powerun tools often execute PowerShell using the `-ExecutionPolicy Bypass` flag or instantiate the PowerShell runspace directly within a custom C# or C++ executable to completely ignore local Group Policy restrictions.
• Obfuscation and Fileless Execution: Powerun wrappers frequently decode heavily obfuscated (Base64) PowerShell scripts and execute them directly in memory (`-EncodedCommand`). This means the actual malicious payload never touches the hard drive, rendering static disk scanning ineffective.
• AMSI Evasion: Advanced Powerun utilities attempt to patch or disable the Anti-Malware Scan Interface (AMSI) in memory before executing the PowerShell script, blinding the EDR solution to the script's contents.

Threat Impact

Defense and Resilience Strategies

• Constrained Language Mode (CLM): The most effective defense against malicious PowerShell usage is enforcing Constrained Language Mode via Windows Defender Application Control (WDAC). CLM severely restricts the APIs and COM objects that PowerShell can access, neutralizing most offensive scripts.
• Script Block Logging: Enable PowerShell Script Block Logging (Event ID 4104). This forces the OS to log the *de-obfuscated* content of the script as it executes, providing invaluable telemetry for incident responders.
• Behavioral Monitoring: Monitor EDR telemetry for suspicious parent-child process relationships, such as Word (`winword.exe`) or Excel (`excel.exe`) unexpectedly spawning `powershell.exe` with encoded command-line arguments.

Known aliases

Threat reports may refer to this family under multiple names:

• HackTool.Powerun
• Riskware.PowerShellRunner
• Trojan.Powerun

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:

• T1059.001: Restrict execution of PowerShell. Enforce PowerShell Constrained Language Mode and Script Block Logging.

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

title: SystemHelpDesk Detection - Powerun (Ransomware) Execution & Triage
id: eeaf75b1-632f-53be-a1ab-fb98bb917fbd
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Powerun malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/powerun
- 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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_001
- attack.t1222_001
- attack.t1562_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

rule MALWARE_WIN_POWERUN_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Powerun 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 = "powerun" 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 affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Powerun from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
2. Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Powerun symmetric encryption keys or uncompiled payload components may still reside in memory.
3. Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Powerun to inhibit recovery.
4. Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.
5. Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Powerun binary and related persistence hooks are eradicated.

What to Avoid

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

1. Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Powerun.
2. Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
3. Do not connect clean backup drives or external storage to the affected network until Powerun eradication is completely verified.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Oztar
• Bredo
• Anserin
• Jord
• Malmaker
• Keydownload
• Refroso
• Renaz

Machine-readable

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