examples

Some example scripts can be found in /extra/payloads/. You should
keep in mind that it is not possible to make some one-size-fits-all
payloads that will magically do exactly what you want, without you
ever touching the code or doing whatever preparations that are needed.
Everybody has their own personal preferences, local GUI and language
settings; your target machine may be substantially faster or slower
than the intended example machine, etc. Basically, you should not just
copy-paste examples, you should actually understand what you are doing.
All these example payloads only serve one purpose, which is to give
you an idea of how the device can be used. They are intentionally
made to be simple and generic. In any kind of real application, you
will have to build up your own payload, possibly reusing some of
the code or techniques that you have learned from example payloads.

Each example payload is placed in a dedicated directory, inside of which
all the relevant files are included, along with a readme.md documentation
file which is optional and only exists to explain what the payload does.
You may be able to simply copy all the contents inside of such directory
to the device and have it run the payload. Keep in mind, however, that
most of the example payloads expect a US keyboard layout and are intended
for a particular operating system. I recommend to always read the readme.md
file and also all of the in-script comments before using the examples.
The database of layout files is available in /extra/payloads/LayoutTest/kblayout/

Since the command language used by PocketAdmin is based on duckyscript,
you can also quite easily reuse payloads that were originally designed for
the USB rubber ducky, or some of the payloads for HAK5 bash bunny.
Though, you could also take some inspiration from payloads which are in a
substantially different format, such as scripts for arduino style badusb's;
if necessary, you can convert them to duckyscript without too much effort.
The exact same know-what-you-do precautions apply here; if somebody made a payload back in 2012 for windows7
does not necessarily mean that you can blindly copy-paste it and it will work.

---

Always keep in mind, that for everything to work you MUST have
all the right files in the right places! That means:

1. If you have any pre-configuration commands, you need to place them
   separately in a config.txt file in the device's root directory.

2. If fingerprinter was not enabled (default), you need to place
   your script file (payload.txt) in the device's root directory.

3. If fingerprinter was enabled, you need to place your script files
   (windows.txt, linux.txt, other.txt, etc) in /fgscript/ directory
   and also provide a database of .fgp files in /fingerdb/ directory.

4. If you want to replace the default US keyboard layout with some other
   one, you need to place required layout files in /kblayout/ directory.

5. If you want to use on-demand payloads, you need to place them inside
   /ondemand/ directory, with names from script03.txt up to script19.txt