Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
radare2 is an open-source reverse engineering framework that disassembles, debugs, patches, and compares binaries from the command line across dozens of processor architectures.

What Is radare2?
radare2 is a reverse engineering framework: a set of tools for taking a compiled binary apart when you have no source code. It disassembles instructions, reconstructs functions and control flow, inspects and edits raw bytes, attaches a debugger to a running process, compares two builds, and scripts all of it. Everything happens in a terse command-line interface that is either the tool’s greatest strength or the reason people give up on it in the first hour.
The project started in 2006 as a small hex editor for forensic work and grew into a framework supporting dozens of processor architectures and file formats, from ordinary Windows executables to firmware images and bare-metal dumps. It is free software, which is why it turns up in academic work, capture-the-flag competitions, and embedded security research where commercial licences are impractical.
radare2 commands are short because they are meant to be typed constantly. Most are a single letter with modifiers, and the pattern becomes predictable quickly.
| Command | Meaning |
|---|---|
aaa | Run the standard analysis passes over the whole binary |
afl | List the functions that analysis found |
pdf | Print the disassembly of the current function |
s | Seek to an address or symbol |
iz | List strings in the data sections |
V and VV | Visual mode and the interactive call graph |
Commands compose. Appending ~ filters output like grep, and a trailing j returns JSON, which is what makes the framework attractive for automation. The r2pipe bindings let a Python or Go script drive an analysis session and consume those JSON results, so bulk triage of a malware corpus becomes a script rather than a week of clicking.
Several standalone binaries ship alongside the main shell and are often more convenient for one-off questions. rabin2 prints headers, imports, exports, and sections. radiff2 compares two binaries, which is the standard way to work out what a vendor changed in a security patch. rafind2 searches for byte patterns, rahash2 computes hashes over regions of a file, and rax2 converts between numeric representations.
For analysts who prefer a graphical interface, Cutter provides one. It was originally built on radare2 and now sits on top of Rizin, a fork created in 2020, so the two ecosystems have diverged somewhat while sharing a common ancestry and much of the same command vocabulary.
The most common context is malware analysis. An analyst examines strings and imports for a quick impression, identifies the unpacking routine, follows the code that resolves API addresses at runtime, and extracts configuration such as command-and-control addresses. Because radare2 reads raw memory dumps as happily as files, it pairs naturally with memory forensics output.
Vulnerability research is the second context. Comparing the patched and unpatched versions of a library narrows the search for the fixed bug to a handful of functions, which is how public proof-of-concept exploits often appear within days of a vendor update. Firmware work is the third: router, IoT, and industrial device images frequently use architectures that commercial decompilers support poorly, and radare2’s breadth of architecture support is a genuine advantage there.
Ghidra, released by the NSA in 2019, offers a strong decompiler and a graphical interface at no cost, and it has become the default teaching tool. IDA Pro remains the commercial standard with the most mature decompiler. radare2 wins on scriptability, on obscure architectures, on being small enough to run on a constrained analysis box, and on being modifiable. Many practitioners use two of the three, reading decompiled pseudocode in one and doing byte-level and automation work in the other.
Reverse engineering is how detections get written. Analysing a sample produces the behavioural indicators, network patterns, and YARA rules that a detection team deploys, and it is how an incident responder establishes what a piece of malware actually did to a victim rather than what a vendor report claims. On the development side, the same tools show how little effort it takes to read secrets compiled into a mobile or desktop application, which is a useful corrective for teams who assume that obfuscation equals protection.
Our Hardware Penetration Test Services include firmware extraction and binary analysis of embedded devices using exactly this class of tooling.
Generally yes, at the beginning. Ghidra presents a graphical interface and a decompiler that produces readable pseudocode, so newcomers see useful output immediately. radare2 expects you to learn its command vocabulary first. Analysts who make that investment usually find it faster for repetitive work and far easier to script, which is why many use both.
Not natively in the way IDA Pro and Ghidra do, but plugins provide one. The r2dec and r2ghidra extensions add pseudocode output, with r2ghidra reusing the Ghidra decompiler engine inside the radare2 shell. Many analysts run radare2 for navigation, patching, and scripting while reading decompiled output from a separate tool.
Yes. It includes a debugger that can start a process or attach to an existing one, set software and hardware breakpoints, step through instructions, inspect and modify registers and memory, and handle signals. On Windows, analysts often prefer x64dbg for its interface, but radare2’s debugger is useful when the same scripts need to run on Linux targets.
Owning and running the tool is lawful. What you analyse is the question. UK copyright law permits decompilation in limited circumstances, mainly for interoperability, and many licence agreements prohibit reverse engineering outright. Malware analysis and work on your own software are uncontroversial; analysing a third party’s licensed product should be checked with legal advice first.
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.