Search the Community

Just thought it would be fun to make my own little tutorial on this I know other people have already but just wanted to see how fast I could do it really..... Quack Quack lol :D

Violation of CoC

UPGRADE TO THE LATEST FIRMWARE Download the latest version of the Bash Bunny firmware from https://bashbunny.com/downloads Verify that the SHA256 checksum of the downloaded firmware files matches the checksum listed at bashbunny.com Slide the Bash Bunny switch into Arming Mode (closest to the USB plug) and plug the Bash Bunny into your computer Copy the firmware upgrade file downloaded in step 1 to the root of the Bash Bunny flash drive. Safely eject the Bash Bunny flash drive (IMPORTANT) With the switch still in Arming Mode, plug the Bash Bunny back into your computer and wait 10 minutes. When the bunny is done flashing, it will pop up as an storage device. INSTALLING LANGUAGES i have opened a pull request on the official repo to add the languages to the /languages folder (.json provided/made by ducktoolkit.com) But for now you will have to manually add them (Atleast from what i understand since i cannot get the ducktoolkit install payload to work) Download the Ducktoolkit compressed file-> https://github.com/hak5/bashbunny-payloads/raw/53a9e7fb69677b0480b2005a590471f4feacd180/payloads/library/DuckyInstall/DuckToolkit-1.0.1.tar.gz Unzip all the .json language files from "\DuckToolkit-1.0.1\ducktoolkit\languages" inside the .tar.gz file to\languages on the BashBunny (Connected while in arming mode) Remove and re-attach the bash bunny, you can now use different keyboard languages INSTALLING "IMPACKET" AND OTHER DEPENDENCIES There are 2 tools folders on the bash bunny itself, one lives in /tools on the Linux file-system which you can see and access using SSH/ Serial access.The other one lives in the mounted drive which you see every-time you connected the bunny as an storage device. What we effectively are going to do is to download the latest impacket source from github, place it on the bash bunny flash-mounted tools folder. re-attach and re-boot the bunny , this will copy the folder into the linux file-system tools folder, where we will install the module. Clone or download -> https://github.com/CoreSecurity/impacket as an .zip file. Unzip the "impacket-master" folder inside the .zip file into the /tools folder while the bash bunny is connected as an storage device (in arm mode) Rename the "impacket-master" folder to "impacket" ( remove and re-attach /reboot the bash bunny on the system. If you go to the same /tools folder now, the "impacket" folder should be gone. Serial/SSH into the bunny so you get a shell. and execute the following commands, in this order "cd" | "cd .." | " cd /tools/impacket/" | "python setup.py install" ( "|" separate each command, dont type the " quotes) remove and re-attach the bash bunny, and you are all good ! :)

Hello All, I just purchased two rubber ducky. I am new to this, but have following the youtubes and reading a lot of posts. Well my first attempt is to create the HELLO WORLD payload, but I am stuck at flashing the device. I am following the instructions located at : https://github.com/hak5darren/USB-Rubber-Ducky/wiki/Flashing-ducky My System : Windows 7 64bit 1. I already have the following MS Visual C++ 2010 Red. (x64/x86) installed 2. I installed Flip 3. I had to manually install the Atmel Driver 4. Downloaded firmware duck_v2.hex (i assume this is twin duck) from https://github.com/midnitesnake/USB-Rubber-Ducky/tree/master/Firmware/Images (right click > save-as > filetype (all files)) 5. I ran program.bat duck_v2.hex and it FAILS as Parsing HEX file with error "Invalid HEX file syntax" I have tried 3 other firmware images from the repo. but still same error on all of them :( Can someone help me to what I am doing wrong? Thank you.

So the pineapple has an APP in the android market. Anyone thought of making an app for the Ducky? Would be nice to be able to flash and adjust payloads on the go with an android device. Select the payloads through the app, dl them to our android device and flash them to the duck at will. Could also have a live editor to compile our own payloads. 1. could android flash the duck? / drivers out there for it? 2. anyone want to write the app? -thought process here is that we are mobile most of the time. half or our gear is ready to go. Using our mobile device vs a computer would make more sense to me to be less visible when it comes down to blending in on a pen test. Don't have to stop there, could be all the Hak5 tools wrapped into one app that have an interface. Lan turtle, etc. --- anyone? --- thoughts?

