Bitzu

312-50 ยท Malware threats

Fileless malware and living off the land

In-memory execution, PowerShell, WMI, LOLBins, why signature scanning misses it, and behavioural detection.

Key points

  • Fileless malware runs mainly in memory or through built-in tools, with no new executable on disk.
  • Living off the land: abusing trusted OS components such as PowerShell, WMI, LOLBins.
  • LOLBins: legitimate signed binaries, scripts, libraries.
  • File-hash and signature scanning has little to inspect.
  • Detect by behaviour: script block logging, unusual parent-child process chains, WMI persistence, EDR memory scanning.

Practice questions

Single choice

Why does traditional signature-based antivirus often miss fileless attacks?

  1. There is little or no malicious file on disk to match, and the tools used are legitimate
  2. Fileless attacks always use encrypted network traffic
  3. Signatures only work when the computer is offline
  4. Fileless attacks run only on firmware
Show answer

Answer: A. There is little or no malicious file on disk to match, and the tools used are legitimate

There is often no new malicious file to hash or match, and the tools abused are legitimate. The attack is not encrypted traffic by nature, and signatures do not need internet access.

Select all that apply

Which are legitimate Windows components commonly abused in living-off-the-land attacks?

  1. PowerShell
  2. Windows Management Instrumentation (WMI)
  3. certutil.exe
  4. A third-party game launcher
  5. An image editing suite
Show answer

Answer: A. PowerShell, B. Windows Management Instrumentation (WMI), C. certutil.exe

PowerShell, WMI and certutil are built-in and frequently abused. Photoshop and a third-party game launcher are not built-in OS components.

True or false

Because fileless malware lives only in memory, it always disappears and leaves no evidence once the system is rebooted.

Show answer

Answer: False

False. Many fileless attacks add persistence through the registry, scheduled tasks or WMI subscriptions that re-launch the in-memory payload after reboot, and logs often keep traces.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More 312-50 topics in this module