hak5
/
usbrubberducky-payloads
mirror of https://github.com/hak5/usbrubberducky-payloads.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
The Official USB Rubber Ducky Payload Repository
67 Commits
4 Branches
0 Tags
70 MiB
PowerShell 75.8%
Java 11.1%
Python 5.5%
Shell 3.1%
JavaScript 2%
Other 2.5%
 
 
 
 
 
 
Go to file
cribb-it 2ba0b3e08c Small Fixes 2022-08-26 18:32:02 +01:00
payloads/library Small Fixes 2022-08-26 18:32:02 +01:00
.gitignore misc: Remove .DS_Stores, add to git ignore 2021-09-30 15:20:46 +01:00
README.md Update README.md 2021-09-09 16:46:28 -05:00

README.md

Payload Library for the USB Rubber Ducky by Hak5

This repository contains payloads and extensions for the Hak5 USB Rubber Ducky. Community developed payloads are listed and developers are encouraged to create pull requests to make changes to or submit new payloads.

About the USB Rubber Ducky

A "flash drive" that types keystroke injection payloads into unsuspecting computers at incredible speeds.

USB Rubber Ducky

Disclaimer

Generally, payloads may execute commands on your device. As such, it is possible for a payload to damage your device. Payloads from this repository are provided AS-IS without warranty. While Hak5 makes a best effort to review payloads, there are no guarantees as to their effectiveness. As with any script, you are advised to proceed with caution.

Legal

Payloads from this repository are provided for educational purposes only. Hak5 gear is intended for authorized auditing and security analysis purposes only where permitted subject to local and international laws where applicable. Users are solely responsible for compliance with all laws of their locality. Hak5 LLC and affiliates claim no responsibility for unauthorized or unlawful use.

Contributing

Once you have developed your payload, you are encouraged to contribute to this repository by submitting a Pull Request. Reviewed and Approved pull requests will add your payload to this repository, where they may be publically available.

Please adhere to the following best practices and style guide when submitting a payload.

Naming Conventions

Please give your payload a unique and descriptive name. Do not use spaces in payload names. Each payload should be submit into its own directory, with - or _ used in place of spaces, to one of the categories such as exfiltration, phishing, remote_access or recon. Do not create your own category.

Comments

Payloads should begin with REM comments specifying the title of the payload, the author, the target, and a brief description.

REM Title: Canary Duck
REM Author: Jessie Crimson Hart
REM Description: Opens hidden powershell and connects to canary webserver using Invoke-WebRequest alerting you to spies and snoops.
REM Target: Windows 10 (Powershell)
REM Props: Hak5, Thinkst
REM Version: 1.0
REM Category: General