{
  "family": "xmrigminer",
  "sample_count": 2,
  "category": "advanced_threat",
  "description": "RiskTool:Win32/Xmrigminer (or simply XMRig) is a highly efficient, open-source CPU mining application designed to mine Monero (XMR) and other RandomX-based cryptocurrencies. While XMRig itself is legitimate software, it is the most frequently abused tool in 'Cryptojacking' attacks. Threat actors silently deploy XMRig onto compromised endpoints and cloud servers to steal computational resources, enriching themselves at the expense of the victim's hardware and electricity (`T1496`).<br><br><b>Understanding Xmrigminer (Cryptojacking)</b><br>To an end-user, the infection manifests as severe system sluggishness, loud cooling fans, and unresponsive applications, as the CPU is pinned at 100% utilization. For an enterprise, Cryptojacking represents a significant financial loss in the form of inflated cloud computing bills (if deployed in AWS/Azure) and premature hardware degradation, as well as a severe security failure, as the attacker had sufficient access to execute arbitrary code.<br><br><b>Execution and Abuse Mechanics</b><br>Attackers typically gain access via phishing, exploiting vulnerable web applications (e.g., unpatched Log4j, vulnerable WordPress plugins), or brute-forcing SSH/RDP. Once inside, they download the XMRig binary (often renaming it to look like a legitimate system process, e.g., `svchost.exe` or `java.exe` (`T1036.005`)). They configure XMRig via command-line arguments or a `config.json` file, pointing it to an attacker-controlled mining pool and providing their wallet address. To evade detection, advanced attackers use Process Hollowing to inject the XMRig code directly into memory, leaving no executable on disk, and configure the miner to pause if the user opens Task Manager (`T1562.001`).<br><br><b>Indicators of Compromise & Impact</b><br>The impact is resource exhaustion, financial loss, and reduced productivity. Host-based IoCs include prolonged 100% CPU utilization by unknown or strangely located processes (e.g., `svchost.exe` running from `%Temp%`), and the presence of `config.json` files containing mining pool URLs (like `minexmr.com` or `supportxmr.com`). Network IoCs involve constant, long-duration outbound TCP connections (often on ports 3333, 4444, or 5555, or disguised over port 443) communicating using the Stratum mining protocol.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Xmrigminer and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Xmrigminer is classified as a Advanced Threat. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments."
      }
    },
    {
      "@type": "Question",
      "name": "How does Xmrigminer establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Xmrigminer typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks."
      }
    },
    {
      "@type": "Question",
      "name": "What are the essential incident response steps for mitigating a Xmrigminer compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Xmrigminer should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups."
      }
    },
    {
      "@type": "Question",
      "name": "What lateral movement and credential access tactics does Xmrigminer leverage in enterprise intrusions?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Xmrigminer frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers."
      }
    },
    {
      "@type": "Question",
      "name": "How does Xmrigminer maintain covert communications and evade perimeter network monitoring?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Xmrigminer often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1496",
    "T1036.005",
    "T1562.001"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1496",
      "name": "Resource Hijacking (The core behavior of stealing CPU cycles to mine cryptocurrency)",
      "tactic": "Impact"
    },
    {
      "id": "T1036.005",
      "name": "Masquerading: Match Legitimate Name or Location (Renaming the miner to hide in plain sight)",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1562.001",
      "name": "Impair Defenses: Disable or Modify Tools (Configuring the miner to pause when Task Manager opens)",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "Terminate the offending process and isolate the machine. Cryptojacking implies the attacker had Remote Code Execution capabilities.",
    "Analyze the command-line arguments or `config.json` file of the miner to extract the mining pool URL and wallet address for threat intelligence.",
    "Investigate *how* the miner was deployed. If on a server, look for exploited web vulnerabilities or compromised administrative credentials.",
    "Implement network-level blocking (DNS sinkholing) for known cryptocurrency mining pools to render the malware useless even if executed."
  ],
  "what_to_avoid": [
    "Do not dismiss a cryptominer as a 'low severity' threat; the attacker who deployed it could easily have deployed ransomware instead.",
    "Avoid relying solely on CPU monitoring alerts, as advanced cryptojackers throttle their usage to stay below alerting thresholds (e.g., capping at 40% CPU)."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "execution",
    "persistence"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows Server 2022",
    "Windows Server 2019"
  ]
}