A curated collection of BadUSB / HID-injection payload scripts organised by operating system and functionality.
Payloads are written in DuckyScript format (compatible with USB Rubber Ducky, Flipper Zero Bad-USB, Bash Bunny, and similar tools).
⚠️ For educational and authorised penetration-testing purposes only.
Never deploy these payloads on systems you do not own or have explicit written permission to test.
{os}/{functionality}/
<payload>.txt – DuckyScript payload
manifest.txt – lists every file in this folder (fullpath | filename)
manifest.txt – root map of all {os}/{functionality} folders
| Folder | Description |
|---|---|
windows |
Windows 10 / 11 targets |
linux |
Linux targets (Ubuntu, Debian, Fedora, Kali) |
macos |
macOS 12+ targets (Monterey, Ventura, Sonoma) |
| Folder | Description |
|---|---|
recon |
System information, user enumeration, network recon |
persistence |
Registry run keys, startup folders, scheduled tasks, cron, LaunchAgents, SSH keys |
exfiltration |
WiFi credentials, clipboard, browser history, SSH keys, Keychain |
reverse_shell |
TCP reverse shells (PowerShell, Bash, Python, Netcat) |
credentials |
SAM/SYSTEM hive dump, Credential Manager (Windows only) |
Maps each {os}/{functionality} directory to a one-line description:
windows/recon | Windows system & network reconnaissance scripts
windows/persistence | Windows persistence mechanisms (registry, startup, scheduled tasks)
...
Each {os}/{functionality}/manifest.txt lists all payload files in that directory:
# Format: fullpath | filename
windows/recon/windows_sysinfo.txt | windows_sysinfo.txt
...
- Follow the existing folder naming convention:
{os}/{functionality}/. - Name payload files descriptively:
{os}_{description}.txt. - Begin every payload with
REMheader comments (Title, Author, Version, Target, Description). - After adding new files, regenerate the relevant
manifest.txtfiles.