Skip to content

lshaf/badusb-collection

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

9 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

badusb-collection

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.


Repository Structure

{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

Operating Systems

Folder Description
windows Windows 10 / 11 targets
linux Linux targets (Ubuntu, Debian, Fedora, Kali)
macos macOS 12+ targets (Monterey, Ventura, Sonoma)

Functionality Categories

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)

Manifest Files

Root manifest.txt

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)
...

Per-folder manifest.txt

Each {os}/{functionality}/manifest.txt lists all payload files in that directory:

# Format: fullpath | filename
windows/recon/windows_sysinfo.txt | windows_sysinfo.txt
...

Contributing

  1. Follow the existing folder naming convention: {os}/{functionality}/.
  2. Name payload files descriptively: {os}_{description}.txt.
  3. Begin every payload with REM header comments (Title, Author, Version, Target, Description).
  4. After adding new files, regenerate the relevant manifest.txt files.

Thanks To

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors