Lion Cipher Lab

See through polymorphism: why two different-looking files are the same malware

Why it matters

A blue team that blocks malware by file hash is playing a game it cannot win. A packer wraps the real program in a randomized outer layer, so the attacker rebuilds the same malware a thousand times and gets a thousand different SHA-256 hashes and section layouts — every one sails past a hash blocklist and past static signatures tuned to the wrapper. This is one of the most common evasions in the wild, catalogued by MITRE as Software Packing (T1027.002). The skill that beats it is knowing where the malware's DURABLE identity actually lives: not in the mutating file on disk, but in the unpacked…

What you'll learn

Steps in this lab

  1. The paradox: two different files, one malware
  2. WHEN static hashing and signatures win — and WHEN they fail (the third rule)
  3. The setting: two invented samples in your isolated lab
  4. BEFORE — read the two files as they sit on disk
  5. The stub import table — the second, decisive tell
  6. AFTER — dump the unpacked payload from memory
  7. The invariant: signature the payload, not the wrapper
  8. The limits: what this analysis does NOT prove, and how a pro stays honest
  9. Recap: the decision you can now make

Open the full interactive lab →