CyberKit

Polymorphism

Also called Polymorphic malware.

Malware that changes its appearance each time while keeping behavior.

What it is

Polymorphic malware mutates its outward form on each propagation (usually by re-encrypting its body and varying the decryptor) while the underlying logic stays the same. Every instance looks different on disk.

Why it matters

Constant byte-level change defeats static hash and signature matching, pushing detection toward behavior and the invariant decrypted core. Recognizing the stable payload beneath the mutation is what makes reliable signatures possible.

In practice

Two infections sharing identical behavior but no common file hash, because the body is re-encrypted with a fresh key each time.

What to look for

  • Different hashes for samples that behave the same.
  • Mutated decryptor stubs between samples.
  • Detections that only work on one variant.

Common mistake

Blocking by hash. Each copy has a new one, so detect behavior instead.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Ghidra Open source

    A disassembler and decompiler for reading what a sample's code actually does. Our notes.

  • YARA Open source

    Writes rules that match a family's code or strings across many files. Our notes.

  • VirusTotal Commercial

    Shows how many engines flag a file, plus its relations to domains and other samples.

  • ANY.RUN Commercial

    An interactive sandbox where you watch a sample run and click through what it asks for.

Read next

  • Crypter: A tool that encrypts a payload and decrypts it in memory at runtime.
  • Behavioral Signature: Detecting malware by what it does, not how its bytes look.
  • Byte Signature: A fixed byte sequence used to match a known sample on disk.

Sources