Pshell

Overview

Trojan:PowerShell/Pshell is not a specific malware family, but a highly critical **Generic Heuristic Detection** focused entirely on the malicious abuse of the Windows PowerShell framework. Microsoft Defender and other AV engines use this classification when they detect a PowerShell script or command-line execution exhibiting behaviors that strongly indicate malicious intent, regardless of the specific payload being delivered.

Understanding Pshell (Living off the Land)
To an end-user, this detection usually appears as a blocked script execution in the background. For a security analyst, Pshell is a massive red flag indicating an attack utilizing 'Living off the Land' (LotL) techniques. By abusing PowerShell (`T1059.001`), attackers leverage a trusted, built-in system administration tool to download payloads, execute code in memory, and bypass traditional application whitelisting and file-based antivirus scanners.

Execution and Evasion Mechanics
The specific mechanics triggering a Pshell alert are vast. Common triggers include: obfuscated or heavily encoded PowerShell scripts (e.g., using Base64 encoding via the `-enc` or `-EncodedCommand` flags) (`T1027`); scripts that attempt to use `Invoke-WebRequest` or `Net.WebClient` to download executables directly into memory (fileless malware) (`T1105`); scripts attempting to bypass the Execution Policy (`-ExecutionPolicy Bypass`); or scripts containing known malicious cmdlets like `Invoke-ReflectivePEInjection` (often associated with tools like Empire or PowerSploit).

Indicators of Compromise & Impact
The impact depends entirely on what the PowerShell script was attempting to execute (ranging from a simple coinminer to a devastating ransomware deployment). Host-based IoCs are centered around the PowerShell operational event logs (Event IDs 4104, 4103) which must be analyzed to decode the obfuscated command that triggered the AV block. Network IoCs include the PowerShell process (`powershell.exe`) making anomalous outbound connections to download secondary payloads.

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.
• T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.

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_PSHELL_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Pshell"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "pshell" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Pshell (Ransomware) Execution & Triage
id: a37d687a-7849-56b0-995d-a1045f75199f
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Pshell 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/pshell
- 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.t1105
- attack.t1027
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_PSHELL_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Pshell 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 = "pshell" 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 review the Windows Event Logs (specifically PowerShell Operational logs, Event ID 4104 'Script Block Logging') to capture and decode the exact script that executed.
2. Isolate the endpoint if the decoded script indicates a successful payload execution (e.g., it dropped a file or established a reverse shell) before the AV could block it.
3. Analyze the decoded script to identify C2 domains or IP addresses and block them at the network perimeter.
4. Ensure PowerShell Constrained Language Mode is enforced and Script Block Logging is enabled across the enterprise.

What to Avoid

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

1. Do not ignore the alert assuming it is a benign admin script; heavily encoded or web-downloading PowerShell commands are rarely legitimate administrative tasks.
2. Avoid relying solely on file-based AV logs; you must investigate the PowerShell command line arguments and script blocks to understand the attack.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Asianraw
• Xdata
• Tftpd
• Cachedis
• Bero
• Winiga
• Nion
• Donloz

Machine-readable

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