View Issue Details

IDProjectCategoryView StatusLast Update
0004412Kali Linux[All Projects] Queued Tool Additionpublic2021-09-13 23:02
Reporterwetw0rk Assigned To 
Status acknowledgedResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0004412: Sickle - Shellcode development tool
DescriptionSickle is a shellcode development tool, created to speed up the various steps needed to create functioning shellcode. Aids the developer in eliminating bad characters, formatting output in various languages, executing shellcode in both Windows and Linux environments, comparing reversed shellcode to original, and disassembling shellcode into assembly language (ARM, x86, etc).
Steps To Reproducegit clone

cd Sickle/

apt-get install python3-pip

pip3 install capstone

chmod +x && cp /usr/bin/sickle

Additional InformationWritten in Python 3, and only dependency required to run is capstone (for disassembly).



2017-12-09 04:24

manager   ~0007674

is the version of capstone that we have in Kali not new enough for sickle?


2017-12-09 07:40

reporter   ~0007675

After checking you are correct, the version currently installed in Kali will work perfectly. I made a couple changes, and verified sickle worked properly on a fresh Kali 2017.3 install.


2017-12-11 07:45

reporter   ~0007680

Pushed some changes to the sickle. Thank you for your time.


2018-01-29 15:13

administrator   ~0008471

To help speed up the process of evaluating the tool, please make sure to include the following information (the more information you include, the more beneficial it will for us):

- [Name] - The name of the tool
- [Version] - What version of the tool should be added?
--- If it uses source control (such as git), please make sure there is a release to match (e.g. git tag)
- [Homepage] - Where can the tool be found online? Where to go to get more information?
- [Download] - Where to go to get the tool?
- [Author] - Who made the tool?
- [Licence] - How is the software distributed? What conditions does it come with?
- [Description] - What is the tool about? What does it do?
- [Dependencies] - What is needed for the tool to work?
- [Similar tools] - What other tools are out there?
- [How to install] - How do you compile it?
- [How to use] - What are some basic commands/functions to demonstrate it?


2018-01-29 18:10

reporter   ~0008548

Absolutely, if there’s any other information that would help let me know. Below is the
requested info:

-[Name] - Sickle

-[Version] - 1.4

-[Homepage] -

-[Download] -

-[Author] - Milton Valencia (wetw0rk)

-[License] - MIT License

-[Description] - Sickle is a shellcode development tool created to speed up the various steps
                    needed to create functioning shellcode. Sickle aids the developer in:
                    identification of bad characters, formatting in multiple languages (python,
                    perl, powershell, etc), executing shellcode in both Linux and Windows environments,
                    comparing reversed shellcode to original, and disassemble shellcode into various
                    architectures (ARM-THUMB, x86-32, x86-64, etc).

-[Dependencies] - capstone (If used within Kali the existing version of capstone works out of the
                    box. Otherwise it’s recommended to install via pip3 `pip3 install capstone`)

-[Similar tools] - msfvenom, ndisasm, shellnoob

-[How to install] - git clone
                    cd Sickle/ && chmod +x && cp /usr/bin/sickle
                    echo “Sickle installed!”

-[How to use] - Identification of instructions what result bad characters:
                        sickle -r shellcode -f python -v jumpcode -b "\x00" -c
                    Running shellcode (Sickle detects if Windows or Linux):
                        sickle -r shellcode -rs
                    Comparing shellcode:
                        sickle -r <my reverse shell> -e <original reverse shell>
                    Disassembly of shellcode (x86-64):
                        sickle -r reverse-shell -d -a x86 -m 64
                    Asciinema example:

I also went ahead and added screenshots.

example.png (357,345 bytes)


2018-01-29 23:05

reporter   ~0008557

I went ahead and added a git tag as well:



2018-02-12 00:26

reporter   ~0008654

@g0tmi1k I recently released v1.5 the git tag is here:

The only notable change is the compare function.



2018-02-12 00:28


compare.png (286,740 bytes)


2018-02-12 00:28


dissemble.png (413,406 bytes)


2018-05-22 01:51

reporter   ~0009169

Whenever a new change is made do we need to release a new tag?


2018-05-22 04:26

manager   ~0009170

Not for every change necessarily, but if you consider a new change worth a new release, then you should.

It depends on your idea of versioning.