Ok so let me preface this with an apology in case my google fu has failed me. I've had a ducky for about a week now and have to be able to flash new firmware to it. I know you have to push the button during insertion to enter dfu mode. I have tried on a mac, windows 10 VM, and a kali box and have to get it. Nothing even seems to see it... Is there a way to verify dfu mode? Im hoping its not a faulty pin. Any help is greatly appreciated!!

running windows 10 with nano tethered, am getting bulletins and the firmware search found the new version however it sits. have attempted almost 10 times to get it to load.

Hello everyone, So, sometime ago I made a video about how to flash an AP121U with the WiFi pineapple firmware. I know that it is a little bit old, but I thing that it will be nice to have it here in the forums for everyone that wants this information in the future. Feel free to commend and subscribe to my channel ! thank you for watching Video link: https://www.youtube.com/watch?v=DsC4AinWrvs

I have no use for my MK5 and really need a repeater. https://forums.hak5....-as-a-repeater/ In the above thread he says flash dd-wrt? I was hoping since the Pineapple software is based off OpenWrt a flash of unmodified OpenWrt will be possible.

Hi, I'd like to flash the apple firmware if this is possible. What type of firmware would you write to run multiple OSs, and how would you flash the firmware --via USB? The firmware should remove the restrictions for 'gpt' and other concerns within the protected UEFI. The laptop in question is a MacBook Air (mid-2014). I hope to run OSX, Liberte, and Ubuntu Private Remix. Thanks for any suggestions! PS. If you have suggestions for wiping the UEFI and Firmware of any hacks, please, do share. Thanks!

Hi, so I've started using Ubuntu (after a really long time) and I have a really frustrating problem. I have dfu-programmer-0.5.4 and I've already extracted everything from its archive, but I cannot compile the code so I can flash my duck. It cannot compile because the usb.h file is missing. Can anyone help? Thanks.

Hey guys, I followed the instructions at the bottom of this page https://wifipineapple.com/?flashing for unbricking the pineapple. I downloaded the stager, set the pineapple to a static IP address of 192.168.1.2. Powered it on and navigated to 192.168.1.1 and made it to the MK5 Recovery Page. I selected the stager.bin and uploaded it, then nothing happens, even after 15-20 minutes, my browser just says "Connecting to 192.168.1.1". Could someone offer me some advice or help please?

All, Got a MKV and had it running 1.0.4 - working fine for months, including most of today. Today after finishing some work on dnsspoof and /www/index.php, I turned her off and later back on. Now I get a solid green light, and a very faint red light and that's it. No ethernet link recognised so I don't have a workable LAN connection. Tried setting dips to U,D,D,U,U and U,U,U,U,D left to right per reflashing/recovery instructions to no avail. Tried multiple LAN cables, and both the USB and primary power supplies that came with the unit. There's definitely no LAN link. Any help appreciated! Thanks, _sw1tch_

