Pluto

Category: worm · Aliases: Worm:Win32/Pluto, Trojan:Win32/Pluto, W32.Pluto, Worm.Win32.Pluto, Win32/Pluto · Sample count (EMBER 2018): 209 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: WormStatus: Automated SignaturePlatform: WINDOWS_PEStage: Lateral Movement, Persistence, ExecutionFirst seen: 2006Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Unauthorized Access🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 10, Windows 7, Windows XP
Executive Summary
Pluto (identified in security intelligence under signatures including Worm:Win32/Pluto, Trojan:Win32/Pluto, W32.Pluto, and Worm.Win32.Pluto) is a hybrid Windows worm and backdoor trojan that emerged in 2006.

Table of Contents

Overview

Pluto (identified in security intelligence under signatures including Worm:Win32/Pluto, Trojan:Win32/Pluto, W32.Pluto, and Worm.Win32.Pluto) is a hybrid Windows worm and backdoor trojan that emerged in 2006. Designed for widespread propagation and long-term endpoint control, Pluto self-replicates across external removable media (USB thumb drives and flash memory) and open local network shares. The worm drops disguised executable copies into drive root directories alongside weaponized autorun.inf files, masquerading as folder icons or legitimate system files to lure users into launching the payload. Upon execution, Pluto drops system binaries into %SYSTEM32% or %APPDATA%, creates autostart registry entries under the Run key, and establishes persistence through scheduled tasks. The payload connects back to remote command-and-control (C2) servers over HTTP or TCP, allowing operators to execute remote commands, manipulate system files, terminate running security tools, and download secondary malware droppers or cryptominers.

Known aliases

Threat reports may refer to this family under multiple names:

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: Win32 Removable Media Worm Family · Modular Usb Infection Engine

Known Derivatives & Downstream Variants: Pluto.A · Pluto.B · Pluto.Gen

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-BDABinary De-obfuscation & UnpackingAnalyzeT1027Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation.
D3-STMScheduled Task Creation AnalysisDetectT1053.005Audit task creation targeting system and hidden service directories; verify task author credentials.
D3-RMCRemovable Media Access ControlHardenT1091Enforce Group Policy settings disabling Windows autorun and block execution permissions on removable USB storage media.
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

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_PLUTO_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Pluto"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "pluto" ascii wide nocase
        $s2 = "worm:win32/pluto" ascii wide nocase
        $s3 = "trojan:win32/pluto" ascii wide nocase
        $s4 = "w32.pluto" ascii wide nocase
        $s5 = "worm.win32.pluto" ascii wide nocase
        $s6 = "win32/pluto" 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 - Pluto (Worm) Execution & Triage
id: c706daaf-5b3f-5ab4-b1ba-b54c2c3397d2
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Pluto malware family. Detects suspicious execution from temporary user
  directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/pluto
- 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.worm
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1091
- attack.t1547_001
- attack.t1053_005
- attack.t1105
- attack.t1027
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_PLUTO_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Pluto 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 = "pluto" 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. Disconnect the infected system from the local network and unplug all connected USB and external storage media.
  2. Sanitize connected flash drives using non-Windows analysis environments to remove malicious autorun.inf and disguised binaries.
  3. Delete persistent registry entries under HKCU and HKLM Run keys and remove scheduled tasks referencing pluto.exe.
  4. Perform a full antimalware scan to eliminate secondary binaries dropped during the C2 session.

What to Avoid

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

  1. Do not insert infected USB thumb drives into other workstations without disabling Windows AutoRun/AutoPlay.
  2. Avoid executing unverified files appearing disguised as folders or system utilities on external drives.

References & External Analysis

Frequently Asked Questions

What is the Pluto malware family?

Pluto is a Windows worm and backdoor trojan that spreads via USB drives and network shares.

How does Pluto spread between computers?

It infects removable flash drives with autorun.inf files and copies itself across writable network shares.

What remote capabilities are provided by Pluto?

Attackers can remotely execute commands, tamper with files, disable antivirus software, and drop secondary payloads.

How does Pluto establish persistence?

It adds registry autostart keys under HKCU Run and creates automated Windows scheduled tasks.

How can systems be defended against Pluto?

Disable Windows AutoRun/AutoPlay for removable media, restrict open network shares, and deploy updated antivirus definitions.

How do I remove the Pluto Worm from Windows?

Manual removal of Pluto 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 Pluto a virus or a Worm?

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

What are the main symptoms of a Pluto infection?

Symptoms of Pluto 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 Worms

Want to prevent Pluto and similar threats from compromising your organization? Read our comprehensive defensive guide: Worm & Virus Protection.

📣 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 Threat Intelligence Team.

Machine-readable

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