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

[enhancement] Implicitly set rhost value for stargers #155

Open
ajkerley628 opened this issue Jul 10, 2020 · 1 comment
Open

[enhancement] Implicitly set rhost value for stargers #155

ajkerley628 opened this issue Jul 10, 2020 · 1 comment

Comments

@ajkerley628
Copy link

Can we get the ability to implicitly set the rhost value when generating stagers? Hosting a teamserver in AWS lightsail causes issues when dealing with AWS NATing, since the host cannot bind directly to the public IP address (this option is available in DigitalOcean droplets). The listeners must bind to the local AWS IP address, which is then NATed through automatically by AWS.

When the stagers are generated, the local AWS IP address is set in the payload. Is there any current way to change this?

@d-sec-net
Copy link

Hey, you can set additional IP's using the callback url option within the listener generation. This allows the launchers to be used with redirectors so should work with the nat issue if you set your public ip as a callback url.
callback urls

This will generate an additional url that the stager will use when running within the payload. Currently however at least in the version / fork I am running it also includes the bind IP address which is perhaps not best if trying to conceal the actual IP of your C2 but it can be easily removed from launchers or additional IP's added on the fly.

Annotation 2020-07-14 150129

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