Jump to content


Active Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by chrizree

  1. I answer the same way as I did to the question in the Nano section of the forum; I don't see that this is a real problem though, nothing says that the client should reconnect specifically to the Pineapple just because the Pineapple deauthenticated the client device. On top of that, if you have an AP/SSID that you protect with WPA2 PSK and try to mimic that AP with your Mk7 using the open AP, you will never get clients to connect. You can't mimic an SSID and expect clients to connect as long as you don't have the same security on the mimicking AP as the original ("copied") AP has.
  2. At about 19 minutes into the video where the deauth starts it shows another MAC address than the one that the actual AP has. You were commenting on channel hopping or channels at that point, but it's not hopping channels, it's still on channel 8. The thing is that you need to specify the BSSID of the AP as well with the parameter/option -B to only deauthenticate the specified station from the desired AP, for example: mdk4 wlan1mon d -c 8 -B <MAC address of the AP> -S <MAC address of the station/client> Then, at about 21 minutes where you run the mdk command from the Pinea
  3. I'm not sure if I understand the question, it all depends on how you start your C2 instance. If you start C2 with a domain name, then the device.config file will be populated with the very same domain name, which in turn is used by the Hak5 device to communicate with the C2 instance. The same if you start C2 with an IP address, then the device-config file will contain the IP address and the device will use that.
  4. wow, that was tldr, I hope I get the time to read it all some day
  5. Install the Evil Portal module, copy the files from GitHub to a directory representing the module under /root/portals on the Mk7, then enable/start the Evil Portal module and activate the portal
  6. At first I thought your 5GHz USB NIC was a bit "strange" since it showed up as a 7601 chipset device, but now when reading your old post again I realize that I wasn't paying attention to what you actually had pasted. That 7601 line from lsusb that you showed was one of the internal radios of the Mk7 itself (based on the Bus and ID info). I have the same output on my Mk7 for my internal radios. You had the 7612 there all the time most likely, you just didn't see it. So, your 5 GHz is probably as correct as it can be. And I guess the Mk7 itself is also not the issue here either. Before running M
  7. It's better to post Mk7 questions in the Mk7 part of the forum, not where the Nano is discussed... I don't see that this is a real problem though, nothing says that the client should reconnect specifically to the Pineapple just because the Pineapple deauthenticated the client device.
  8. Deauth works every single time for me. I grabbed a test/lab home router with a 5 GHz AP and two devices connected to the 5 GHz WiFi network (2 Android phones). Using MDK4 both from CLI and the module web GUI on the Mk7 deauths the devices with 100% success from the 5 GHz AP. I have probably done 20 iterations now while testing.
  9. Just remember to create new device.config files if you need to correct some setup issue and copy them to each device
  10. I can try later when I get some time to do it, I know MDK4 is working on 2.4GHz at least since I did a PoC on that some week ago
  11. You probably start the C2 service with the wrong command if you can't see an IP address or a domain name in the device.config file. I know users do this since I have helped some figuring out why their Hak5 devices doesn't connect to their C2 instance. Are you using the public IP of the VPS (or domain name if you use that)? Some use Darren's setup videos on YouTube when installing their C2 instance (which is totally OK since they are good and accurate videos), however... they sometimes take things out of context since they aren't skilled enough and, for instance, starts the server with $IP as i
  12. ok, that's strange, I have a 7612 based USB NIC and it shows up correctly as a 7612 device on the Mk7
  13. ok, I'm not familiar with alternative firmwares, just the stock one coming with the Ducky (if I want such features, I use other Hak5 devices or alternative hardware solutions), no idea why it shows up as an ordinary USB drive, probably a feature of the alternative firmware, someone else might have an explanation to why this is happening, the script looks fairly standard though, more or less a copy of the example that is on the Hak5 Docs website
  14. Post the script here so that it can be looked at, difficult to say otherwise what may have gone wrong
  15. I guess you need to use iptables rules and ipv4 forwarding, search for it, I use similar setups but not specifically the use case scenario that you are describing. Another way that may be possible would be to use VPN and some access server.
  16. There is probably a difference in version of MDK4 between your Kali box and the one that is installed on your Mk7. Most likely "4.0 v1" on the Mk7 and "4.1" on your Kali machine. I've experienced other types of problems with the 4.0 v1 version on the Mk7 (not with 5GHz specifically though so it might not solve your problems if it's driver related, 5GHz specific or such). Try installing a newer version of MDK4 on the Mk7 and see if it works better. opkg remove mdk4 wget https://github.com/adde88/openwrt-useful-tools/raw/packages-19.07_mkvii/mdk4_4.1-9_mipsel_24kc.ipk opkg in
  17. Is the Pineapple your only Hak5 device or do you have other Hak5 devices that are already connected to your C2 instance and working well without any problems? In which way do you run your C2 instance? Locally on your own network or somewhere on the internet (VPS or such)? How do you start your C2 instance? Manually or is it set up as a service? If running the C2 instance in a VPS, have you checked any eventual firewall and its configuration. Does it allow communication from the "outside" on the ports that the Hak5 device needs opened to be able to communicate with the C2 instance? If you look
  18. have you tried to add txpower to /etc/config/wireless for the specific interfaces that should have increased transmit power?
  19. Something has probably gone wrong when downloading the zip file. Split it up instead to make sure every step is successful. Run: wget https://c2.hak5.org/dl -O c2.zip first and make sure the zip file is correctly downloaded. It should be about 46 MB in size (46 214 845). Then unzip it using unzip c2.zip
  20. What country have you set in the Pineapple web GUI?
  21. Use the correct keyboard language for the situation when encoding the payload script, then just use the function keys in the script. I would suggest using the JS Ducky Encoder along with a language file from the Bash Bunny repo on GitHub https://downloads.hak5.org/ducky https://github.com/hak5/bashbunny-payloads/tree/master/languages
  22. That is not DUCKY script. That is most likely some code for a Digispark unit/device, looks very "Arduino".
  23. You could simplify the download process in the video even more instead of having to find the GitHub repo on the internet, download the portals to some intermediate place, unpack them and then transfer them to the Mk7 using some "non native" Windows software. I have a script on my GitHub doing the download procedure, but it's done directly on the Mk7. https://github.com/chrizree/PineappleEPfix/blob/main/just_add_the_portals.sh
  24. Not sure what rubberduckytoolkit.com is, can't reach it either, perhaps you mean ducktoolkit.com... I would suggest using JS Ducky Encoder instead that can be downloaded from the Hak5 downloads web site https://downloads.hak5.org/ducky
  25. ok, but do you have any other SD card (not the one you got from Hak5) that you can try?
  • Create New...