Extensions

Extensions which augment DuckyScript with new commands and functions. For each payload.txt run, extensions are sourced automatically. Calling the function names of any extension will produce the desired result. Extensions reside in the payload library on the USB mass storage partition from /payloads/library/extensions.
EXAMPLE EXTENSIONS
This table is provides a non-exhaustive list of basic usage for some extensions. Additional extension documentation can be found from the comments within each individual extension script file in /payload/library/extensions.
COMMAND
Description
Example
RUN
Keystroke injection shortcut for mutli-OS command execution.
RUN WIN notepad.exe
 
 
RUN OSX terminal
 
 
RUN UNITY xterm
GET
Exports system variables
GET TARGET_IP # exports $TARGET_IP
 
 
GET TARGET_HOSTNAME # exports $TARGET_HOSTNAME
 
 
GET HOST_IP # exports $HOST_IP
 
 
GET SWITCH_POSITION # exports $SWITCH_POSITION
REQUIRETOOL
Exits payload with LED FAIL state if the specified tool is not found in /tools
REQUIRETOOL impacket
DUCKY_LANG
Accepts two letter country code to set the HID injection language for subsequent ducky script / QUACK commands
DUCKY_LANG us
Extensions replaced bunny_helpers.sh from Bash Bunny firmware version 1.1 onwards.
Extensions come pre-installed on the Bash Bunny Mark II

COMMAND	Description	Example
`RUN`	Keystroke injection shortcut for mutli-OS command execution.	`RUN WIN notepad.exe`
		`RUN OSX terminal`
		`RUN UNITY xterm`
`GET`	Exports system variables	`GET TARGET_IP # exports $TARGET_IP`
		`GET TARGET_HOSTNAME # exports $TARGET_HOSTNAME`
		`GET HOST_IP # exports $HOST_IP`
		`GET SWITCH_POSITION # exports $SWITCH_POSITION`
`REQUIRETOOL`	Exits payload with LED FAIL state if the specified tool is not found in /tools	`REQUIRETOOL impacket`
`DUCKY_LANG`	Accepts two letter country code to set the HID injection language for subsequent ducky script / QUACK commands	`DUCKY_LANG us`

Last modified 1yr ago