Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time
December 14, 2021 14:26
December 14, 2021 14:26
December 14, 2021 14:26

Uroboros: Infrastructure for Reassembleable Disassembling and Transformation (Version 0.5)



Uroboros is available as a docker image, you can check the details in Docker


Before build Uroboros, you need to run the following command:

$ sudo apt-get install -y -q autoconf automake debianutils m4 build-essential python

Also, you need to obtain the OCaml compiler and libraries:

$ sudo apt-get install opam
$ opam init
$ opam switch create 4.01.0
$ opam install -y deriving.0.7 ocamlfind.1.5.5 parmap.1.0-rc6 batteries.2.3.1
$ eval $(opam env)

To build Uroboros, run the command below.

$ git clone /uroboros
$ cd /uroboros/src
$ ./build



Uroboros can take 64-bit and 32-bit ELF executable binaries as the input. To use Uroboros for disassembling:

$ python bzip

The disassembled output can be found at current dicrectory, named final.s. Uroboros will also assemble it back into an executable, a.out.

Python script provides multiple options to manipulate the disassembling process.

  1. -i (iteration):

    The disassemble-reassemble process can be iterated for multiple times. For example.

    $ python bzip -i 50
  2. -k (keep):

    This option will create a folder to store the assembly code and binary generated from each iteration. This is only effective together with -i.

    $ python bzip -i 50 -k

    A subfolder will be created in ./src folder, with input binary name and timestamp. For example: test_fold_bzip_2021-09-19_05:51:00

  3. -a (assumption):

    This option configures the three symbolization assumptions proposed in the original Uroboros paper [1]. Note that in the current version, the first assumption (n-byte alignment) are set by default. The other two assumptions can be set by users.

    Assumption two:

    $ python bzip -a 2

    Note that by accepting this assumption, we need to put data sections (.data, .rodata and .bss) to its original starting addresses. Linker scripts can be used during reassembling. For exmaple:

    $ gcc -Tld_gobmk.sty final.s

    Users may write their own linker script, some examples are given at ./src/ld_script folder.

    Assumption three:

    $ python bzip -a 3

    This assumption requires to know the function starting addresses. To obtain this information, Uroboros can take unstripped binaries as input. The function starting address information is obtained from the input, which is then stripped before disassembling.

    These assumptions can be used together.

    $ python bzip -a 3 -a 2

Instrument binaries

Instrumentation tools process the internal data structure of Uroboros. Some examples are shown in the plugins folder. You may start with, which instruments every memory write operation.

To register instrumentation code:

$ cp plugins/
$ ./build


@inproceedings {190920,
author = {Shuai Wang and Pei Wang and Dinghao Wu},
title = {Reassembleable Disassembling},
booktitle = {24th {USENIX} Security Symposium ({USENIX} Security 15)},
year = {2015},
isbn = {978-1-939133-11-3},
address = {Washington, D.C.},
pages = {627--642},
url = {},
publisher = {{USENIX} Association},
month = aug,