Lion Cipher Lab

Read a sample's mutex and host fingerprint: how malware IDs the machine and avoids double-infection

Why it matters

Two of the very first things a lot of Windows malware does are so mundane that beginners skip right past them in a report — it creates a named mutex, and it reads a handful of facts about the machine. But those two behaviors answer the two questions the operator most needs answered: 'have I already got this box?' and 'which box is this?' The mutex is a one-line infection marker: create it, and if it already exists, exit — so the malware never runs twice on the same host and never trips over itself. The fingerprint (computer name, user name, machine GUID, volume serial, CPU/BIOS strings,…

What you'll learn

Steps in this lab

  1. The two mundane behaviors that answer the operator's two big questions
  2. Your scenario and your artifacts (analyst's chair)
  3. The API trace — read the mutex as an infection marker
  4. The mutex as a detection AND a vaccine (and its first limit)
  5. The fingerprint fields — which API produced each fact
  6. The decoded bot-ID — how the fields become one identifier
  7. The locale guardrail — refuse to run in certain countries
  8. The judgment: when the mutex + fingerprint win, when they're fooled, and how a pro finishes

Open the full interactive lab →