Pliskal

Category: trojan · Aliases: Trojan:Win32/Pliskal, Trojan:Win32/Pliskal.A, TrojanDownloader:Win32/Pliskal, Win32/Pliskal, Backdoor.Win32.Pliskal · Sample count (EMBER 2018): 23 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Initial Access, Execution, Persistence, Command And ControlActor: Cybercriminal GroupsIndustry: Global / Opportunistic, Financial Services, Commercial EnterprisesMotivation: Financial Crime & Secondary Malware Distribution🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Pliskal (tracked across enterprise antivirus research telemetry under designations including Trojan:Win32/Pliskal, Trojan:Win32/Pliskal.A, and TrojanDownloader:Win32/Pliskal) is a stealthy Windows trojan downloader and backdoor.

Table of Contents

Overview

Pliskal (tracked across enterprise antivirus research telemetry under designations including Trojan:Win32/Pliskal, Trojan:Win32/Pliskal.A, and TrojanDownloader:Win32/Pliskal) is a stealthy Windows trojan downloader and backdoor. First observed in targeted cybercrime campaigns, Pliskal establishes a foothold on victim machines through malicious email attachments disguised as administrative invoices or bundled inside repackaged pirated utility installers. Upon execution, Pliskal performs defensive evasion routines, checking for the presence of virtualized sandbox environments and analysis debuggers. It establishes persistence by writing Run registry values under HKCU\Software\Microsoft\Windows\CurrentVersion\Run. Pliskal gathers basic host reconnaissance data—including machine hostname, Windows build version, local IP address, and installed security software—and transmits this telemetry to remote command-and-control (C2) servers via HTTP/HTTPS POST requests. In return, the C2 server issues instructions to download, stage, and execute secondary malicious payloads, including credential stealers, keyloggers, and ransomware, using CreateProcessW and ShellExecuteW APIs.

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:

→ 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-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-SDASystem Discovery AnalysisDetectT1082Alert on rapid enumerations of systeminfo, hostname, and registry hardware trees in short intervals.
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.

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_PLISKAL_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Pliskal"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "pliskal" ascii wide nocase
        $s2 = "trojan:win32/pliskal" ascii wide nocase
        $s3 = "trojan:win32/pliskal.a" ascii wide nocase
        $s4 = "trojandownloader:win32/pliskal" ascii wide nocase
        $s5 = "win32/pliskal" ascii wide nocase
        $s6 = "backdoor.win32.pliskal" 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 - Pliskal (Trojan) Execution & Triage
id: 149af7fe-4c68-5861-ae4e-3bd1b5e9f400
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Pliskal 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/pliskal
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_003
- attack.t1071_001
- attack.t1547_001
- attack.t1082
- attack.t1105
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_PLISKAL_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Pliskal 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 = "pliskal" 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 affected host from the local network and terminate active internet connections.
  2. Kill unauthorized processes executing from %APPDATA% or %TEMP% directories.
  3. Inspect and remove startup values under HKCU\Software\Microsoft\Windows\CurrentVersion\Run.
  4. Block outbound C2 IP addresses and domains at the enterprise firewall and DNS resolvers.
  5. Perform a complete endpoint security scan to identify and neutralize secondary payloads dropped by Pliskal.

What to Avoid

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

  1. Do not allow the infected system to maintain outbound internet access while investigating.
  2. Do not assume removing the initial dropper executable cleans the machine, as secondary payloads may have been installed.

References & External Analysis

Frequently Asked Questions

What is Trojan:Win32/Pliskal?

Pliskal is a Windows trojan downloader and backdoor designed to establish persistent access and deploy secondary malware payloads.

How does Pliskal achieve persistence on infected hosts?

It configures Windows Run registry keys under HKCU\Software\Microsoft\Windows\CurrentVersion\Run to trigger automatic execution at user logon.

What network protocols does Pliskal use for C2 communications?

Pliskal uses standard HTTP and HTTPS POST requests with encoded payloads to communicate with remote command-and-control servers.

How is Pliskal delivered to target systems?

It is delivered through weaponized spearphishing email attachments, malicious downloads, and Trojanized software packages.

What steps are required to eradicate a Pliskal infection?

Isolate the endpoint, terminate suspicious parent processes, delete unauthorized Run registry keys, remove staged binaries from %APPDATA%, and scan for secondary payloads.

How do I remove the Pliskal Trojan from Windows?

Manual removal of Pliskal 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 Pliskal a virus or a Trojan?

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

What are the main symptoms of a Pliskal infection?

Symptoms of Pliskal 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 Trojans

Want to prevent Pliskal and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan 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 Threat Intelligence Team.

Machine-readable

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