Anti-Debugging
Also called Debugger detection.
Tricks malware uses to detect or resist analysis under a debugger.
What it is
A set of techniques by which a program detects whether it is being debugged (checking flags, timing, or breakpoints), and alters its behavior, crashes, or hides functionality in response. The aim is to frustrate interactive analysis.
Why it matters
These checks slow reverse engineering and can mask malicious paths entirely, so analysts must recognize and neutralize them. Their very presence flags a sample as deliberately evasive and worth deeper attention.
In practice
A sample that quietly exits the moment it sees a debugger flag set, hiding its payload from a casual analyst.
What to look for
- Calls to IsDebuggerPresent or checks of the PEB BeingDebugged flag.
- Timing checks that measure how long code takes.
- Exceptions used to detect breakpoints.
Common mistake
Giving up when a sample crashes in a debugger. Patch or hide from the checks and continue.
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
- Debugging: Controlling a running sample step by step to watch its state.
- Anti-VM: Checks that detect a virtual machine and suppress malicious behavior.
- Sandbox Evasion: Tactics that detect or stall automated analysis to avoid detonation.