Jump to content


Active Members
  • Content Count

  • Joined

  • Last visited

About HeadScratchCode

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you're doing it on Linux Debian, you should set the payload to RNDIS_ETHERNET From my experience it doesn't work if I use ECM
  2. This is one of the best payloads. Even if you can't snag the plain text (windows 10) you still get the password hashes. If you can't get it working. just add a few more DELAYs. As, I'm in China, I have to add Q SHIFT once it opens the terminal. This is because many systems use a pinyin input method that switches back and forth from English to Chinese by pressing SHIFT. If I don't, the terminal will fill up with Chinese characters. Great payload dude!
  3. Hi guys, sorry for a late reply. I couldn't reply for some reason. Yes, from the post labeled 'tools' I did download gohttp. Along with this, I downloaded responder_2.3.3.6-2 which is not from that same 'tools' post, but from the main QuickCreds thread. The reason I did downloaded responder_2.3.3.6-2 instead of the one Seb's posted one is because it solves the problem of QuickCreds being stuck in a responder loop (Amber light continuous flashing). I miss spoke when I said the tools folder in root. I should have said: after logging in as root via SSH, then cd.. , then cd tools, responser & gohttp are not there. Not I figure that the responder I tried to install just doesn't work, & as you mentioned, gohttp won't display in /tools anyway. I tried to install impacket, and it worked fine, so there is no installation issue after all - I guess. However, I could install responder_2.3.3.6-2 before I upgraded to the latest firmware, and it did solve the QuickCreds issue that a few of us are having, so ideally I wish that this version of responder would install. I guess I now need to find another solution to get QuickCreds working - but that's for another thread. Yes. Thanks for helping. Thanks everyone. Overall: There is actually no installation bug, as gohttp won't show in /tools anyway & responder_2.3.3.6-2 doesn't install (it seems).
  4. I recently upgraded the bash bunny to version 1.3_264 After following the install tools method, the tools don't appear in /tools. I first downloaded the tools, put them in the tools folder of the bash bunny while it was in arming mode. Plug it back in again on arming mode, the magenta LED display as it is meant to. After this process finished, there were no tools to speak of in the /tools folder in root via SSH. Therefore, QuickCreds won't work. Any ideas? Thanks.
  5. I think I'm having the same issue as the comment above, but I'm unsure how to fix it. Successfully continuing past the IEX string fails. The image below displays the problem. Would be graterful for any help in finding a solution. Thanks, guys.
  • Create New...