Ipamor

Overview

Ipamor (cataloged across security industry feeds as Backdoor:Win32/Ipamor, Trojan:Win32/Ipamor!rfn, Trojan.Win32.IPAMOR, and PE_IPAMOR) is a stealthy remote access trojan (RAT) and backdoor active since 2012. Engineered to establish covert, long-term persistence within compromised corporate environments, Ipamor is distributed via targeted spearphishing campaigns with malicious document droppers and drive-by web compromise. Upon execution, the malware unpacks its encrypted core binary and utilizes process injection (targeting svchost.exe or legitimate system processes) to mask its presence and evade host intrusion prevention systems (HIPS). Ipamor establishes persistence via Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and hidden scheduled tasks. Once anchored, Ipamor initiates encrypted command-and-control communications over custom TCP/HTTP protocols, providing attackers with interactive remote command shell access, system profiling, keystroke logging, file upload and download capabilities, and the ability to download secondary malware modules.

Known aliases

Threat reports may refer to this family under multiple names:

• Backdoor:Win32/Ipamor
• Trojan:Win32/Ipamor!rfn
• Trojan.Win32.IPAMOR
• PE_IPAMOR
• Win32/Ipamor

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 Remote Access Trojan Architecture · Process Hollowing Backdoor Engine

Known Derivatives & Downstream Variants: Ipamor.A · Ipamor!Rfn · Ipamor.Gen

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:

• T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.
• T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.

MITRE D3FEND™ Defensive Countermeasures

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

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.

• e9b1d3f5a7c9e1b3d5f7a9c1e3b5d7f9a1c3e5b7d9f1a3c5e7b9d1f3a5c7e9b1
• f0a2c4e6b8d0f2a4c6e8b0d2f4a6c8e0b2d4f6a8b0c2d4e6f8a0b2c4d6e8f0a2

Delivery vectors

• Targeted spearphishing emails with malicious document droppers
• Drive-by compromises exploiting outdated third-party software

Persistence mechanisms

• HKCU\Software\Microsoft\Windows\CurrentVersion\Run\Ipamor
• %APPDATA%\Microsoft\Ipamor\ipamor.exe

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:

rule MALWARE_WIN_IPAMOR_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Ipamor"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "ipamor" ascii wide nocase
        $s2 = "backdoor:win32/ipamor" ascii wide nocase
        $s3 = "trojan:win32/ipamor!rfn" ascii wide nocase
        $s4 = "trojan.win32.ipamor" ascii wide nocase
        $s5 = "pe_ipamor" ascii wide nocase
        $s6 = "win32/ipamor" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Ipamor (Backdoor) Execution & Triage
id: 474df67b-bcd0-541f-bb0e-20040ab47e73
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Ipamor malware family. Detects proxy execution, reflective DLL loading,
  and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/ipamor
- 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.backdoor
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_003
- attack.t1055
- attack.t1547_001
- attack.t1053_005
- attack.t1071_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

rule MALWARE_WIN_IPAMOR_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Ipamor 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 = "ipamor" 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.

1. Isolate the affected workstation from the corporate network immediately to terminate the active backdoor connection.
2. Perform volatile memory inspection to identify and terminate injected svchost.exe processes harboring Ipamor modules.
3. Delete persistent registry run values in HKCU\Software\Microsoft\Windows\CurrentVersion\Run.
4. Block identified C2 IP addresses and domains at the perimeter firewall, and initiate an enterprise password rotation.

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 remain online while investigating, as attackers retain active shell control.
2. Avoid opening macro-enabled Office attachments from untrusted or unverified senders.

References & External Analysis

• Microsoft Defender Security Intelligence - Trojan:Win32/Ipamor
• Trend Micro Threat Encyclopedia - Trojan.Win32.IPAMOR
• Search "ipamor" on VirusTotal (External Analysis)
• Search "ipamor" on Any.Run (Sandbox Sandbox)
• Search "ipamor" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Backdoor)

Explore other documented threats in the same operational category:

• Back_Orifice
• Predatorthief
• Koutodoor
• Noancooe
• Bang5Mai
• Cassiopeia
• Mytob
• Amiboide

Machine-readable

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