-
Notifications
You must be signed in to change notification settings - Fork 2.2k
FAQ
Brendan Coles edited this page Jan 25, 2016
·
21 revisions
By default, beef/beef is the login. Check out the documentation.
Be sure to read the documentation (and here also), and take care especially of the following points :
- Enable MSF integration by changing
beef.extension.metasploit.enable
to true in BeEF's main config.yaml file. - Ensure you load the msgrpc interface in Metasploit before starting BeEF:
msf > load msgrpc ServerHost=127.0.0.1 Pass=abc123 SSL=y
- Ensure that the IP address supplied to Metasploit with the
ServerHost
parameter is the same IP address as specified inbeef.extension.metasploit.host
- Ensure that the IP address specified in
beef.extension.metasploit.callback_host
is the publicly accessible IP address for victim connections to Metasploit. - Ensure that if
SSL=y
was supplied to Metasploit when starting msgrpc thenbeef.extension.metasploit.ssl
is set totrue
.
- Ensure
beef.http.public
andbeef.http.public_port
are set to the public WAN IP address and public WAN port respectively. - Forward the public port (default 3000/tcp) from your border router to
<LAN IP>:3000
of the BeEF server. - Additionally, ports 61985/tcp and 61986/tcp must also be forwarded if web sockets are enabled for communicating with BeEF.
- Likewise, some BeEF extensions, such as IPEC and DNS, require additional ports to be forwarded. Review the associated config.yaml file for each extension and ensure the appropriate ports are forwarded.
Yes! Simply specify the public domain name and port in beef.http.public
and beef.http.public_port
respectively.
- Configuration
- Interface
- Information Gathering
- Social Engineering
- Network Discovery
- Metasploit
- Tunneling
- XSS Rays
- Persistence
- Creating a Module
- Geolocation
- Using-BeEF-With-NGROK