hak5 / bashbunny-wiki Goto Github PK

There should be a section that explains how to update the bash bunny. I'm assuming sharing the internet connection and then apt-get update && apt-get upgrade but are there other things that need to be updated? Things in /dev/nandg? Any firmware?

Would be helpful to have on the wiki.

Something has clearly changed recently in windows connection sharing as the provided instructions do not work under Win7. I propose the following alteration to the HOWTO procedure:

Share Internet Connection with Bash Bunny from Windows

• Configure a payload.txt for ATTACKMODE RNDIS_ETHERNET

  • On a Windows PC boot on payload 1 switch position (Left most position)
  • Go to the directory on the newly available USB drive under Windows - payloads/switch2
  • Edit the text file "payload" and change the line containing ATTACKMODE
  • Change the "ATTACKMODE XXXXXX" to "ATTACKMODE RNDIS_ETHERNET"
  • Save the file & exit notepad.

• Connect to the onboard bashbunny computer using the (separate) instructions for a serial terminal connection under Windows.

  • Make sure you download PUTTY from a safe source - putty.org
  • We want to manually set the IP address of the bashbunny onboard computer
  • To do this we use nano editor " nano /etc/network/interfaces.d/usb0 "
  • change the file to reflect:

  allow-hotplug usb0
  auto usb0
  iface usb0 inet static
  address 192.168.137.2
  netmask 255.255.255.0
  gateway 192.168.137.1
  dns-nameserver 8.8.8.8
  dns-nameserver 8.8.4.4

  • Save the file and exit nano editor.
  • shutdown the usb device - " sync; init 0 "
  • Unplug the bashbunny from the computer.

• Boot Bash Bunny with RNDIS_ETHERNET configured payload on the host Windows PC

  • Switch the USB switch key to position 2 (middle position)
  • Plug the bashbunny into the computer
  • The computer will install device driver files for a new network connection

• Identify the Bashbunny network interface device

  • Open Control Panel > Network Connections (Start > Run > "ncpa.cpl" > Enter)
  • Identify Bash Bunny interface. Device name: "IBM USB Remote NDIS Network Device / Local Area Connection 2"
  • Close all network interface dialogues

• Enable internet connection sharng with your current internet connection

  • Open Control Panel > Network Connections (Start > Run > "ncpa.cpl" > Enter)
  • Identify which connection is your current connection to the internet for your PC. In this example we will take "Wireless Network Connection"
  • Right-click Internet interface (Wireless Network Connection) and click Properties.
  • From the Sharing tab, check "Allow other network users to connect through this computer's Internet connection", select the Bash Bunny from the Home networking connection list (e.g. Local Area Connection 2) and click OK.
  • A warning Dialogue will pop up notifying you that the IP address of Local Area Network 2, i.e. the bashbunny adapter, is now 192.168.137.1

• Because we have manually set the IP address to be 192.168.137.2 for the bashbunny onboard computer and the default gateway is now set the IP of the computer sharing its internet connection, routing should now work!

  • You can now just putty ssh into the device at 192.168.137.2

Don't know if its a software or hardware issue
Just got the bunny today loading in simple Quack payloads as basic tests
Sometimes switch 1 will not work it mounts and just sits there then i copy and paste the payloads to switch 2 then it works perfect then without editing anything else switch to the first one and it works perfect just the same.

The wiki mentions to run the bb.sh script to share internet with the bash bunny but it doesn't say if you should try to run that script on the bash bunny via transferring the file and connecting via serial or if you are supposed to run it on the host OS.

I realize it may sound obvious to run it on the host but I think clarification would be helpful.

A section on how to share internet from macOS is needed. Windows and Linux are covered and as much as I hate to admit it, lots of people use macOS and would benefit from the documentation.