{
  "family": "qjwmonkey",
  "sample_count": 190,
  "category": "trojan_generic",
  "description": "TrojanDownloader:Win32/Qjwmonkey is a persistent, targeted trojan downloader historically focused on Asian markets, engineered to silently bypass security controls and deliver severe secondary payloads.<br><br><b>What is Qjwmonkey?</b><br>To the victim, Qjwmonkey operates entirely invisibly. For threat intelligence analysts, it represents a specialized 'Initial Access Broker' tool. Its primary function is not direct data theft, but establishing a highly reliable, undetected bridgehead on the endpoint. It profiles the system, ensures it is not running in an analysis environment, and then reaches out to its Command-and-Control (C2) server to pull down the final payload, which is often a banking trojan or a specialized RAT.<br><br><b>Execution and Evasion Strategies</b><br>Qjwmonkey is typically distributed via spearphishing campaigns mimicking local financial institutions or embedded within compromised software installers on regional forums. Upon execution, it utilizes intense packing and dynamic API resolution to evade static antivirus signatures. It drops a randomized executable into the <code>%AppData%</code> or <code>%Temp%</code> directories. Persistence is achieved by creating a hidden scheduled task. Crucially, Qjwmonkey frequently injects its downloading routine into legitimate system processes (like <code>explorer.exe</code> or <code>svchost.exe</code>) to mask its outbound network traffic, making its C2 communications blend in with normal HTTP/HTTPS 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 Qjwmonkey reaching out to newly registered domains or compromised WordPress sites. The presence of unexpected, hidden scheduled tasks designed to execute highly entropic binaries in the user's profile is a strong IoC.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1053.005",
    "T1497.001",
    "T1105",
    "T1055",
    "T1027"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1105",
      "name": "Ingress Tool Transfer",
      "tactic": "Command and Control"
    },
    {
      "id": "T1055",
      "name": "Process Injection",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1053.005",
      "name": "Scheduled Task/Job: Scheduled Task",
      "tactic": "Persistence"
    },
    {
      "id": "T1497.001",
      "name": "Virtualization/Sandbox Evasion: System Checks",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1027",
      "name": "Obfuscated Files or Information",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "Isolate the endpoint immediately to prevent Qjwmonkey from downloading and executing its secondary payloads (e.g., banking trojans).",
    "Audit the Windows Task Scheduler and Registry Run keys to identify and remove the Qjwmonkey persistence mechanisms.",
    "Review firewall and proxy logs to identify the C2 domains Qjwmonkey attempted to contact, and block them enterprise-wide.",
    "Capture a live memory image (RAM dump) to extract the injected Qjwmonkey modules and identify the secondary payloads."
  ],
  "what_to_avoid": [
    "Do not close an incident simply because the initial Qjwmonkey dropper was quarantined; always verify if secondary payloads were downloaded.",
    "Avoid relying solely on manual 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"
  ]
}