Xmrigminer

Overview

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`).

Understanding Xmrigminer (Cryptojacking)
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.

Execution and Abuse Mechanics
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`).

Indicators of Compromise & Impact
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.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1036.005: Monitor for executable files running from unusual paths or with deceptive names. Use EDR to detect process masquerading.

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_XMRIGMINER {
    meta:
        description = "Detects Xmrigminer (advanced_threat)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "xmrigminer" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Xmrigminer Activity
id: 55c06aef42552cacdceae1599ca60be4
status: experimental
description: Detects generic indicators of the xmrigminer malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*xmrigminer*"
    condition: selection
level: medium

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

1. Terminate the offending process and isolate the machine. Cryptojacking implies the attacker had Remote Code Execution capabilities.
2. Analyze the command-line arguments or `config.json` file of the miner to extract the mining pool URL and wallet address for threat intelligence.
3. Investigate *how* the miner was deployed. If on a server, look for exploited web vulnerabilities or compromised administrative credentials.
4. Implement network-level blocking (DNS sinkholing) for known cryptocurrency mining pools to render the malware useless even if executed.

What to Avoid

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

1. Do not dismiss a cryptominer as a 'low severity' threat; the attacker who deployed it could easily have deployed ransomware instead.
2. Avoid relying solely on CPU monitoring alerts, as advanced cryptojackers throttle their usage to stay below alerting thresholds (e.g., capping at 40% CPU).

References & External Analysis

• Search "xmrigminer" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: advanced_threat)

Explore other malware families in the same category:

• Addmepoint
• Cardtool
• Hostmodifier
• Pontoeb
• Hostschanger

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/xmrigminer.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.