Cpuminer
Table of Contents
Overview
Trojan:Win32/Cpuminer (often a generalized classification for multiple variants) represents a massive shift in cybercrime monetization: **Cryptojacking**. Instead of stealing data or demanding a ransom, Cpuminer silently hijacks the processing power (CPU/GPU) of the infected endpoint or server to mine cryptocurrency (most commonly Monero/XMR) and deposits the generated coins into the attacker's wallet.
Understanding Cpuminer (Cryptojacking)
To an end-user, a Cpuminer infection manifests as severe system sluggishness, loud cooling fans, and drastically reduced battery life on laptops. For an enterprise, a widespread cryptominer outbreak represents a massive theft of computing resources (driving up AWS/Azure cloud compute bills astronomically) and indicates a severe vulnerability that could easily be exploited to deploy ransomware instead.
Execution and Resource Hijacking Mechanics
Cpuminer variants are distributed via every conceivable vector: phishing, exploit kits, exposed RDP servers, and crucially, exploiting unpatched web servers (like WebLogic, Apache Struts, or vulnerable Docker APIs) (`T1190`). The payloads are often modified versions of open-source mining software like XMRig. Upon execution, the miner establishes persistence (via Scheduled Tasks or WMI event subscriptions) (`T1546.003`). It employs evasion tactics like 'Process Hollowing' (`T1055.012`) to hide the mining activity inside legitimate processes (like `svchost.exe` or `notepad.exe`). Advanced variants monitor Task Manager; if the user opens Task Manager to investigate the high CPU usage, the miner temporarily pauses its activity (`T1562.001`), resuming only when Task Manager is closed. The malware then utilizes nearly 100% of available CPU cycles (`T1496`) to calculate hashes, communicating continuously with a mining pool via the Stratum protocol (often over port 3333, 4444, or disguised as HTTPS/8080) (`T1071.001`).
Indicators of Compromise & Impact
The impact is hardware degradation, massive power consumption, and degraded server performance. Host-based IoCs include persistent 90-100% CPU usage by unrecognized or system processes, and EDR alerts for known mining command-line arguments (e.g., `-o stratum+tcp://... -u [wallet_address] -p x`). Network IoCs include continuous, long-lived connections to known mining pool domains (e.g., `minexmr.com`, `supportxmr.com`).
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1496 | Resource Hijacking (Cryptocurrency Mining) | Impact | ATT&CK ↗ |
T1055.012 | Process Injection: Process Hollowing (Hiding the miner) | Defense Evasion | ATT&CK ↗ |
T1071.001 | Application Layer Protocol (Stratum mining protocol) | Command and Control | ATT&CK ↗ |
T1190 | Exploit Public-Facing Application (Common entry vector for server miners) | Initial Access | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- 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):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-PHA | Process Hollowing Analysis | Detect | T1055.012 | Inspect unbacked executable memory regions (PAGE_EXECUTE_READWRITE) for replaced PE image headers inside legitimate host processes. |
D3-WAF | Web Content Filtering & Inspection | Filter | T1071.001 | Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles. |
D3-PEA | Processor Execution Auditing | Detect | T1496 | Alert on sustained high CPU/GPU utilization by processes originating from temporary user directories and block stratum mining pool ports. |
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:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_CPUMINER_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Cpuminer"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "cpuminer" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Cpuminer (Ransomware) Execution & Triage
id: 11d107b5-4d08-515f-9eb3-55c0ad65a9d6
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Cpuminer malware family. Detects volume shadow copy deletion, boot status
tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/cpuminer
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1055_012
- attack.t1071_001
- attack.t1190
- attack.t1496
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \vssadmin.exe
- \wmic.exe
- \wbadmin.exe
- \bcdedit.exe
CommandLine|contains:
- delete shadows
- shadowcopy delete
- resize shadowstorage
- recoveryenabled no
- ignoreallfailures
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: criticalTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_CPUMINER_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Cpuminer 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 = "cpuminer" 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.
- Isolate the endpoint or server; if it is a cloud instance, immediately take a snapshot and then shut down the instance to halt the billing impact.
- Use EDR or Sysinternals Process Explorer to identify the specific process consuming the CPU and terminate it.
- Block known mining pool domains and Stratum protocol ports (3333, 4444, etc.) at the perimeter firewall.
- Investigate the initial vector: cryptominers on servers almost always indicate an unpatched vulnerability or an exposed management interface (like RDP or SSH).
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not dismiss high CPU alerts as just 'bad performance'; investigate them as potential security incidents.
- Avoid simply killing the process and moving on; most modern miners have watchdogs (secondary scheduled tasks) that will restart the miner immediately.
References & External Analysis
- Search "cpuminer" on VirusTotal (External Analysis)
- Search "cpuminer" on Any.Run (Sandbox Sandbox)
- Search "cpuminer" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Cpuminer and what threat category does it belong to?
Cpuminer is classified as a Ransomware. 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.
How does Cpuminer establish persistence and evade defensive controls?
Cpuminer 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.
What are the essential incident response steps for mitigating a Cpuminer compromise?
Security teams responding to Cpuminer 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.
What cryptographic algorithms and file targeting techniques does Cpuminer employ during execution?
Cpuminer typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options.
Are decryptors available for Cpuminer, and what is the recommended recovery procedure?
Decryption availability for Cpuminer depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups.
How do I remove Cpuminer from Windows?
Manual removal of Cpuminer is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
What are the main symptoms of a Cpuminer infection?
Symptoms of Cpuminer can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Ransomwares
Want to prevent Cpuminer and similar threats from compromising your organization? Read our comprehensive defensive guide: Ransomware Containment & Incident Response.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/cpuminer.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.