Dynamic Malware Analysis Checklist: Safe Lab Setup, Tools and Steps

Dynamic malware analysis means running a suspicious file inside an isolated lab and recording what it does, so defenders can write detections and respond.

Jun 23, 2025 - 10:51
Updated: 
108.5k

Incident Response & Digital Forensics in Cybersecurity & Ethical Hacking · Lab / project

Cyber Threats, Scams & Online Safety

Dynamic Malware Analysis Checklist: Safe Lab Setup, Tools and Steps

Quick answer: Dynamic malware analysis means running a suspicious file inside an isolated lab and recording what it does, so defenders can write detections and respond. A safe checklist is: get written authorisation, build an isolated virtual machine with no route to your real network, take a clean snapshot, start monitoring (Process Monitor, Process Explorer, Sysmon and a packet capture), run the sample, record processes, files, registry, network and persistence, then revert the snapshot and write up indicators mapped to MITRE ATT&CK. Automated sandboxes such as CAPE speed up triage. Never run unknown files on a work or personal machine.

Key takeaways

  • Isolation comes first; analysis comes second.
  • Snapshots let you reset to clean in seconds.
  • Sysinternals tools cover processes, files and registry.
  • Automated sandboxes triage, humans confirm.
  • The output is detections and indicators, not curiosity.

Table of Contents

Why Use Dynamic Analysis?

Static analysis reads a file without running it, but packed or obfuscated code hides its intent. Running it in a controlled lab shows the real behaviour: what it drops, what it changes and where it connects. NIST SP 800-83 treats this kind of analysis as part of malware incident handling, feeding containment and eradication.

How Do You Build a Safe Lab?

  • Authorisation: written approval and a policy on who may handle samples.
  • Dedicated host: a separate machine, not your daily laptop.
  • Host-only or isolated network: no bridge to the corporate LAN; use a simulated internet service if needed.
  • No shared folders or clipboard between guest and host.
  • Clean snapshot before every run.
  • Safe transfer: keep samples in password-protected archives and never open them outside the lab.

For quick, low-risk checks of a file you are unsure about, Windows Sandbox gives a disposable desktop, but it is not a full analysis lab. The sandbox environment explainer covers isolation concepts.

Which Defensive Tools Do You Need?

ToolWhat it records
Process MonitorFile, registry and process activity in real time
Process ExplorerProcess tree, loaded DLLs, signatures
SysmonPersistent event logs for process creation, network and more
WiresharkNetwork traffic, DNS and connection attempts
AutorunsPersistence locations before and after
CAPE SandboxAutomated run, behaviour report and payload extraction

Inside the guest only, Sysmon is installed with a configuration file, for example:

sysmon64.exe -accepteula -i sysmonconfig.xml

What Is the Step-by-Step Checklist?

  1. Record the file hash and source in your case notes.
  2. Revert the VM to the clean snapshot and confirm isolation.
  3. Start Procmon, Process Explorer, Sysmon and the packet capture.
  4. Take an Autoruns baseline.
  5. Run the sample and observe for a fixed period.
  6. Save logs, capture and a memory image if needed (NIST SP 800-86 covers evidence handling).
  7. Compare persistence with the baseline.
  8. Export results off the VM safely, then revert the snapshot.

What Are the Limits of Dynamic Analysis?

Some malware checks for virtual machines, debuggers or missing internet access and stays dormant. Others wait for a date, a user click or a specific language setting. A quiet run does not prove a file is safe. Combine dynamic results with static review, reputation data and endpoint telemetry from real systems.

How Do You Turn Findings Into Defences?

Map each behaviour to a MITRE ATT&CK technique, then list hashes, domains, IPs, file paths and registry keys. Turn behaviours into SIEM or EDR rules, block indicators, and hunt for them across the estate. For tooling that automates triage at scale, see automated malware analysis tools. Handling samples without authorisation can breach Sections 43 and 66 of India's IT Act 2000. WebAsha offers malware analysis training.

References

Frequently Asked Questions

It is running a suspicious file in an isolated lab and recording its behaviour, such as processes, file changes, registry edits and network connections.

Static analysis examines the file without running it, while dynamic analysis observes what it actually does when executed in a controlled environment.

No. Use a dedicated, isolated lab machine with snapshots, because malware can escape weak setups and damage personal or work data.

Sysinternals Process Monitor, Process Explorer, Autoruns and Sysmon, plus Wireshark and the open-source CAPE sandbox, cover most needs.

It is useful for a quick disposable test, but it lacks the monitoring, isolation controls and repeatability of a proper analysis lab.

Many samples detect virtual machines or wait for triggers, so a quiet run does not prove a file is harmless and needs further review.

Hashes, behaviours mapped to MITRE ATT&CK, network and host indicators, persistence methods and recommended detections and blocks.

Yes. Work only under written authorisation and organisational policy, since misuse can breach Sections 43 and 66 of India’s IT Act 2000.

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Wow Wow 0
Sad Sad 0
Angry Angry 0
Vaishnavi

Vaishnavi is a skilled tech professional at the Ethical Hacking Training Institute in Pune, responsible for managing and optimizing the technical infrastructure that supports advanced cybersecurity education. With deep expertise in network security, backend operations, and system performance, she ensures that practical labs, online modules, and assessments run smoothly and securely. Her behind-the-scenes contributions play a vital role in delivering a seamless and secure learning experience for aspiring ethical hackers.