x64dbg
An open-source user mode debugger for Windows. Optimized for reverse engineering and malware analysis.
X64dbg: a Windows debugger for binaries without source
An open-source user mode debugger for Windows, built for malware analysis and reverse engineering binaries you don't have source for. The README covers installation, architecture choices, and the credits behind the tool.
What it targets
X64dbg describes itself as an open-source binary debugger for Windows aimed at malware analysis and reverse engineering of executables you do not have the source code for. There are many features available and a comprehensive plugin system to add your own, with more information on the project blog. It is a user mode debugger, which the GitHub description states explicitly.
Installation and the launcher
Installation is a download and extract. Grab a snapshot from GitHub or SourceForge and extract it somewhere your user has write access. Optionally, x96dbg.exe registers a shell extension and adds desktop shortcuts. From there you can run x32/x32dbg.exe for 32-bit executables or x64/x64dbg.exe for 64-bit ones, and if you are unsure, x96dbg.exe lets you pick the architecture.
A community effort
The README frames the project as a community effort that accepts pull requests, with a CONTRIBUTING document for details. Questions go to the contact channels or an issue, and a good first issues list is offered as an entry point for new contributors.
The credits tell the story
The credits section maps the pieces of the tool to other projects: the debugger core comes from TitanEngine Community Edition, disassembly from Zydis, assembly from XEDParse and asmjit, import reconstruction from Scylla, JSON from Jansson, and database compression from lz4, with icons and the website credited too. Special thanks go to Sigma for the initial GUI, the donators, everyone adding issues, and a long list of named contributors. A historical donors section records the BountySource period and notes that BountySource has since shut down, so those records are reconstructed by hand.
Editorial conclusion
The README leans on its credits section to show how much of the tool rides on other open source projects, which is a fair summary of how the project describes itself.
Community notes