This repository contains documentation and source code of the C++, Python, and Rust APIs for the Binary Ninja reverse engineering platform.
Online documentation is available for the following APIs:
- C++ API, Stable Branch
- Python API, Stable Branch
- Python API, Dev Branch
- Rust API, Stable Branch
- Rust API, Dev Branch
This repository has two primary branches dev and master.
The dev branch has the latest updates and tracks the latest development build of Binary Ninja; pull requests should be made against this branch. The master branch tracks the stable build of Binary Ninja. If you have just installed Binary Ninja for the first time, you are likely on the stable release channel.
To write Binary Ninja plugins using C++, you'll need to build the C++ API. Building the API library is done similarly to most CMake-based projects; the basic steps are outlined as follows:
# Get the source
git clone https://github.com/Vector35/binaryninja-api.git
cd binaryninja-api
git submodule update --init --recursive
# Configure an out-of-source build setup
cmake -S . -B build # (additional arguments go here if needed)
# Compile
cmake --build build -j8In addition to the default build setup, you may want to:
- Build examples. To build the API examples, pass
-DBN_API_BUILD_EXAMPLES=ONto CMake when configuring the build. After the build succeeds, you can install the built plugins by running theinstalltarget. When using the "Unix Makefiles" build generator, this looks like:make install. - Build UI plugins. You will need Qt 6.4.1 (as of writing) installed to build UI plugins.
- Build headlessly. If you are using a headless Binary Ninja distribution or you do not wish to build UI plugins, pass
-DHEADLESS=ONto CMake when configuring the build.
- If Binary Ninja is installed at a different location than the platform default (defined in CMakeLists.txt), you will likely get an error stating "Binary Ninja Core Not Found." Specify the path to your Binary Ninja installation with by passing
-DBN_INSTALL_DIR=/path/to/binaryninjato CMake when configuring the build setup. - Since Binary Ninja is a 64-bit only product, ensure that you are using a 64-bit compiling and linking environment. Errors on Windows like
LNK1107might indicate that your bits don't match.
There are many examples available. The Python examples folder demonstrates many different applications of the Python API, while C++ examples include:
- bin-info is a standalone executable that prints some information about a given binary to the terminal.*
- breakpoint is a plugin that allows you to select a region within an x86 binary and use the context menu to fill it with breakpoint bytes.
- command-line disassm demonstrates how to dump disassembly to the command line.*
- llil-parser parses Low-Level IL, demonstrating how to match types and use a visitor class.*
- mlil-parser parses Medium-Level IL, demonstrating how to match types and use a visitor class.*
- print_syscalls is a standalone executable that prints the syscalls used in a given binary.*
- triage is a fully featured plugin that is shipped and enabled by default, demonstrating how to do a wide variety of tasks including extending the UI through QT.
- workflows is a collection of plugins that demonstrate using Workflows to extend the analysis pipeline.
- x86 extension creates an architecture extension which shows how to modify the behavior of the build-in architectures without creating a complete replacement.
* Requires license supporting headless API access.
The issue tracker for this repository tracks not only issues with the source code contained here but also the broader Binary Ninja product.
Public contributions are welcome to this repository. All the API and documentation in this repository is licensed under an MIT license, however, the API interfaces with a closed-source commercial application, Binary Ninja.
If you're interested in contributing when you submit your first PR, you'll receive a notice from CLA Assistant that allows you to sign our Contribution License Agreement online.
Some components may be released under compatible but slightly different open source licenses and will have their own LICENSE file as appropriate.