Windows Process Creation: Command-Line Indicators of Crypto Mining

Alerts on Windows processes with command-line arguments matching common crypto miner pool and configuration indicators.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-10-26
Updated
2026-07-30

ATT&CK techniques

Impact
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

What it detects

This rule flags Windows process executions whose command line contains strings and parameters commonly seen in cryptocurrency miners, including pool URLs (e.g., stratum+tcp/udp), miner tuning options, and base64-encoded variants of the same. Such indicators are important because attackers often deploy miners via command-line arguments to establish pool communication and maximize resource usage. The detection relies on process creation telemetry with access to the full command line, matching specific substrings and excluding cases containing certain developer/build-related indicators.

Related detections9 linkedT1496 — drag to rearrange
Malicious Hadooken Cryptominer Execution via Masqueraded Binaries (via process_creation)
Suspicious Lucifer Botnet Mining Pool Domain Resolution (via dns_query)
Suspicious Proxyjacking Service Resolution Observed in perfctl Campaign (via dns_query)
Malicious PureMiner Persistence Executable in AppData HResult Folder
Suspicious T-Rex CoinMiner Binaries in Windows NT Program Files Folder (via file_event)
Malicious Cryptocurrency Miner Execution (via process_creation)
Possible Cryptomining Beacon to c3pool Mining Domain
Malicious XMRig Cryptominer Execution with NiceHash Pool Arguments
Suspicious Payload Execution From systemd-private Temporary Directory on Linux
Windows Process Creation: Command-Line Indicators of Crypto Mining
Pivot detection · T1496 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.