You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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.
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?
The text was updated successfully, but these errors were encountered: