CyberKit

Crypter

Also called Crypter stub.

A tool that encrypts a payload and decrypts it in memory at runtime.

What it is

A crypter wraps a malicious payload in encryption and bundles a stub that decrypts and runs it directly in memory. The goal is to defeat static signatures and on-disk scanning until execution.

Why it matters

Crypters let one payload spawn countless undetected on-disk variants, frustrating hash- and signature-based detection. Analysts usually have to run or debug the stub to recover the real payload, then signature that instead.

In practice

A sample whose only static logic is a decryption stub; the actual stealer appears only after the crypter unpacks it in memory.

What to look for

  • High entropy payloads with a small decryption stub.
  • Memory allocation followed by writing and running decrypted code.
  • The same stub across unrelated malware families.

Common mistake

Attributing by the crypter. Many crews buy the same service, so it says little about who is behind it.

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

  • Manual Unpacking: Reversing a packer by hand to recover the real payload.
  • Polymorphism: Malware that changes its appearance each time while keeping behavior.
  • PE Section: A named region of a PE holding code, data, or resources.

Sources