Loading...
Malware analysis tools tell you what a suspicious file actually does before it does it to you. They fall into a few camps: sandboxes that detonate a sample in an isolated environment and record its behavior, disassemblers and debuggers that let analysts reverse-engineer binaries instruction by instruction, unpackers and deobfuscators that strip away the layers attackers use to hide intent, and classification engines that match samples to known families and threat actors. This is core SecOps tooling for incident responders, threat hunters, and reverse engineers who need to triage alerts, confirm a detection, extract indicators of compromise, and understand campaigns rather than just block hashes.
We cover 167 Malware Analysis tools, 118 free and 49 commercial.
Accuracy and depth improve over time. Last reviewed Sep 2026. Is something off? Reach out.
New to this category? What is Malware Analysis?
A collection of Android Fakebank and Tizi samples for analyzing spyware on Android devices.
A collection of setup scripts for various security research tools with installers for tools like afl, angr, barf, and more.
An open-source binary debugger for Windows with a comprehensive plugin system for malware analysis and reverse engineering.
steg86 is a steganographic tool that hides information within x86 and AMD64 binary executables without affecting their performance or file size.
Binary analysis and management framework for organizing malware and exploit samples.
Emulates browser functionality to detect exploits targeting browser vulnerabilities.
Compact C framework for analyzing suspected malware documents and detecting exploits and embedded executables.
Repository of scripts, signatures, and IOCs related to various malware analysis topics.
Strelka is a real-time, container-based file scanning system that performs file extraction and metadata collection at enterprise scale for threat hunting, detection, and incident response.
DECAF++ is a fast whole-system dynamic taint analysis framework with improved performance and elasticity.
A collection of Python scripts that automate tasks and extend IDA Pro disassembler functionality for reverse engineering workflows.
Open Source Intelligence solution for threat intelligence data enrichment and quick analysis of suspicious files or malware.
Android Loadable Kernel Modules for reversing and debugging on controlled systems/emulators.
An Emacs major mode that provides syntax highlighting and enhanced readability for smali code files used in Android malware analysis.
A modified version of Cuckoo Sandbox with enhanced features and capabilities.
BARF is an open source binary analysis framework for supporting various binary code analysis tasks in information security.
DroidBox is a dynamic analysis framework for Android applications that monitors runtime behavior, network activity, file operations, and security events while generating behavioral visualizations.
Interactive incremental disassembler with data/control flow analysis capabilities.
CapTipper is a python tool to analyze, explore, and revive HTTP malicious traffic.
Binkit is a binary analysis tool that merged with DarunGrim and incorporates its analysis algorithms, currently in internal testing before official release.
A script to assist in creating templates for VirtualBox to enhance VM detection evasion.
Drltrace is a dynamic API calls tracer for Windows and Linux applications.
Common questions about Malware Analysis tools, selection guides, pricing, and comparisons.
A malware analysis tool helps security teams understand what a suspicious or malicious file does. Some run the sample in an isolated sandbox and record its behavior, network calls, and file changes. Others let analysts reverse-engineer the binary directly through disassembly and debugging. The aim is to confirm whether something is malicious, extract indicators of compromise, and understand the actor behind it.
Static analysis examines a file without running it, using disassemblers, decompilers, and unpackers to read the code and structure. Dynamic analysis detonates the sample in a controlled sandbox and watches what it does: processes spawned, registry changes, network connections. Static is safer and catches dormant code paths; dynamic reveals real runtime behavior. Serious investigations use both, since each covers the other's blind spots.
Start with what you analyze most and on which platforms, then decide between sandboxing, reverse engineering, or both. Check anti-evasion capabilities, since modern malware detects analysis environments. Confirm the output gives you usable IOCs, ATT&CK mapping, and clean exports to your SIEM or threat intel platform. If samples are sensitive, prioritize on-prem or air-gapped detonation over public cloud upload.
Free and open-source tools cover an enormous amount of ground, and many reverse engineers rely on them daily for disassembly, debugging, and unpacking. Commercial platforms tend to add managed sandbox infrastructure, automated family attribution, threat actor context, and integrations that save analyst time at scale. A common pattern is open tooling for deep manual work, paid services for fast automated triage and enrichment.
A sandbox is one technique within malware analysis, focused on detonating samples and observing behavior. Malware analysis is broader, adding static reverse engineering, unpacking, and classification on top of sandboxing. EDR detects and responds to threats on live endpoints in production. Malware analysis tools are where you take a captured sample apart to understand it, often after EDR or a sandbox first flagged it.