RSPET (Reverse Shell and Post Exploitation Tool) is a Python based reverse shell equipped with functionalities that assist in a post exploitation scenario.

DISCLAIMER: This software is provided for educational purposes and as a proof of concept. The developer(s) do not endorse, incite or in any other way support unauthorised computer access and networks disruption.

NOTE: As of v0.0.3 folder min has been added. Since the new version has many more features not essential to the main functionality (a reverse shell that is), min will not recieve any more features beyond v0.0.3 and will only get bug and performance related fixes.

Current Version: v0.0.4

Follow: @TheRSPET on Twitter for updates.

• Remote Command Execution
• Trafic masking (XORed insted of cleartext); for better results use port 443[1]
• Built-in File/Binary transfer (both ways) over the masked trafic
• Built-in UDP Flooding tool
• Multiple/All Hosts management; order File/Binary transfer and UDP Flood from Multiple/All connected Hosts
• Modular Code Design to allow easy customization[3]
• Client script is tested and is compatible with PyInstaller (can be made into .exe)[2]

*[1]The idea for XORing as well as the skeleton for the client came from primalsecurity.net so if you like this pack of scripts you'll probably love what they do

*[2]Again check primalsecurity.net's perfect blogpost about producing an .exe

*[3]See EXPANDING for how you can easily add new functionality and customize RSPET to your needs

• RSPET_server.py or RSPET_server_min.py is situated at the attacker's machine and running to accept connections
• RSPET_client.py or RSPET_client_min.py is situated in the infected machine(s) and will initiate the connection and wait for input.

• Server:

python RSPET_server.py (max_connections) 

max_connections defaults to 5 if left blank

• Client:

python RSPET_client.py server_ip

Many changes can be made to fit individual needs.

As always if you have any suggestion, bug report or complain feel free to contact me.

• Fix logic bug where if a dirrect command to Host OS has no output Server displays command not recognised
• Fix logic bug where if a dirrect command's to Host OS execution is perpetual the Server deadlocks
• Add UDP Reflection functionality (already in the workings)

MIT