Jump to content


Active Members
  • Posts

  • Joined

  • Last visited

  • Days Won


Profile Information

  • Gender
  • Location
  • Interests
    Software; Hardware; Old Computers; Artificial Intelligence; Operating System Internals; System Architecture; Digital Equipment Corporation;

Recent Profile Visitors

3,148 profile views

MB60893's Achievements


Newbie (1/14)

  1. To my understanding, when the Bash Bunny is first plugged in, it draws power from the USB lines and boots its own Linux OS. From there, whatever options were listed in the script will be applied (such as the hardware ID), and after this point, the Bash Bunny will communicate its new settings to the USB Host device (i.e. whatever the bunny is plugged into.) As is indicated in the documentation for VID and PID: This would make sense, as drivers need to be present before a USB device can be mounted/setup for use by the system. Therefore, the VID and PID must be set BEFORE the bunny connects. Hope this helps!
  2. There are a number of packages I would like to update for my Bash Bunny. I use a variety of programming languages on my Bash Bunny, especially: Python 3 (3.7 and up.) GCC (5.0 and up.) GoLang (1.14 and up.) Lua (5.3 is there, but the latest is always nice.) I know the firmware images I'm using are based on Debian, but I'm not sure if there is a way I can get the latest packages without the risk of running software that isn't supported by the Bash Bunny. @Sebkinne and @Darren Kitchen, considering there hasn't been an update to the firmware since August 2019, can you please advise how best to proceed without borking anything? Thanks all! 🙂
  3. Execute the first cURL command with the --insecure flag. Then try executing the second command. If it prompts you with a GPG command, run that, then run the second command again, possibly with the --insecure flag as well.
  4. MB60893

    impacket SMB

    You should be installing all the packages through the bash bunny's serial console connection in PuTTY. Alternatively, just disable defender for the time being until impacket has been installed to the /tools folder on the bash bunny, then everything should execute without being exposed to Windows from the Bash Bunny's linux partition.
  5. Check the BashBunny Github Repository.
  6. Sounds like the Bash Bunny's physical switch may not be working correctly... If you can still access the bash bunny, it may be worthwhile flashing it with the latest firmware, seeing if that fixes it (in case it was just a software issue,) else contact the HakShop and see what they can do for you.
  7. Also worth noting that Windows Internet Sharing with the Bash Bunny seems to be quite temperamental at times. I've had to reboot mine and configure things in a specific way in the past numerous times.
  8. MB60893

    Python Tools

    As the Bash Bunny is essentially a Debian linux machine, just use apt-get install python for either version 2.7.3 or the newer python 3 versions. Then you can use PIP. If things don't install, make sure you are running with sudo privileges. EDIT: The impacket example is actually the tools compiled for the Bash Bunny into a single .deb file, which may then be installed using the dpkg package manager, hence the REQUIRETOOL part checks the tools directory to see if this is installed, and uses the tools there. You won't need to do this in Python, just simply tell the bash script to execute a python script, the same way you would run a .py file from the command line.
  9. Unless the device has a network port open (such as SSH or Telnet) this would be very difficult to accomplish, as physical/keyboard access is generally required to start powershell or command line programs. For Windows, I'd look into PSExec and other PSTools by Mark Russinovich as potential tools to accomplish such a task, but even then it may be difficult to gain access.
  10. Easiest thing to do is to reflash the bash bunny with the latest firmware.
  11. Flash the Bash Bunny with the v1.5 firmware. See if you still have the same problem after doing so.
  12. Try a different payload that doesn't require any dependencies/packages/tools on the bunny. As for the apt-get upgrade, this is most likely because you haven't followed the network sharing guide for Windows/Linux. There are instructions on the Bash Bunny Wiki.
  13. Run the chkdsk utility on the drive. Refer to any USB with this problem on Windows.
  14. I think Seb pinned a post in the Bash Bunny forum somewhere with the image for the bash bunny. Possibly try flashing that onto the bunny...? It may be a few versions behind, but when you update it, everything should work just fine. EDIT: Almost forgot the link: https://wiki.bashbunny.com/#!downloads.md
  15. Darren said in a video some time ago that he will be working on streamlining the process for approving and merging community payloads into a repository. Apparently the GitHub solution hasn't been working too well for some reasons (of which he did not go into detail.)
  • Create New...