Psshell
Table of Contents
Overview
Executive Summary
PSShell refers to a category of offensive PowerShell scripts and frameworks (such as Nishang or Empire modules) designed to establish a remote, interactive command shell on a compromised Windows system. While PowerShell is a legitimate administrative tool, "PSShell" variants are specifically weaponized to evade detection, bypass execution policies, and provide threat actors with a powerful "Living off the Land" (LotL) mechanism for post-exploitation, lateral movement, and data exfiltration.Infection Vector and Technical Capabilities
PSShell scripts are rarely the initial infection vector. They are typically executed by an initial dropper (like a malicious macro) or deployed by an attacker who has already compromised an endpoint via RDP brute-forcing or vulnerability exploitation. Once deployed, PSShell frameworks exhibit advanced offensive capabilities:- Fileless Execution: PSShells are often executed entirely in memory using "Download Cradles" (e.g., `Invoke-Expression (New-Object Net.WebClient).DownloadString(...)`). This allows the attacker to establish a reverse shell without ever writing a `.ps1` script file to the hard drive, evading many traditional antivirus scanners.
- AMSI Evasion: Modern PSShell frameworks incorporate code specifically designed to hook and bypass the Windows Anti-Malware Scan Interface (AMSI), preventing Windows Defender from scanning the malicious PowerShell commands as they are executed.
- Post-Exploitation Framework: Once the shell is established, the attacker has unrestricted command-line access to the system. They can utilize built-in PowerShell cmdlets to dump credentials (e.g., Mimikatz modules), enumerate Active Directory, and pivot to other systems on the network.
Threat Assessment
The detection of an unauthorized PSShell is a critical incident indicating that an attacker has achieved interactive, command-line control over the endpoint. It signifies a mature compromise where the adversary is actively navigating the network and likely preparing for a larger objective, such as ransomware deployment or data theft.Incident Response and Remediation
- Behavioral Monitoring (EDR and Script Block Logging): Detection relies heavily on EDR telemetry and Windows Event Log 4104 (Script Block Logging). Analysts must review these logs to reconstruct the commands executed by the attacker during the PSShell session.
- Immediate Network Isolation: The endpoint must be isolated instantly to severe the reverse shell connection and halt the attacker's lateral movement.
- Total Re-imaging: Because the attacker had interactive command-line access, they could have established deep, secondary persistence mechanisms (like WMI event subscriptions or modified registry keys) that are difficult to uncover. A complete bare-metal wipe and re-image is required, alongside a global password reset.
Known aliases
Threat reports may refer to this family under multiple names:
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1059.001 | Command and Scripting Interpreter: PowerShell (Used in infection chain) | Execution | ATT&CK ↗ |
T1059 | Command and Scripting Interpreter | Execution | ATT&CK ↗ |
T1562.001 | Impair Defenses: Disable or Modify Tools | Defense Evasion | ATT&CK ↗ |
T1071.001 | Application Layer Protocol: Web Protocols (C2 Communication) | Command and Control | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1059: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
- T1059.001: Restrict execution of PowerShell. Enforce PowerShell Constrained Language Mode and Script Block Logging.
- 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):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-SEA | Script Execution Analysis | Detect | T1059 | Analyze script block syntax and command arguments at runtime to detect malicious automation. |
D3-PSBL | PowerShell Script Block Logging | Detect | T1059.001 | Enable PowerShell event ID 4104 and Constrained Language Mode to neuter obfuscated script payloads. |
D3-WAF | Web Content Filtering & Inspection | Filter | T1071.001 | Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
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:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_PSSHELL_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Psshell"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "psshell" ascii wide nocase
$s2 = "hacktool.psshell" ascii wide nocase
$s3 = "riskware.powershell" ascii wide nocase
$s4 = "trojan.powershell.reverseshell" ascii wide nocase
$s5 = "nishang" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}
Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Psshell (Ransomware) Execution & Triage
id: d2a00928-3586-55ac-9b43-360d9028b6be
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Psshell 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/psshell
- 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.t1059
- attack.t1562_001
- attack.t1071_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
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_PSSHELL_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Psshell 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 = "psshell" 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.
- Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Psshell from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
- Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Psshell symmetric encryption keys or uncompiled payload components may still reside in memory.
- 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 Psshell to inhibit recovery.
- 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.
- Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Psshell 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.
- Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Psshell.
- Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
- Do not connect clean backup drives or external storage to the affected network until Psshell eradication is completely verified.
References & External Analysis
- Search "psshell" on VirusTotal (External Analysis)
- Search "psshell" on Any.Run (Sandbox Sandbox)
- Search "psshell" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Psshell and what threat category does it belong to?
Psshell is classified as a Ransomware. 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.
How does Psshell establish persistence and evade defensive controls?
Psshell 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.
What are the essential incident response steps for mitigating a Psshell compromise?
Security teams responding to Psshell 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.
What cryptographic algorithms and file targeting techniques does HackTool.PSShell employ during execution?
HackTool.PSShell typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options.
Are decryptors available for HackTool.PSShell, and what is the recommended recovery procedure?
Decryption availability for HackTool.PSShell depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups.
How do I remove the Psshell Ransomware from Windows?
Manual removal of Psshell is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
Is Psshell a virus or a Ransomware?
Psshell is classified as a Ransomware. Unlike traditional viruses that infect files, modern malware like Psshell typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Psshell infection?
Symptoms of Psshell can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Ransomwares
Want to prevent Psshell and similar threats from compromising your organization? Read our comprehensive defensive guide: Ransomware Containment & Incident Response.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/psshell.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.