Contribute
Submit a Payload to be featured & rewarded.
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.
Get Rewarded
Get your payload in front of thousands and enter to win over $2,000 in prizes in the Hak5 Payload Awards.
Collaborate
Get inspired, showcase your work and receive helpful feedback on your payloads in the Hak5 Community!
