CyberKit

Loader

Code that prepares and executes a payload, often only in memory.

What it is

A loader is malware whose role is to set up and launch a payload (decrypting it, mapping it into memory, and transferring control) frequently without writing the final stage to disk. It bridges delivery and execution.

Why it matters

Loaders are commodity infrastructure shared across many families, so identifying the loader and the payload it runs are separate, valuable findings. Their in-memory execution makes them a focus of fileless-attack analysis.

In practice

A loader that decrypts a backdoor and reflectively maps it into a running process, leaving no payload file on disk.

What to look for

  • Payloads decrypted and run in memory.
  • Connections to fetch additional modules.
  • Common loader families reused across many campaigns.

Common mistake

Treating the loader as the end goal. It exists to deliver something else.

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

  • Dropper: Malware that carries and deposits an embedded payload on the host.
  • Stager: A tiny first stage that pulls and runs a larger second stage.
  • Reflective DLL Loading: Loading a DLL from memory while bypassing the OS loader and its lists.

Sources