{
  "family": "ipamor",
  "sample_count": 147,
  "category": "trojan_generic",
  "description": "Backdoor:Win32/Ipamor is a highly stealthy, targeted Remote Access Trojan (RAT) engineered to provide attackers with persistent, interactive control over compromised endpoints, specifically designed for corporate espionage and data exfiltration.<br><br><b>Understanding Ipamor</b><br>To the victim, Ipamor provides zero visual indicators of compromise. For threat intelligence analysts, Ipamor represents a capable, mid-tier backdoor frequently utilized in targeted attacks. It is designed to bypass initial security controls, harvest comprehensive system intelligence, and maintain a highly covert Command-and-Control (C2) channel.<br><br><b>Execution and Evasion Strategies</b><br>Ipamor is typically delivered via spearphishing campaigns containing weaponized Office documents or dropped as a secondary payload by exploit kits. Upon execution, it utilizes heavy packing and dynamic API resolution to evade static antivirus signatures. It drops a randomized executable into the <code>%AppData%</code> or <code>%SystemRoot%</code> directories. Persistence is achieved by creating a hidden scheduled task or modifying the Registry Run keys. Ipamor frequently injects its core modules into legitimate system processes (like <code>svchost.exe</code>) to mask its outbound network traffic.<br><br><b>Indicators of Compromise (IoCs)</b><br>Threat hunters should investigate EDR alerts for 'Suspicious Process Injection' or 'Anomalous Child Process Spawning'. Network logs will often reveal Ipamor reaching out to compromised domains using custom-encrypted HTTP/HTTPS traffic. The presence of unexpected, hidden scheduled tasks designed to execute randomly named binaries in the user's profile is a strong IoC. Memory analysis is absolutely crucial to extract the injected modules and identify the specific C2 infrastructure.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1053.005",
    "T1547.001",
    "T1105",
    "T1055",
    "T1027"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1055",
      "name": "Process Injection",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1105",
      "name": "Ingress Tool Transfer",
      "tactic": "Command and Control"
    },
    {
      "id": "T1547.001",
      "name": "Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder",
      "tactic": "Persistence"
    },
    {
      "id": "T1053.005",
      "name": "Scheduled Task/Job: Scheduled Task",
      "tactic": "Persistence"
    },
    {
      "id": "T1027",
      "name": "Obfuscated Files or Information",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "Instantly isolate the endpoint from the network to sever the attacker's interactive, remote-control session.",
    "Capture a full forensic memory image of the machine to extract the decrypted Ipamor payload and its C2 configuration.",
    "Audit the Windows Task Scheduler and Registry Run keys to identify and remove the Ipamor persistence mechanisms.",
    "Assume total endpoint compromise; perform a clean OS rebuild and force global password resets for all accounts that accessed the machine."
  ],
  "what_to_avoid": [
    "Do not leave the machine connected to the network during triage; the attacker has live access and will likely destroy evidence or move laterally.",
    "Avoid relying solely on static file deletion, as the injected processes will likely just recreate the dropped binaries."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}