Plugx

Category: rat · Aliases: PlugX, Korplug, Sogu, Trojan.PlugX, Win32/PlugX, Backdoor.PlugX · Sample count (EMBER 2018): 8 · Enrichment: curated_sourced · Updated: 2026-06-09
Category: RatStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2012Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
PlugX (also known across threat intelligence teams as Korplug or Sogu) is an exceptionally sophisticated, highly modular Remote Access Trojan first observed in 2012.

Table of Contents

Overview

PlugX (also known across threat intelligence teams as Korplug or Sogu) is an exceptionally sophisticated, highly modular Remote Access Trojan first observed in 2012. Developed as a successor to legacy Chinese espionage tools like Gh0st RAT and Poison Ivy, PlugX has served as the flagship post-exploitation framework for numerous Chinese state-sponsored advanced persistent threat (APT) groups, including Mustang Panda (Bronze President / HoneyMyte), APT41 (Barium / Winnti), APT26, and APT10 (Stone Panda). PlugX is renowned for popularizing the 'triad' technique of DLL side-loading: threat actors pair a legitimate, cryptographically signed third-party executable (such as legitimate binaries from McAfee, Kaspersky, Symantec, or Microsoft) with a malicious proxy DLL and an encrypted payload blob (.dat or .bin). When the trusted binary executes, Windows automatically loads the attacker's DLL, which decrypts and injects the PlugX shellcode directly into memory, evading traditional endpoint file-scanning defenses. In 2024, French cybersecurity firm Sekoia, in coordination with the French National Police (DGGN) and Europol, spearheaded a monumental international cleanup operation: researchers sinkholed the master C2 server commanding a self-propagating USB-worm variant of PlugX (Sogu), sending benign disinfection commands that disarmed over 3 million infected hosts across 100+ countries worldwide.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Gh0St Rat · Poison Ivy

Known Derivatives & Downstream Variants: Plugx Type I · Plugx Type Ii · Plugx Type Iii · Plugx P2P · Plugx / Sogu Usb Worm

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-EAFEgress Analysis and FilteringIsolateT1041Enforce perimeter TLS inspection and alert on anomalous outbound data volume ratios transmitting over active C2 channels.
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsHTTP, HTTPS, DNS Tunneling, Raw TCP, UDP, Custom Encrypted Triad Protocol
Observed ports80, 443, 53, 8080, 13579
Infrastructure modelMulti-tiered dynamic DNS and VPS proxy infrastructure with encrypted C2 beacons using XOR, RC4, or custom additive decompression algorithms to transmit exfiltrated files and execute remote shell commands.
Identifiable from traffic aloneUnrated

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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_PLUGX_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Plugx"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "plugx" ascii wide nocase
        $s2 = "plugx" ascii wide nocase
        $s3 = "korplug" ascii wide nocase
        $s4 = "sogu" ascii wide nocase
        $s5 = "trojan.plugx" ascii wide nocase
        $s6 = "win32/plugx" ascii wide nocase
        $s7 = "backdoor.plugx" 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 - Plugx (Rat) Execution & Triage
id: 5c8691ef-bd4b-5cf8-bd05-e811b00e1e11
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Plugx malware family. Detects unauthorized persistence creation via Windows
  Registry Run keys, scheduled tasks, and privilege escalation indicative of RAT installations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/plugx
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.rat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1574_002
- attack.t1055
- attack.t1091
- attack.t1071_001
- attack.t1056_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \reg.exe
    - \schtasks.exe
    - \cmd.exe
    - \powershell.exe
    CommandLine|contains:
    - \CurrentVersion\Run
    - /create /tn
    - bypass -enc
    - net user /add
    - net localgroup administrators
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_PLUGX_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Plugx 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 = "plugx" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Instantly isolate the endpoint, but assume the adversary is already established elsewhere in the network; PlugX is an APT tool.
  2. Capture a full forensic memory dump (RAM) before shutting down the machine, as the active PlugX payload and its plugins reside entirely in memory.
  3. Perform a massive enterprise-wide hunt for the specific legitimate executable (the side-loading host) and the malicious DLL.
  4. Enforce immediate password resets for all accounts associated with the compromised user, prioritizing privileged access.

What to Avoid

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

  1. Do not assume the attack is over by deleting the side-loading files; APT actors frequently establish secondary, redundant backdoors (like webshells).
  2. Avoid noisy remediation; coordinate a synchronized response, as tipping off the APT may cause them to rapidly exfiltrate data or deploy destructive payloads to cover their tracks.

References & External Analysis

Frequently Asked Questions

What is PlugX / Korplug?

PlugX is a modular Remote Access Trojan heavily used by Chinese state-sponsored APT groups since 2012 for espionage, credential theft, and network reconnaissance.

How does PlugX use DLL side-loading?

PlugX uses a 'triad' structure: a legitimate signed software executable loads a malicious companion DLL, which decrypts and injects the PlugX payload directly into memory without file-based detection.

What was the 2024 global PlugX disinfection operation?

In 2024, French security firm Sekoia and Europol seized PlugX C2 infrastructure and sent self-deleting commands that safely cleaned over 3 million USB-infected devices worldwide.

Which threat groups deploy PlugX?

Major threat actors include Mustang Panda (Bronze President), APT41 (Winnti), APT10, and APT26, targeting government, defense, and telecommunications sectors.

How can defenders identify PlugX DLL side-loading?

Monitor for signed binaries loading DLLs from non-standard user directories, inspect process memory for decrypted PE headers, and scan external USB media for unauthorized LNK shortcut files.

How do I remove the Plugx Rat from Windows?

Manual removal of Plugx 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 Plugx a virus or a Rat?

Plugx is classified as a Rat. Unlike traditional viruses that infect files, modern malware like Plugx typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Plugx infection?

Symptoms of Plugx 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 Rats

Want to prevent Plugx and similar threats from compromising your organization? Read our comprehensive defensive guide: Backdoor & RAT Protection for Businesses.

📣 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.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

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