Jump to content

Recommended Posts

Posted

First thing im gonna say is that i know i made many mistakes and that why im in this situation. So first mistake is that i downloaded the payloads to a separate folder off the bunny. then i added the bunny tap payload to the second switch. i didn't change any of the scripts or attack modes. i plug the bash bunny into my linux pc and nothing happened. so i take it out switch it to arming mode and bam the bunny is stuck on read-only. i tried to do a forced recovery a few times. the first time i plugged the bunny in after the recovery it gave a lock icon to all the files in the bunny and still keeped the bunny tap files in the second switch location. i tired the recovery the second time and now it wont mount and show up in my connected devices. I have no idea where to go from here.

Posted

UPDATE

i plugged in my bunny into my windows system, windows then said how there was an error and how it would like to run repairs i said yes. unplugged then replugged and bam it mounted. first thing i did was remove all the bunny tap payloads. i then plugged it back into my Linux machine and it fully works again.

Posted

Hi Lunch,

Now that you are up-and-running again, I suggest you update to firmware 1.1. Once you have done that, serial / ssh in and execute the following command: "reformat_udisk". This will make sure it's properly set up and formatted for all systems.

  • Upvote 1

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...