Plasma
Table of Contents
Overview
Backdoor:Win32/Plasma (often referring to the 'Plasma RAT') is a sophisticated Remote Access Trojan frequently sold on underground hacking forums. It provides an attacker with comprehensive, interactive control over a compromised Windows system. Unlike automated botnets, Plasma is designed for 'hands-on-keyboard' attacks, allowing a human operator to explore the file system, steal credentials, and pivot within a corporate network (`T1059`).
Understanding Plasma (Commercial RATs)
To an end-user, the infection is entirely invisible. For an incident response team, the presence of Plasma indicates an active, intelligent adversary is inside the network. Because the tool is commercially available (to criminals), the skill level of the attacker using it can range from a novice 'script kiddie' to an advanced ransomware affiliate preparing the environment for encryption.
Execution and Interactive Control Mechanics
Plasma is typically delivered via spearphishing campaigns (weaponized Office documents) or dropped by initial access brokers. Upon execution, it establishes persistence, often via Registry Run keys or hidden Scheduled Tasks (`T1547.001`). It establishes a reverse shell connection to the attacker's C2 server. The Plasma control panel provides the attacker with a GUI to execute a wide array of modules: file managers, registry editors, keyloggers (`T1056.001`), password dumpers (targeting browsers and FTP clients), and remote desktop (VNC) capabilities (`T1021.001`).
Indicators of Compromise & Impact
The impact is total loss of system confidentiality and a high likelihood of lateral movement. Host-based IoCs include EDR alerts for anomalous command-line execution (e.g., `cmd.exe` or `powershell.exe` spawning from unexpected parent processes), unauthorized access to credential stores, and the creation of hidden staging directories for exfiltration. Network IoCs include a persistent, encrypted outbound connection to an unknown IP address, with traffic volume spiking when the attacker is actively interacting with the system (e.g., viewing the desktop or downloading files).
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:
- T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
- T1059: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
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-RDP | RDP Access Controls & NLA | Harden | T1021.001 | Enforce Network Level Authentication (NLA) on RDP and restrict remote desktop ports via host firewalls. |
D3-EAF | Egress Analysis and Filtering | Isolate | T1041 | Enforce perimeter TLS inspection and alert on anomalous outbound data volume ratios transmitting over active C2 channels. |
D3-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
D3-SEA | Script Execution Analysis | Detect | T1059 | Analyze script block syntax and command arguments at runtime to detect malicious automation. |
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_PLASMA_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Plasma"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "plasma" 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 - Plasma (Ransomware) Execution & Triage
id: c6917352-4d18-5f41-b699-8aa5caa39a32
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Plasma 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/plasma
- 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.t1056_001
- attack.t1021_001
- attack.t1059
- attack.t1041
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_PLASMA_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Plasma 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 = "plasma" 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.
- Isolate the machine immediately to sever the attacker's interactive control over the system.
- Assume all credentials present on the machine (saved passwords, active session tokens, domain credentials) have been compromised and force a reset.
- Hunt across the network for the specific C2 IP address to identify other endpoints the attacker may have pivoted to using stolen credentials.
- Capture a memory dump before remediation to analyze the running Plasma configuration and identify any dropped secondary modules.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the attack is over once the RAT is removed; the attacker likely created secondary backdoor accounts or dropped other persistence mechanisms.
- Avoid relying solely on static AV signatures, as the Plasma builder allows attackers to easily obfuscate and repack the payload.
References & External Analysis
- Search "plasma" on VirusTotal (External Analysis)
- Search "plasma" on Any.Run (Sandbox Sandbox)
- Search "plasma" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Plasma and what threat category does it belong to?
Plasma 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 Plasma establish persistence and evade defensive controls?
Plasma 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 Plasma compromise?
Security teams responding to Plasma 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 Plasma employ during execution?
Plasma 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 Plasma, and what is the recommended recovery procedure?
Decryption availability for Plasma 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 Plasma Ransomware from Windows?
Manual removal of Plasma 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 Plasma a virus or a Ransomware?
Plasma is classified as a Ransomware. Unlike traditional viruses that infect files, modern malware like Plasma typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Plasma infection?
Symptoms of Plasma 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 Plasma 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/plasma.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.