Jump to content


Active Members
  • Posts

  • Joined

  • Last visited

  • Days Won


Recent Profile Visitors

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

datguy_dev's Achievements


Newbie (1/14)

  1. I've only worked with the BB. Turns out what you need of a HID device for it to work in the BIOS are particular boot protocols. The device has to support them. So the digispark does not support it. But apparently the rubberducky, official Arduino* Uno, and Teensy do. I've settled on the Rpi + Teensy. (https://forum.pjrc.com/threads/48581-BIOS-project-sanity-check)
  2. Thanks a lot for testing Ranish! I appreciate it greatly. The rubberducky is the most promising HID automation device I've found thus far for doing such things. Moreover, the boot time. But what I really need is GPIO capability of the device as well because I configure many different models and brands. Therefore, I'd like to select which duckyscript* to run whether I need to configure Dell or HP etc. I noticed the BashBunny has GPIO, or additional GPIO pins given the vias on the board I could probably hack around with. But I could configure a BIOS before a BB boots so it wouldn't be as useful as a platform like the rubber ducky for my project. If you have advice on having GPIO, I'm all ears.
  3. The digispark does not work pre-boot or in the BIOS. Tried with two different systems, with different combinations of keyboards and states. Such as I thought perhaps the BIOS maybe become fixed on USB discovery once loaded ... But nothing. Guess I'd have to hack the electrical connections of a standard keyboard with transistors in order to do this.
  4. If your up to it, I'd appreciate it if you'd try entering the BIOS with your ducky. I just went on vacation and will soon try with the digispark. Prefer to use a rubber ducky as that is a better product for the project and whatnot.
  5. Greetings, I have a project idea to use a rubber ducky (or similar) to enter a BIOS and then configure some settings. A solution for a repetitive task of mine. I do not have a ducky atm, but I would imagine the rubber ducky would work in the BIOS and the menus as you can plug in a HID device after the fact and it'll work? But most importantly, I need it to be pressing F2/F10/F1 for example as the computer is powered on to enter the BIOS or boot to PXE. Is the rubber ducky or Arduinos capable of this?
  6. I should have mentioned I was running v1.3 at the time this happened. Yet, the problems I have began immediately after I changed the switch. Before that, it was fine. So I'm not entirely sure we have the exact same issues. I have wait 5 minutes, try to boot, and 70% or so of the tries it'll fail. Whereas if I wait 1 minute, it fails 100% of the time. However, there is like a 95% chance it'll boot if I remove the cover to inspect it, put it back together, then boot. But it crashes shortly after. Therefore I cannot recover nor change the firmware because my BB crashes after 15 seconds or so. Its truly bricked. Ran a continuity test on the switch. Seems to be working fine. Though it doesn't appear to be grounded directly to the USB negative. Odd. Oh well, peace out. I'm not going to buy another. May try the Rpi Zero route sometime down the road though.
  7. Do I really need to explain that the BB was plugged in after a period of time? To clarify that, there is a duration of time of when the BB is left unplugged - that when plugged back into a power source - that produces different boot sequences for the BB. Whether that be no power, a solid green led, or a slow blue led. For example, 1 minute between the BB being unplugged and plugged in, would likely produce no led; as in dead. Say 2-3 minutes of rest would more likely produce a solid green light, with it being plugged back in of course. Where 5+ minutes of rest might reach a slow blue led, with it being plugged back in of course. 1+1 Search for "bricked." There are numerous threads and thus this is "yet another" one of those threads. Those are your words, not mine. If someone can't put 1+1 together on the power discussion, I would not even attempt to try and explain that Python library, let alone take techincal troubleshooting advice from them.
  8. Greetings, I was in the middle of developing this Python library: https://github.com/datguy-dev/pythonbunny I was testing the "switch helper." I wanted to see what would happen if someone happened to change the switch position while the Bunny was running. Perhaps I could use the change of the switch for additional functionality mid-payload... Kind of risky, but with my research, I figured it simply indicates where and what resources to run at after booting. I thought it would be safe, but it crashed the Bunny when I did. Ever since I've been trying to get the BB working again. If I leave the BB unplugged for 5 minutes, it will sometimes boot to ARMing mode but crash shortly after. Sometimes in ARMing mode it will boot to a solid green led but not progress even waiting for ~10 minutes. The longer I wait with it unplugged, the better the odds of it booting. The led will not light in switch position 1 or 2 nor will it appear as a device. These other switch positions appear completely dead. One time, it appeared stable so I tried to run the recovery script in /usr/local/bunny/bin. It began the red/blue routine and within a minute or so it went a blue led. But after booting again, the firmware version was the same so I suspect that failed... Haven't gotten that far since. I have had no success with the unplugging recovery method given the inconsistent booting. Such as sometimes I get no power and a solid green led. Still, I tried to get at least 3 of the proper green led, just before blue, and it has yet to recover. Tried an 2A USB power adapter in the wall with the same results. One thing I found interesting is the BB with heatsinks, will not boot at all without the case. I'm not sure why that is. If I can't fix this BB, it'll suck because that library is going to be abandoned.
  9. That is true. But if you're good, no one should see it right? :D Personally, I'm in it for the tech and not the creds. I tinker around with Arduino and ARM boards as well. I guess you could call me a whitehat, as I just graduated not too long ago w/ certs and now work as a sys admin. Can't take such risks anymore. I did try out cucumber plaid. I didn't see a difference at first glance.
  10. Greetings, I was bored, so I cut a chunk off the top of the BashBunny and slapped a small heatsink on the CPU. The fit is snug, so I could use thermal paste (generic white). With storage, ethernet, and ssh, it idles around 50 C*? according to /sys/class/thermal/thermal_zone0/temp. Default governor. The heatsink is hot to the touch; not warm. I simulated a load looping "find /" and it got as hot as 55 C. I never had heat issues with the BashBunny. But it does look "cooler" so why not?
  11. It's not the LEDs. Its just I'm having all sorts of "saving loot" or writing issues that have been inconsistent and just wonky all around. I was hoping there was a definite answer to writing to the BashBunny. This shouldn't be a cryptic thing in the least. With my bashbunny, I found that it fails to write the first pass. But after being re inserted, it does work. I would really like to know the reasoning behind why I have to do that to save a simple text file.
  12. Greetings, Would anyone care to provide the most current means for "saving loot." Whether that be echo "${X}" > /root/udisk/etc or mv $file to /root/udisk. I'm sure both work, but I have had no luck saving anything run from a payload to the disk on the BashBunny. I just cannot figure it out even scraping through all the payloads posted on github. It's kind of crazy. I made a payload to test directories while using switch 1 or 2. Such as below, it's simple. Yet I'll get a green led saying that /see/more/butts is a directory! It makes no sense. Even if I change /root/udisk to /udisk it still lights green. I had a payload that used the echo write method for saving information to a file. But when I went to check the loot in arming mode, the payloads folder was gone! It just disappeared. :D I had to do a recovery and the first time, it failed. Second time worked a charm, but I wouldn't be surprised if my permissions or something is now even more messed up. It is working normally in every other context though. But I thought I'd ask as I don't want to brick the BB experimenting further. (! = not. -d = directory.) #!/bin/bash if [ ! -d "$(pwd)" ]; then LED R else LED G fi if [ ! -d "/root/udisk" ]; then LED R else LED G fi if [ ! -d "/see/more/butts" ]; then LED R else LED G fi
  13. Thanks for your reply. I just found your thread about this issue and it answered a lot of questions. ... That sucks for the time being huh? I remember watching hak5's bash bunny introduction video and Darren was combining attackmodes like it was nothing. [face palm]
  14. It has been wonky for me as well. I don't know what to make of it as of yet.
  15. No one else has had this issue? Maybe I have the wrong idea, are you supposed to only use a single attackmode at a given time?
  • Create New...