When a proxy is set, poseidon sends CONNECT requests with the default golang user-agent "Go-http-client/1.1", rather than using the user-agent defined for the payload. This can create some opsec issues, as the traffic can be signatured as out of place.
A quick fix for this would be to add a call to ProxyConnectHeader during the headers check in http.go, so that the user-agent matches what is defined during build.
Steps to reproduce:
Set http/https proxy variables in environment
Run poseidon payload with default config
Have a netcat listener ready on the proxy:port
Observe user-agent is golang default and not the one defined during payload generation
When a proxy is set, poseidon sends CONNECT requests with the default golang user-agent "Go-http-client/1.1", rather than using the user-agent defined for the payload. This can create some opsec issues, as the traffic can be signatured as out of place.
A quick fix for this would be to add a call to ProxyConnectHeader during the headers check in http.go, so that the user-agent matches what is defined during build.
Steps to reproduce: