sickle-pdk
v4.0.0 open-sourceThe section your link pointed to isn't on sickle-pdk's page any more, so we've brought you to the top.
Payload development kit for shellcode generation, formatting, execution, disassembly, bad character identification, and diffing across multiple architectures.
sickle generate -p linux/aarch64/memfd_reflective_elf_tcp sickle -b"\x00\x0a\x0d"
Summary
sickle-pdk is an open-source payload development kit for shellcode work, run as a command-line tool, and free to use. It converts assembly to opcodes and back, formats shellcode for a target language, executes generated payloads for testing, identifies bad characters, and performs linear disassembly and diffing on binaries or stubs, with shellcode generation itself handled through the Keystone engine. It's aimed at exploit developers and red teamers who write or study shellcode across Windows, Linux and ARMARMA family of RISC processor architectures designed by Arm Holdings and licensed to chip makers worldwide; tools target it to run natively on mobile, embedded, and increasingly server and desktop hardware. targets, offering built-in stubs for reverse shells, egg-hunters, VirtualAlloc-based execution, reflective loaders and kernel-level techniques rather than requiring each to be hand-assembled. No comparable tool is named in its own material, but it sits in the payload-development corner of exploitation tooling. First committed in 2017, it has stayed active with 8 contributors, 92 commits and 16 releases in the past year, though the most recent release was over seven months ago.
Payload development kit for shellcode generation, formatting, execution, disassembly, bad character identification, and diffing across multiple architectures.
How sickle-pdk helps
Does this shellcode contain bytes that will break my exploit's input path?
scans the generated or supplied opcodes against a list of characters you specify in one pass and flags every offset where one occurs
What machine code does this assembly actually assemble to, and can I get back from bytes to instructions?
converts between assembly and opcodes in both directions, so a written stub can be turned into raw bytecode or a captured payload can be read back as instructions
Does this stub actually pop a shell before I burn it in an exploit chain?
wraps the raw shellcode in a minimal runner and executes it directly on Windows or Unix, skipping the manual compile-wrapper-compile-run cycle
What changed between these two versions of a shellcode stub?
diffs two stubs at the assembly level, the opcode level, or as raw hexdumps, and shows where the instructions or bytes diverge
What instructions are hiding in this raw binary blob?
performs linear disassembly over a raw binary file via Capstone and prints the recovered assembly, without relying on section headers or metadata
Do I have to hand-write a reverse shell or loader for this architecture, or is there a stub already?
ships built-in payloads for reverse shells, egg-hunters, VirtualAlloc-based execution, reflective PE/ELF loaders and kernel-level techniques across Windows, Linux and ARM targets, selectable instead of assembling one from scratch
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for sickle-pdk, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail sickle-pdk puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
6 entries
No entries match these filters.
- October 20251
- August 20251
- December 20241
- August 20241
- November 20191
- May 20191
Project health
Issue, contributor and maintainer activity in wetw0rk/sickle-pdk, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 −1 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 0 of 2 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 0
- Commits / month 0
- Stars 873
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.