If it's a bug change, you could do v1.5.1, if it's enough to be considered a new release, you could do v1.6. If it's massive changes, then possibly 2.0.


2018-05-23 01:14

reporter   ~0009171

Alright sweet in that case I went ahead and added a new release tag

Syntax, Running Shellcode in 64bit, and Comparing shellcode has changed. Running shellcode in 64bit is more reliable thanks to contributor luoyeah, and comparing shellcode has dramatically changed since 1.5 (ASM and Opcodes vs just opcodes). Examples below:

Identification of instructions what result bad characters:
  sickle -r shellcode -f python -v jumpcode -b "\x00" -c
Running shellcode (Sickle detects if Windows or Linux):
  sickle -r shellcode -rs
Comparing shellcode:
  sickle -r <my reverse shell> -e <original reverse shell>
Disassembly of shellcode (x86-64):
  sickle -r reverse-shell -a x86_64 -d
Asciinema example:


2019-05-22 03:11

reporter   ~0010603

v2 release ◝(⁰▿⁰)◜


2019-10-28 13:16

administrator   ~0011232

Last edited: 2020-01-06 13:21

View 2 revisions

@kali-team, please could this be packaged up.
@author, If you want to help the packaging process, you can check the documentation here ~


2019-11-25 08:02

reporter   ~0011344

Recently pushed v2.0.2 below is usage with the new module layout:

-[Name] - Sickle

-[Version] - 2.0.2

-[Homepage] -

-[Download] -

-[Author] - Milton Valencia (wetw0rk)

-[License] - MIT License

-[Description] - Sickle is a payload development tool originally created to aid in crafting shellcode, however it can be used in crafting payloads for other exploit types as well (non-binary). Although the current modules are mostly aimed towards assembly this tool is not limited to shellcode.

-[Dependencies] - capstone

-[Similar tools] - msfvenom, ndisasm, shellnoob

-[How to install] - git clone && cd Sickle/ && python3 install

-[How to use] -

  sickle -h
List Modules:
  sickle -l
Diff module:
  sickle -i -m diff # help (applys to all modules)
  sickle -r <bin1> -m diff BINFILE=<bin2> MODE=hexdump
  sickle -r <bin1> -m diff BINFILE=<bin2> MODE=byte
  sickle -r <bin1> -m diff BINFILE=<bin2> MODE=asm
  sickle -r <bin1> -m diff BINFILE=<bin2> MODE=raw
Format module (default module):
  sickle -i # list formats
  sickle -r <bin> -f <format>

Issue History

Date Modified Username Field Change
2017-12-06 06:14 wetw0rk New Issue
2017-12-09 04:24 steev Note Added: 0007674
2017-12-09 07:40 wetw0rk Note Added: 0007675
2017-12-11 07:45 wetw0rk Note Added: 0007680
2018-01-26 11:46 g0tmi1k Summary Shellcode development tool => Sickle - Shellcode development tool
2018-01-29 15:13 g0tmi1k Note Added: 0008471
2018-01-29 18:10 wetw0rk File Added: example.png
2018-01-29 18:10 wetw0rk Note Added: 0008548
2018-01-29 23:05 wetw0rk Note Added: 0008557
2018-02-12 00:26 wetw0rk Note Added: 0008654
2018-02-12 00:28 wetw0rk File Added: compare.png
2018-02-12 00:28 wetw0rk File Added: dissemble.png
2018-02-21 09:35 g0tmi1k Product Version 2017.3 =>
2018-05-22 01:51 wetw0rk Note Added: 0009169
2018-05-22 04:26 steev Note Added: 0009170
2018-05-23 01:14 wetw0rk Note Added: 0009171
2019-05-22 03:11 wetw0rk Note Added: 0010603
2019-10-28 13:16 g0tmi1k Note Added: 0011232
2019-10-28 13:16 g0tmi1k Category New Tool Requests => Queued Tool Addition
2019-10-28 16:01 g0tmi1k Status new => assigned
2019-11-25 08:02 wetw0rk Note Added: 0011344
2020-01-06 13:07 g0tmi1k Status assigned => acknowledged
2020-01-06 13:21 g0tmi1k Note Edited: 0011232 View Revisions
2020-06-17 14:57 g0tmi1k Severity feature => minor