Suspicious Dero Miner Binaries nginx and cloud Execution

PremiumReviewedSigma · Medium · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-05-05
Updated
2026-08-28

ATT&CK techniques

Defense Evasion → Impact
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

What it detects

This rule detects execution of the Dero campaign binaries planted as usr bin nginx for propagation and usr bin cloud as the Dero miner. Naming the miner and worm after benign system tools hides them from operators reviewing running processes inside containers. The specific paths combined with these names are strong campaign indicators.

Related detections9 linkedT1496 — drag to rearrange
Malicious Cryptominer Masquerading as Kubernetes pause Container
Malicious Fake Fortinet Patch Infostealer Execution (via process_creation)
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)
Suspicious Masquerading Python Interpreter csshost Executing Script
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)
Suspicious Dero Miner Binaries nginx and cloud Execution
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.