When attempting to compile dfu-programer-0.5.4 on Ubuntu, getting many errors when "making". ./configure no problem. Any help much apprerciated. make all-recursive make[1]: Entering directory `DuckEncoder_2_6_3/dfu-programmer-0.5.4' Making all in src make[2]: Entering directory `DuckEncoder_2_6_3/dfu-programmer-0.5.4/src' gcc -Wall -g -O2 -I/usr/include/libusb-1.0 -lusb-1.0 -o dfu-programmer main.o arguments.o atmel.o commands.o dfu.o intel_hex.o util.o main.o: In function `main': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/main.c:58: undefined reference to `libusb_init' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/main.c:108: undefined reference to `libusb_release_interface' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/main.c:121: undefined reference to `libusb_close' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/main.c:131: undefined reference to `libusb_exit' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/main.c:79: undefined reference to `libusb_set_debug' dfu.o: In function `dfu_transfer_out': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:836: undefined reference to `libusb_control_transfer' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:836: undefined reference to `libusb_control_transfer' dfu.o: In function `dfu_transfer_in': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:863: undefined reference to `libusb_control_transfer' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:863: undefined reference to `libusb_control_transfer' dfu.o: In function `dfu_transfer_out': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:836: undefined reference to `libusb_control_transfer' dfu.o:DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:863: more undefined references to `libusb_control_transfer' follow dfu.o: In function `dfu_device_init': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:388: undefined reference to `libusb_get_device_list' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:394: undefined reference to `libusb_get_device_descriptor' dfu.o: In function `dfu_find_interface': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:677: undefined reference to `libusb_get_config_descriptor' dfu.o: In function `dfu_device_init': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:415: undefined reference to `libusb_open' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:417: undefined reference to `libusb_set_configuration' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:445: undefined reference to `libusb_close' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:451: undefined reference to `libusb_free_device_list' dfu.o: In function `dfu_find_interface': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:716: undefined reference to `libusb_free_config_descriptor' dfu.o: In function `dfu_device_init': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:419: undefined reference to `libusb_claim_interface' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:436: undefined reference to `libusb_release_interface' DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:426: undefined reference to `libusb_free_device_list' dfu.o: In function `dfu_make_idle': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:814: undefined reference to `libusb_reset_device' dfu.o: In function `dfu_device_init': DuckEncoder_2_6_3/dfu-programmer-0.5.4/src/dfu.c:431: undefined reference to `libusb_free_device_list' collect2: error: ld returned 1 exit status make[2]: *** [dfu-programmer] Error 1 make[2]: Leaving directory `DuckEncoder_2_6_3/dfu-programmer-0.5.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `DuckEncoder_2_6_3/dfu-programmer-0.5.4' make: *** [all] Error 2

ducky-flasher I was finding the process of flashing the ducky kind of a pain (and I wanted it faster XD), so I wrote a small program in python to do the work for me. I thought I share it :) https://code.google.com/p/ducky-flasher/ It can flash the following firmware: duck.hex v2 (Duck(Original)) usb.hex v2 (FAT Duck) m_duck.hex v2 (Detour Duck(formerly Naked Duck)) c_duck.hex v2 (Twin Duck) (Special 1) (Special 2) Installation 1. Install dfu-programmer (apt-get install dfu-programmer) 2. Download ducky-flasher 2. unzip ducky-flasher1.0 3. cd ducky-flasher1.0 4. sudo python setup.py 5. sudo ducky-flasher Usage To start simply type ducky-flasher in a terminal emulator Insert your ducky while holding down the GPIO pin to put it in DFU mode Uninstalling 1. sudo python uninstall.py https://code.google.com/p/ducky-flasher/

What I am saying is: cannot find FILE to flash firmware on UG802 I try over and over again to find the file. When I have found a file similar, It won't work ): All Firmware Files for UG802 Ubuntu "Invalid" Tried to use multiple flashers, all which state the ubuntu rom for the ug802 is invalid...... So what is wrong??Already rooted, Already have ADB and the other one working..... even tried a manual flash, only flashers really WORK. UPDATE: The flashers aren't working, I cannot use adb, and manual flash is not working

Since people around the globe are struggling to find all the original Ducky Code. I have chucked it all up on Google Code (with help from Dnucna). http://code.google.com/p/ducky-decode/ Find all Firmware Find Flashing Software Find Dnucna's much improved Encoder v2. Find old Encoder version 1 Find example of ducky-decode.pl (current only decodes US languages) - if you ever wanted to know what script the ducky was preinstalled with (anything nasty or simply a harmless message :) (depending where you obtained the Ducky)) Most importantly you can find updates. --Snake

Hi everybody, I found too much thread as : "My pineapple is bricked !" "I'm stuck on the redirect loop" "New FW not working" .... Please read a bit more changelogs before upgrade .... So we can focus on real problems ! (I think Seb is going to have a stack overflow if people don't stop this and still don't read docs...) Thanks to all the community ! Cheers

I just bricked my pineapple mark IV. I made a firmware flashing and my pc Rebooted in the sametime..... now I can't access my router pineappe when i try, i just reach the "redirect.php" in loop :( is there a way to fix it?

Hi All, I tried loading the auto-rickroll hack from the following tutorial http://hak5.org/hack...-wifi-pineapple I followed all the instructions and since I rebooted my pineapple (last step) I can't connect to it - It's not broadcasting an SSID and plugging in an ethernet cable (PoE LAN port) does not do anything (LAN light does not come on). I've tried re-setting, power cycling, different PC and still get nothing. Additionally I've noticed when powering up, the LAN and WAN lights flash once, WPS light flashes for about 10 seconds and then nothing but the power light remains on. I've come to the conclusion that it's now bricked - especially since I just saw the comment at the bottom of the tutorial saying I needed to remove an additional line. Guess this is karma for trying to rick roll the entire office tomorrow :P Just wondering if anyone else has run into this or if you have any ideas how I can avoid buying a console board to perform a clean flash (SSH wont work either since the pineapple is not broadcasting a SSID) Any help would be appreciated! Cheers, Rich