beef

[unknown- DF Member Posts:4 Threads:3 Reputation 0]

Is there anyway to hide my public ip when using beef? Instead of having the victim seeing it in the url when they visit the page?

[beta DF Member Posts:120 Threads:11 Reputation 3]

The 'callback_host' and 'callback_port' in './extensions/metasploit/config.yaml' should be the public IP/port for metasploit. This would be your VPN IP address.

You'll also need to configure BeEF for metasploit RPC so BeEF can communicate with metasploit. ('host' 'port' 'user' 'pass' , etc)

Hope this helps.

Similarly, if you're running BeEF locally behind NAT you'll need to configure a public IP address if you want to access it from the internet. You can do this with 'public' and 'public_port' in ./config.yaml. This is the IP address/port you will use for the hook. You'll also need to forward port 3000 from your router to BeEF.

Additionally, you'll also need to forward ports 61985 and 61986 from your router to BeEF if you want to use websockets instead of XHR for communicating with the hooked browser.

[Testhuman DF Member Posts:14 Threads:8 Reputation 0]

The 'callback_host' and 'callback_port' in './extensions/metasploit/config.yaml' should be the public IP/port for metasploit. This would be your VPN IP address.

You'll also need to configure BeEF for metasploit RPC so BeEF can communicate with metasploit. ('host' 'port' 'user' 'pass' , etc)

Hope this helps.

Similarly, if you're running BeEF locally behind NAT you'll need to configure a public IP address if you want to access it from the internet. You can do this with 'public' and 'public_port' in ./config.yaml. This is the IP address/port you will use for the hook. You'll also need to forward port 3000 from your router to BeEF.

Additionally, you'll also need to forward ports 61985 and 61986 from your router to BeEF if you want to use websockets instead of XHR for communicating with the hooked browser.