Lion Cipher Lab

Characterize a cryptominer: CPU abuse, pool connections, and how it hides

Why it matters

A cryptominer is the quietest serious infection you will ever chase: it does not steal files or pop ransom notes, it just silently rents out your CPUs to mine coins into a stranger's wallet — so it can sit on a fleet for months, showing up only as slow machines, hot laptops and a puzzling power bill. The tell is a very specific behavioural fingerprint: one process pinning every core, a network connection to a mining pool, and a wallet string baked into the binary. Learning to read that fingerprint — and, crucially, to separate it from a legitimate render farm or build server that also runs…

What you'll learn

Steps in this lab

  1. The scene: a hot, slow machine and a bag of collected artifacts
  2. The two suspects: an unauthorized miner vs a legitimate CPU-heavy job
  3. Read the CPU signature: find the process pegging the cores
  4. The smoking gun: the stratum+tcp pool connection
  5. Attribution: the wallet and pool config inside the binary
  6. Persistence: read the scheduled-task export
  7. How it hides: a system-process name and throttling when you're active
  8. Map it to MITRE ATT&CK
  9. The third rule: miner vs false positive, why it throttles, and finding the rest

Open the full interactive lab →