Submit a Payload
Payloads for the respective Hak5 gear may be submit to either the payloads sub-forum on the Hak5 Forums or payload repository on the Hak5 Github listed below.
Payload authors are encouraged to follow the best practices and style-guide when submitting payloads.
Entries to the Hak5 Payload Awards must be made via pull-request to the respective github payload repository. If you're new to Github PR's — check out this Hak5 tutorial video.
Bash Bunny Payload Best Practices
- Give your payload a unique and descriptive name using
- or _ instead of spaces.
- Do not include binaries. If necessary, include a source link in the comments.
- Include a comment block with Author, Title and Description.
- Optionally include the Target, LED status and dependencies.
- Configurable options should be variables at the top of the payload.
- Use standard LED like
LED SETUP, LED ATTACK and LED FINISH.
- Comment each stage of the payload.
See the full
Bash Bunny readme for more details.
Key Croc Payload Best Practices
- Give your payload a descriptive name beginning with target OS (e.g. WIN_, MAC_, LINUX_ or MULTI_).
- Include a comment block with Author, Title and Description.
- Optionally include the Target, LED status and dependencies.
- Configurable options should be variables at the top of the payload.
- Use standard LED like
LED SETUP, LED ATTACK and LED FINISH.
- Comment each stage of the payload.
See the full
Key Croc readme for more details.
Packet Squirrel Payload Best Practices
- Give your payload a unique and descriptive name using
- or _ instead of spaces.
- Include a comment block with Author, Title and Description.
- Optionally include the Target, LED status and dependencies.
- Configurable options should be variables at the top of the payload.
- Use standard LED like
LED SETUP, LED ATTACK and LED FINISH.
- Comment each stage of the payload.
See the full
Packet Squirrel readme for more details.
Shark Jack Payload Best Practices
- Give your payload a unique and descriptive name using
- or _ instead of spaces.
- Include a comment block with Author, Title and Description.
- Optionally include the Target, LED status and dependencies.
- Configurable options should be variables at the top of the payload.
- Use standard LED like
LED SETUP, LED ATTACK and LED FINISH.
- Comment each stage of the payload.
See the full
Shark Jack readme for more details.
USB Rubber Ducky Payload Best Practices
- Give your payload a unique and descriptive name using
- or _ instead of spaces.
- Include a
REM comment block with Author, Title, Target and Description.
- Comment each stage of the payload.
See the full
USB Rubber Ducky readme for more details.
O.MG Cable Payload Best Practices
- Give your payload a unique and descriptive name using
- or _ instead of spaces.
- Include a
REM comment block with Author, Title, Target and Description.
- Comment each stage of the payload.
See the full
O.MG Cable readme for more details.
Download Payloads
Get Rewarded
Enter now to get your payload in front of thousands. Win over $2,000 in Hak5 prizes, enter the payload leaderboard and Hak5 Payload Award Book. You may have been rewarded already!
Learn more about the Hak5 Payload Awards.
Get Inspired & Collaborate
The Hak5 forums and our Discord are a great place to get inspired, showcase your work and receive helpful feedback on your payloads. Some even opt to submit and support their payloads within each devices respective payload sub-forum — a practice we fully support!
Join the Hak5 Community today!
