daven2411 Posted November 5, 2017 Share Posted November 5, 2017 As a bare minimum you would expect the Payloads that are downloaded onto the Bash Bunny when you run the Bunny Updater to work. The only change you should need to make is to change the ATTACKMODE so the payload runs on Windows or MAC/*nix. There are so many people complaining about the payloads not running. Maybe the development team could put some time & effort into getting the supplied payloads to work. Quote Link to comment Share on other sites More sharing options...
Foxtrot Posted November 5, 2017 Share Posted November 5, 2017 Can you elaborate on what’s broken? Quote Link to comment Share on other sites More sharing options...
daven2411 Posted November 5, 2017 Author Share Posted November 5, 2017 OK. Let's start with 'quickcreds'. The LED flashes amber and never reaches a steady green even after 30 minutes. It creates a folder under loot called quickcreds, and under quickcreds it creates a folder called Dave-Win8-HP-1 which is my computername-1. This folder is empty. Quote Link to comment Share on other sites More sharing options...
UnLo Posted November 5, 2017 Share Posted November 5, 2017 (edited) Did you install responder? Nvm I see it created the folder... Sounds like it's working. What version of windows / update is the target machine? Edited November 5, 2017 by UnLo Quote Link to comment Share on other sites More sharing options...
biob Posted November 5, 2017 Share Posted November 5, 2017 Lol... I guess he’s using windows 8 :-) Quote Link to comment Share on other sites More sharing options...
daven2411 Posted November 5, 2017 Author Share Posted November 5, 2017 Sorry, my PC name is misleading. It was Windows 8 when I bought it but it has since been upgraded to Windows 10. Also, responder is installed as are the other two tools. Am I supposed to do apt-get update and apt-get upgrade from a putty sessions when logged into the Bash Bunny ??? 1 Quote Link to comment Share on other sites More sharing options...
PoSHMagiC0de Posted November 6, 2017 Share Posted November 6, 2017 The issue you are most likely encountering is due to the improvements to windows 10. Microsoft has been actively hardening Windows 10. To test quickcreds on Windows 10, open file explorer and explore to any network location. Doesn't have to be real. Like: \\blah Quote Link to comment Share on other sites More sharing options...
daven2411 Posted November 6, 2017 Author Share Posted November 6, 2017 You are spot on. When I browsed to any network location, the LED turned green and there was output in the loot folder. Is there any way to automate this intermediate step? Can GET TARGET_OS return more details like the version of Windows that is running? Quote Link to comment Share on other sites More sharing options...
sundhaug92 Posted November 6, 2017 Share Posted November 6, 2017 @daven2411 GET TARGET_OS doesn't currently support details.@thehappydinoa could perhaps implement some GET TARGET_OS_DETAILS or something, the problem is returning the amount of detail that's actually wanted. For example, some times you might want IS_WIN7_OR_HIGHER and other times you might want IS_VERY_SPECIFIC_WINDOWS10_BUILD. While you could get some details from nmap, it's not always correct and can lack details. The best way would be to execute the following powershell-command and return its values tot he BB via for example the networking or filesystem: [System.Environment]::OSVersion.Version Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.