Catch22 Posted January 11, 2015 Share Posted January 11, 2015 I recieved my first Rubber Ducky on friday and have enjoyed playing with and I am dreaming big with the abilities this thing has! I just have one problem, my payloads don't run automatically. They will run if I press the button but thats the only way. I put a delay in at the beginning of the code like suggested in the FAQs but that was not the problem. Any help would be very appreciated! Firmware: Composite_Duck_S003.hex Code: REM Prints: Hello World! DELAY 5000 STRING Test DELAY 5000 STRING Hello Word If you have any questions about the setup please let me know and I will answer them! Quote Link to comment Share on other sites More sharing options...
Mr-Protocol Posted January 11, 2015 Share Posted January 11, 2015 Try increasing the delay, it takes a little time for hardware detection. REM Prints: Hello World! DELAY 15000 STRING Test DELAY 5000 STRING Hello Word Quote Link to comment Share on other sites More sharing options...
Catch22 Posted January 11, 2015 Author Share Posted January 11, 2015 I just tried increasing it all the way to 50000 and leaving it for an half hour with no luck :( Thanks though! I'm starting to think maybe its a firmware bug possibly (I am no expert by far!) but when I plug it in the LED blinks blue which I believe is the "normal"/"not running" state of the LED in this firmware version but once I hit the button is flashes red and blue until the payload finishes running. Not sure if it really means anything but thought it might be useful for someone reading! Quote Link to comment Share on other sites More sharing options...
Broti Posted January 11, 2015 Share Posted January 11, 2015 (edited) check the end of the FAQ for the firmware: Why Composite Firmware? Brings back the old Autorun/ USB-Switchblade attacks. Function To access Programs on the SDcard you are advised to label the SDcard eg. DUCKY Ubuntu The USB partition is normally mounted at /media/LABEL e.g. /media/Ducky OSX OSX will auto mount at /Volumes/LABEL e.g. /Volumes/Ducky Windows Depending on the number of additional Drives/Partitions the Ducky could appear on E:\ or F:\ Use wmic to dynamically locate the right drive letter for /f %d in ('wmic volume get driveletter^, label ^| findstr "DUCKY"') do set myd=%d Then execute your payload (this example duck.bat) %myd%/duck Edited January 11, 2015 by Broti Quote Link to comment Share on other sites More sharing options...
Catch22 Posted January 11, 2015 Author Share Posted January 11, 2015 In that they are explaining how determine the drive letter or name then they refer to a .bat file as being the payload I believe (not sure why since the injection.bin should be the payload) but it still doesn't help me. The problem I'm having is my ducky doesn't autorun. It will run if I press the button but not just from being plugged in. Thanks for post though! Quote Link to comment Share on other sites More sharing options...
Broti Posted January 11, 2015 Share Posted January 11, 2015 (edited) injection.bin ? You mean inject.bin, right? (Just checking ;-) ) Hmmm... sadly I can't test the firmware, cuz my dcuky is in one of my moving boxes. Edited January 11, 2015 by Broti Quote Link to comment Share on other sites More sharing options...
Catch22 Posted January 12, 2015 Author Share Posted January 12, 2015 Haha yeah still a newbie oops hahaha and I'm going to flash it with the newest non-composite firmware and see what happens later tonight! I'll post the results! Quote Link to comment Share on other sites More sharing options...
Catch22 Posted January 12, 2015 Author Share Posted January 12, 2015 Alright so tonight I tested two more firmwares. One was c_duck_v2_S002.hex which had the same behavior as the previously mentioned firmware that would not autorun. I wasn't overly shocked by this with it also being a composite firmware. Then I tested the m_duck_v2.hex and to my amazement it worked as intended and autoran the payload like it should! Little sad that I can't use to composite driver as I really liked having the storage space for executables I plan to look into this more and still try to pick the minds of the community because it doesn't seem anyone else has had this issue. Anyway hope these results can help! On a final note when flashing the new firmware everything worked without a hitch and all three times every one of the 11 tests passed. Quote Link to comment Share on other sites More sharing options...
cyber_dog Posted July 7, 2015 Share Posted July 7, 2015 Hi, i am having the same problem, my rubber ducky used to autorun payloads perfectly but in some point he stoped =/ the green light is up and stable (not blink) and the payload just not runing (ive tried some of the basic payloads...) i tried to flash it using ducky-flasher to 'duck.hex', no autorun. i tried to flash it using ducky-flasher to 'm_duck.hex', no autorun. Any help would be very appreciated! Quote Link to comment Share on other sites More sharing options...
shamwow Posted July 7, 2015 Share Posted July 7, 2015 I recieved my first Rubber Ducky on friday and have enjoyed playing with and I am dreaming big with the abilities this thing has! I just have one problem, my payloads don't run automatically. They will run if I press the button but thats the only way. I put a delay in at the beginning of the code like suggested in the FAQs but that was not the problem. Any help would be very appreciated! Firmware: Composite_Duck_S003.hex Code: REM Prints: Hello World! DELAY 5000 STRING Test DELAY 5000 STRING Hello Word If you have any questions about the setup please let me know and I will answer them! try c_duck_v2.1.hex and if you are printing hello world then where are you trying to print it? in cmd prompt or in notepad? maybe add one of them to that ducky script. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.