Bryfi
-
Posts
38 -
Joined
-
Last visited
Posts posted by Bryfi
-
-
I'd like to know the same. 1.1 isn't in my best interests at the moment.
-
SSH
in Bash Bunny
Give your BB internet connection. Then you may need to use the kali sources temporarily which I believe it is in /etc/apt/sources.list (just comment the regular sources and put the kali sources in) then run apt-get update && apt-get install setoolkit. You can switch back the sources if you wish.
-
9 hours ago, Dave-ee Jones said:
Uhuh.
Recovering your BB does reset your version, by the way. As I said above :)
Nice. How did you recover? 3 times stick in and out? Or do I use a command. I forget xD
EDIT: Figured it out. So happy I got this version now. Thank you so much!
-
8 minutes ago, Dave-ee Jones said:
Maybe try removing the line 'source bunny_helpers.sh' from the payloads. Since that line is irrelevant and the bunny_helpers.sh doesn't exist anymore, all variables being made environmental.
Also, some LED calls might not work anymore either, as that method was redone.
I have re-coded all the possible LED conflicts and fixed the lighting issue but the payload still wouldn't run. Said payloads either didn't source bunny_helpers.sh at all or were already coded for environmental variables.
EDIT: Had to keep bunny_helpers.sh for some payloads to work(WiPassDump). It's existence should not bother other payloads that don't source it.
-
This update has not been a productive one and I am wondering if there is a safe way to revert back to 1.0. This update has broken a couple payloads for me that were working before 1.1.
Should I factory reset the BB? The said payloads (BunnyTap, Quickcreds mainly) are apparently working for others but I cannot seem to get it to work.
-
On 04/10/2017 at 3:14 PM, LowValueTarget said:
The payload works fine for me on Win8, Win10.
You could potentially pipe the output of this line to a file in the loot or payload folder
python Responder.py -I usb0 $RESPONDER_OPTIONS &
How are you guys getting this to work?! Ever since this update, both Bunnytap and Quickcreds are broken for me. EDIT: Downgrading to 1.0 seemed to solve the issue.
-
Tried with both Win7 and Win10. Seems that this payload is also bricked. Any idea how I can log these payload while they are running so I have something to give to the devs?
-
10 minutes ago, LowValueTarget said:
Are you running v1.1 and did you run the impacket setup script?
cd /tools/impacket && python ./setup.py install
Just installed it going to retry.
EDIT: Works flawlessly. Good job.
- 1
-
Looks really good and stealthy! Only problem is it just creates a folder and does not execute the script.
-
Try recovering your BB. Plug it in and out about 3 times I think in order for it to recover. This update is not clean for all unfortunately. So you may have to recover it.
-
Seems like you guys got farther than I have. I was and still am unable to get this payload to work. Others do so its not my bb. Is there more I have to do other than copying the files into a switch1/2 folder? I have installed impacket and responder correctly.
-
27 minutes ago, LowValueTarget said:
I noticed that behavior sometimes
Sebkinne may have a solution or at least some insight.
I also have this issue with bunnytap (payload not running correctly) Do you think it is due to the update? It was working fine before then.
-
6 hours ago, defiant said:
Great! Thanks! This worked for me.
Then, a few lines changed in quickcreds and it's working again.
How did you get quickcreds to work. Mine refuses to work.
EDIT: Will there be an update to bunny_helpers.sh?
-
Payload runs fine. Goes through the setup but for some reason the LED turns off instead of finishing. Also nothing comes up in the loot/ folder
-
Just now, LowValueTarget said:
Don't worry about the payloads. All previous payloads should work. As far as I could tell, all LED statuses may not work; those that combine colors. (e.g. LED R B). Everything else seemed to worked fine.
I updated my payload and pull request to make it more 'compatible' with the new firmware.
Good to hear. I am still holding back upgrading temporarily due to the LED situation you mentioned. But I will upgrade eventually. Thank you!
-
Before I upgrade my BB, do previous 1.0 payloads become deprecated and unusable or you can still use Quack and Delay and GUI r
-
Make sure you have the correct name of the bash bunny in the script. e.g. if the name of your bash bunny is "Bash Bunny" then you either have to change the name to "BashBunny" (named this in most scripts) or change the script to match the name of your flash.
-
On 4/2/2017 at 0:33 AM, illwill said:
not enough space on the bunny
What if we were to place another flash drive into the machine that has sufficient space?
-
Are you guys still having issues? What I did besides change ECM to RNDIS (windows 10) is enable the network prompt when it pops up (basically I say yes). If you are still having problems, I am willing to give you the payload.txt I am using to see what the issue is.
-
3 hours ago, Bob123 said:
Sorry I got to start somewhere. I too have tried this payload from the github then just copying yours Kel. It completes but the folder is empty. What am I doing wrong?
Also my keyboard is a US or EN layout...what's the two letter for that? Is it just EN or US? I'm not sure if that's causing it or if there is something messed up with my powershell. Any help would be great. Thanks.
Hey there. You may need to change the name in the script
Q STRING 'cd (gwmi win32_volume -f "'"Label='BASH BUNNY'"'").Name'
My bash bunny is named "BASH BUNNY" So, you may have to change the name to whatever the name is when you put it in arming mode.
-
UPDATE: Blue light came on for like .5 seconds than dimmed out. I think this is a hardware issue.
-
Nothing. Just one green light. Switch is in arm mode. I have checked multiple times and switches. Same green light. Only payload that runs is nmapper and it used to flash yellow. Now I get nothing but the payload "runs". Like its executing blindly
-
I did I have left it in for a minute or to and it just stays dark. No blue light anymore like earlier.
-
It used to which is what is throwing me off. Now it just blinks green once then turns off. I tried factory reseting (in and out 3 times) no results. No red light
Update from 1.0 to 1.3
in Bash Bunny
Posted
I have Bashbunny 1.0 due to the bunnytap and quickcreds payloads working for 1.0 and not 1.1 so I downgraded. If I update to the version 1.3 directly, will I encounter any issues?