Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
x64dbg is an open-source Windows debugger used to watch programs execute instruction by instruction, which makes it a standard tool for unpacking and analysing malware.

What Is x64dbg?
x64dbg is a debugger for Windows programs. You load an executable, set breakpoints, and step through its instructions while watching registers, memory, and the stack change. Where a disassembler shows you what the code says, a debugger shows you what it does, and for anything packed, obfuscated, or encrypted that difference decides whether analysis succeeds.
The project is open source under GPLv3, maintained by a community of contributors, and supports both 64-bit and 32-bit targets in one interface. It replaced OllyDbg as the default choice for most analysts, largely because OllyDbg never gained 64-bit support and stopped being updated.
The main window shows four panes: disassembly, registers, memory dump, and stack. Around them sit the features that make a session productive.
Two plugins are near-universal. Scylla reconstructs the import table of a dumped process and produces a working executable from it, which is what turns an unpacked memory image into something a disassembler can read. ScyllaHide conceals the debugger from the many checks a program can perform to detect one.
Most malware arrives packed. The file on disk contains a small loader and a compressed or encrypted blob; the real payload only exists once that loader has run. Static analysis of the file therefore shows almost nothing useful.
The debugger changes that. An analyst runs the sample under control, waits for the loader to decompress the payload into memory and transfer execution to it, pauses at that moment, and dumps the now-decoded code. From there, malware analysis proceeds normally: strings, imports, configuration, and network behaviour all become readable. This is also where command-and-control addresses and campaign identifiers are recovered, which is what feeds detection content and threat intelligence.
Malware authors expect to be debugged and build in countermeasures. The common ones are:
| Technique | How it works |
|---|---|
| API checks | Calling functions that report whether a debugger is attached |
| Process structure checks | Reading the flag the operating system sets in the process environment block |
| Timing checks | Measuring how long a short code sequence takes; stepping through it is far slower |
| Exception tricks | Raising exceptions that behave differently when a debugger handles them first |
| Breakpoint scanning | Searching its own code for the byte that software breakpoints write |
| Environment checks | Looking for analysis tool processes, virtual machine artefacts, and small disks or low memory |
ScyllaHide neutralises many of these automatically. The rest are handled by patching checks as they are found, which is itself a reliable way to locate the interesting code: a sample that works hard to avoid being watched is usually protecting something worth seeing.
Debugging malware means running it. Work in an isolated virtual machine with no route to production networks, take a snapshot before each run, and treat the host as untrusted afterwards if anything unexpected happens. Sandbox escapes exist, and some families specifically target analysis environments.
x64dbg rarely works alone. Analysts read structure and decompiled pseudocode in Ghidra or IDA Pro, use radare2 for scripted bulk work, and switch to the debugger when static reading stalls. Where the sample was captured from memory rather than disk, output from a memory forensics framework often provides the starting artefact.
On the defensive side, the same tools demonstrate how quickly a determined analyst reads secrets compiled into a desktop application, which is a useful counterargument whenever a development team proposes to protect something with obfuscation alone. Our Hardware Penetration Test Services apply this kind of analysis to firmware and embedded software.
Ghidra performs static analysis: it disassembles and decompiles a binary without running it, producing readable pseudocode. x64dbg is dynamic: it executes the program under control so you can watch what actually happens. Packed or obfuscated samples defeat static analysis until they are unpacked, which is exactly what a debugger is for, so analysts use both.
Only inside a properly isolated analysis environment. Debugging a sample means executing it, so use a virtual machine with no access to production networks or shared folders, snapshot before each run, and revert afterwards. Some malware detects virtual machines or attempts to escape them, so treat the analysis host as disposable and never use a working machine.
Through several checks: calling APIs that report debugger presence, reading the flag the operating system sets in its own process structure, timing short code sequences that run far slower when stepped, exploiting how exceptions are handled when a debugger is attached, and scanning its own code for the bytes that software breakpoints write.
Yes. The distribution includes both a 64-bit and a 32-bit engine, selected automatically according to the target, and the interface, shortcuts, and plugin ecosystem are the same for both. This was a significant practical advantage over older debuggers that handled only 32-bit targets and were never updated for modern Windows.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.