Dynamic Analysis
Also called Behavioral analysis, Runtime analysis.
Running a sample under observation to record what it actually does.
What it is
Executing malware in a controlled, instrumented environment and recording its file, registry, process, and network behavior. It captures activity that only appears at runtime, after any unpacking or decryption.
Why it matters
Dynamic analysis reveals real behavior that static review can miss (dropped files, persistence, and C2), which is why it is central to extracting indicators. Capable malware fights back with anti-analysis and sandbox-evasion checks.
In practice
Detonating a loader and watching it write a scheduled task and resolve a hard-coded command-and-control domain.
What to look for
- Processes started, files written and network connections made.
- Registry changes and persistence created.
- Behavior that changes with user input or time.
Common mistake
Trusting one sandbox run. Samples can detect sandboxes or wait out the analysis window.
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
- Static Analysis: Examining a sample's code and structure without executing it.
- Anti-VM: Checks that detect a virtual machine and suppress malicious behavior.
- C2 Configuration Extraction: Recovering a sample's embedded settings, like C2 and keys.