Sandbox Evasion
Also called Sandbox detection, Stalling code.
Tactics that detect or stall automated analysis to avoid detonation.
What it is
Behaviors malware uses to recognize an automated analysis environment (checking for short uptime, missing user activity, known artifacts, or long sleep timers), and to withhold its payload until conditions look like a real victim.
Why it matters
Evasion can turn an automated verdict falsely clean, so analysts must account for stalling and environment checks when a sample looks inert. It often forces a move to instrumented manual analysis to coax out behavior.
In practice
A dropper that waits for genuine mouse movement and a minimum uptime before unpacking, sleeping through a quick automated run.
What to look for
- Checks for VM artifacts, low RAM, few CPU cores or analysis tool processes.
- Long sleeps or waits for user input before anything malicious happens.
- Samples that behave benignly in a sandbox but differently on real hosts.
Common mistake
Calling a sample clean because the sandbox saw nothing. A quiet run can mean the sample noticed the sandbox.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- File Triage
Drop any file. It names the format from its first bytes, hashes it, and opens the parser that reads it: PE, ELF, Mach-O, Office, PDF, plist, or entropy and strings.
- Rule Range
Write a regex, a Sigma rule, a YARA rule and a query pipeline, each graded live against samples, some of which you never see.
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
- Anti-VM: Checks that detect a virtual machine and suppress malicious behavior.
- Anti-Debugging: Tricks malware uses to detect or resist analysis under a debugger.
- Dynamic Analysis: Running a sample under observation to record what it actually does.