Pynamer

Category: trojan · Aliases: Trojan:Win32/Pynamer, Trojan.Pynamer, Trojan:Win32/Pynamer!ac, Win32/Pynamer · Sample count (EMBER 2018): 67 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Defense Evasion, ImpactFirst seen: 2018Actor: Unknown / CybercriminalIndustry: Healthcare, Critical Infrastructure, EnterpriseMotivation: Credential Theft & Unauthorized Access🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 8.1
Executive Summary
Pynamer (cataloged across security vendors and threat intelligence databases under signatures including Trojan:Win32/Pynamer, Trojan.Pynamer, and Trojan:Win32/Pynamer!ac) is a versatile family of compiled Python trojans active since 2018.

Table of Contents

Overview

Pynamer (cataloged across security vendors and threat intelligence databases under signatures including Trojan:Win32/Pynamer, Trojan.Pynamer, and Trojan:Win32/Pynamer!ac) is a versatile family of compiled Python trojans active since 2018. Packaged into standalone Windows Portable Executables using utilities like PyInstaller, cx_Freeze, or Py2exe, Pynamer encapsulates complete Python runtime environments and obfuscated bytecode to evade conventional static antivirus signatures. In the wild, Pynamer is distributed via malicious cracked software installers, game cheat tools, and malicious email attachments. Upon execution, the malware extracts its internal Python payload into %Temp%, establishes persistent autostart registry entries under Windows CurrentVersion\Run, and initiates encrypted C2 communications. Pynamer acts as an initial access stager, capable of capturing keystrokes, harvesting browser credentials, downloading secondary malicious payloads, and providing interactive backdoor shells.

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: Python-Based Information Stealers

Known Derivatives & Downstream Variants: Pynamer.A · Pynamer.Ac

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-EDAExecutable Deobfuscation AnalysisDetectT1027.002Deploy static entropy scanners and dynamic memory-unpacking heuristics to identify obfuscated and packed PE structures.
D3-SEAScript Execution AnalysisDetectT1059.006Analyze script block syntax and command arguments at runtime to detect malicious automation.
D3-FSFile Sandboxing (Attachment Detonation)IsolateT1566.001Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor.

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_PYNAMER_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Pynamer"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "pynamer" ascii wide nocase
        $s2 = "trojan:win32/pynamer" ascii wide nocase
        $s3 = "trojan.pynamer" ascii wide nocase
        $s4 = "trojan:win32/pynamer!ac" ascii wide nocase
        $s5 = "win32/pynamer" 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 - Pynamer (Trojan) Execution & Triage
id: ae55771e-7877-57be-a7ef-4f57f7e67126
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Pynamer 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/pynamer
- 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.t1027
- attack.t1059_006
- attack.t1547_001
- attack.t1105
- attack.t1555_003
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_PYNAMER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Pynamer 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 = "pynamer" 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. Quarantine the endpoint to halt the execution of the unpacked Python payload, which could be an infostealer or ransomware.
  2. Clear the Windows `%Temp%` directory, specifically looking for and deleting any `_MEIxxxxxx` folders created by the PyInstaller stub.
  3. Submit the original massive executable to a malware analyst for unpacking and decompilation to understand the specific threat.
  4. Perform a full system sweep to determine the initial delivery vector (e.g., a phishing email or a compromised download).

What to Avoid

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

  1. Do not waste time trying to statically analyze the original `.exe` file using standard dissassemblers; you must unpack the Python bytecode first.
  2. Avoid assuming the threat is contained just by deleting the `.exe`; the script may have already executed and established persistence elsewhere.

References & External Analysis

Frequently Asked Questions

What is Trojan:Win32/Pynamer?

Pynamer is a compiled Python trojan packaged as an executable that steals credentials and downloads malware.

How is Pynamer packaged to evade antivirus scanners?

It uses Python compilation tools like PyInstaller to bundle obfuscated bytecode inside standalone binaries.

What malicious capabilities does Pynamer possess?

It logs keystrokes, steals stored browser passwords, executes remote commands, and downloads secondary payloads.

How does Pynamer maintain persistence across Windows reboots?

It writes autostart entries to the Windows CurrentVersion\Run registry key.

How can systems be disinfected from Pynamer?

Quarantine the infected binary with antimalware software, clear %Temp% extraction folders, and remove startup registry keys.

How do I remove the Pynamer Trojan from Windows?

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

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

What are the main symptoms of a Pynamer infection?

Symptoms of Pynamer 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 Pynamer 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/pynamer.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.