Pupy is an opensource, cross-platform (Windows, Linux, OSX, Android) remote administration and post-exploitation tool mainly written in python

Pupy is a cross-platform, multi function RAT and post-exploitation tool mainly written in python. It features an all-in-memory execution guideline and leaves a very low footprint. Pupy can communicate using multiple transports, migrate into processes using reflective injection, and load remote python code, python packages and python C-extensions from memory. Windows payload can load the entire Python interpreter from memory using a reflective DLL.  Pupy does not touch the disk. Can be packed into a single .py file and run without any dependencies other than the python standard library on all OSes.  PyCrypto gets replaced by pure Python AES &amp; RSA implementations when unavailable. Reflectively migrate into other processes. Remotely import pure python packages (.py, .pyc) and compiled python C extensions (.pyd, .so) from memory.  Imported python modules do not touch the disk. Easily extensible, modules are simple to write and are sorted by os and category. Modules can directly access python objects on the remote client using rpyc. Access remote objects interactively from the pupy shell and get auto-completion of remote attributes. Communication transports are modular and stackable. Exfiltrate data using HTTP over HTTP over AES over XOR, or any combination of the available transports. Communicate using obfsproxy pluggable transports. Execute noninteractive commands on multiple hosts at once. Commands and scripts running on remote hosts are interruptible. Auto-completion for commands and arguments. Custom config can be defined: command aliases, modules. automatically run at connection, etc. Open interactive python shells with auto-completion on the all-in-memory remote python interpreter. Interactive shells (cmd.exe, /bin/bash, etc) can be opened remotely.  Remote shells on Unix &amp; Windows clients have a real tty with all keyboard signals working just like an SSH shell. Execute PE executable remotely and from memory. Generate payloads in various formats: Deploy in memory from a single command line using python or powershell one-liners. Embed "scriptlets" in generated payloads to perform some tasks "offline" without needing network connectivity (ex: start keylogger, add persistence, execute custom python script, check_vm, etc.) Multiple Target Platforms: 

Pupy is an opensource, multi-platform (Windows, Linux, OSX, Android), multi function RAT (Remote Administration Tool) mainly written in python. It features a all-in-memory execution guideline and leaves very low footprint. Pupy can communicate using various transports, migrate into processes (reflective injection), load remote python code, python packages and python C-extensions from memory.

Pupy is an opensource, multi-platform (Windows, Linux, OSX, Android), multi function RAT (Remote Administration Tool) and post-exploitation tool mainly written in python. It features a all-in-memory execution guideline and leaves very low footprint. Pupy can communicate using various transports, migrate into processes (reflective injection), load remote python code, python packages and python C-extensions from memory. Pupy modules can transparently access remote python objects using rpyc to perform various interactive tasks. Pupy can generate payloads in multiple formats like PE executables, reflective DLLs, pure python files, powershell, apk, ... When you package a payload, you can choose a launcher (connect, bind, ...), a transport (ssl, http, rsa, obfs3, scramblesuit, ...) and a number of "scriptlets". Scriptlets are python scripts meant to be embedded to perform various tasks offline (without requiring a session), like adding persistence, starting a keylogger, detecting a sandbox, ... On windows, the Pupy payload is compiled as a reflective DLL and the whole python interpreter is loaded from memory. Pupy does not touch the disk :) Pupy can reflectively migrate into other processes Pupy can remotely import, from memory, pure python packages (.py, .pyc) and compiled python C extensions (.pyd). The imported python modules do not touch the disk. (.pyd mem import currently work on Windows only, .so memory import is not implemented) Pupy is easily extensible, modules are quite simple to write, sorted by os and category. A lot of awesome modules are already implemented! Pupy uses rpyc and a module can directly access python objects on the remote client  We can also access remote objects interactively from the pupy shell and you even get auto-completion of remote attributes! Communication transports are modular, stackable and awesome. You could exfiltrate data using HTTP over HTTP over AES over XOR. Or any combination of the available transports ! Pupy can communicate using obfsproxy pluggable transports All the non interactive modules can be dispatched to multiple hosts in one command Multi-platform (tested on windows xp, 7, 8, 10, kali linux, ubuntu, osx, android) Commands and scripts running on remote hosts are interruptible Auto-completion for commands and arguments Nice colored output :-) Custom config can be defined: command aliases, modules automatically run at connection, ... Interactive python shells with auto-completion on the all in memory remote python interpreter can be opened Interactive shells (cmd.exe, /bin/bash, ...) can be opened remotely. Remote shells on Unix clients have a real tty with all keyboard signals working fine just like a ssh shell Pupy can execute PE exe remotely and from memory (cf. ex with mimikatz) Pupy can generate payloads in multiple formats : exe (x86, x64), dll(x86, x64), python, apk, ... Pupy can be deployed in memory, from a single command line using pupygen.py's python or powershell one-liners. "scriptlets" can be embeded in generated payloads to perform some tasks without needing network connectivity (ex: start keylogger, add persistence, execute custom python script, check_vm ...) tons of other features, check out the implemented modules 