Struthian Posted November 17, 2017 Share Posted November 17, 2017 I want the Bash Bunny to work reasonably well with Windows but not have the same identifiers it comes with. Can Hak5 recommend an alternative VID/PID or SN to use in an attack that disguises the Bash Bunny in a cromulent manner? I like the OS determination method represented in the WIN93 prank and other payloads. However, in a windows computer already set up with the Bash Bunny for Ethernet sharing, this does not work well. I also imagine it might not work well in a computer that is actually using the embiggened blue vendor products that you are spoofing instead of the Bash Bunny. I wonder if, during the development of the Bash Bunny, you had some VID/PID that worked sort of OK which I could spoof, thus having an alternative ethernet RNDIS device. This could be useful for other payloads too. I'd like to enhance the OS determination of the WIN93 prank to take another try where if not windows or linux, try an alt vid pid sn mix. I will experiment with this as well. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.