CyberKit

Fileless Malware

Also called Memory-resident malware.

Malicious activity that runs in memory without a payload on disk.

What it is

Fileless malware operates primarily in memory and through trusted system tools and scripts, avoiding writing a traditional executable to disk. Its persistence and payload often live in places like the registry or scheduled scripts.

Why it matters

With little or no file to scan, it slips past file-based defenses and leaves scarce disk artifacts, pushing detection toward memory and behavior. Investigations lean heavily on RAM captures and command-line and script logging.

In practice

A backdoor that lives only in process memory, restarted each boot by an encoded script stored in a registry value.

What to look for

  • Script engines running encoded or downloaded code.
  • Registry values or WMI subscriptions holding payloads.
  • Executable memory not backed by files.

Common mistake

Thinking fileless means traceless. Logs, registry and memory still hold evidence.

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.

  • CrowdStrike Falcon Commercial

    An EDR agent that records process, file and network activity on each host and flags this kind of behavior.

  • Microsoft Defender for Endpoint Commercial

    Microsoft's EDR, with advanced hunting tables you can query for this activity across Windows, macOS and Linux.

  • Velociraptor Open source

    Collects and hunts for artifacts across many hosts at once, often during live response. Our notes.

  • Sysmon Free

    Free Windows logging of process starts, network connections and more, which many detections rely on. Our notes.

Read next

Sources