Jump to content

chrizree

Active Members
  • Content Count

    492
  • Joined

  • Last visited

  • Days Won

    30

Everything posted by chrizree

  1. -B is BSSID, i.e. MAC address, not SSID (or ESSID) which is -E, you mixed them up, it's the other way around ATTACK MODE d: Deauthentication and Disassociation Sends deauthentication and disassociation packets to stations based on data traffic to disconnect all clients from an AP. -w <filename> Read file containing MACs not to care about (Whitelist mode) -b <filename> Read file containing MACs to run test on (Blacklist Mode) -s <pps> Set speed in packets per second (Default: unlimite
  2. BSSID isn't -e, is it?! For attack mode "d" it should be -B. What version of mdk4 are you running?
  3. Nothing that gets logged related specifically to the payload afaik. You can run logread to see events. Events tagged especially for the Shark can be viewed using: logread -e Shark I guess you are connecting the Shark to the network the "common" way (via a switch port). There should be no real problem with that default payload and getting loot. Is the network restricted in any way? By MAC address making the Shark not able to connect? You can always try the payload I put up on my GitHub that "steals" the MAC address of an endpoint and then uses that MAC address when connecting to the network t
  4. opkg remove mdk4 wget https://github.com/adde88/openwrt-useful-tools/raw/packages-19.07_mkvii/mdk4_4.1-9_mipsel_24kc.ipk opkg install ./mdk4_4.1-9_mipsel_24kc.ipk which installs MDK4 4.1 (according to the info you get from MDK4 when running it from CLI) I.e. you shouldn't remove and reinstall the Mk7 MDK4 module itself, just leave that as it is. Just install a different version of MDK4 at command line on the Mk7.
  5. Do you have any experience involving problems with the SD card itself or has it worked as intended? I just started my Nano up after a long time not using it (just using the Mk7 nowadays) and I have no problems with either the SD card (as other have reported over time in the forum) or that PineAP refuse to stay enabled. It runs as expected. In what way are you powering the Nano? Does it get enough "juice" to make everything run problem free?
  6. Enable PineAP to get a monitor mode interface. Set the attack mode (using "d" here). Specify input and output interface. The "d" attack mode shouldn't really need two interfaces to be specified, but the module won't start mdk4 unless both are set, use wlan1mon for both. Using a blacklist = just make sure it's in the Mk7 file system somewhere and that it contains relevant MAC addresses for AP(s) to "attack". Add the path to the blacklist on the line in the module GUI. Specify channels to operate on. The Command line in the module GUI "grows" as parameters are set, for example a "full" line coul
  7. Doesn't that command throw a (rather long) error message back at you since the interface (wlan1) isn't in monitor mode? I can't in any way say that I'm a frequent user (or a user at all actually) of mdk4, but installing the module and its dependencies on my Mk7 wasn't all that successful. Everything looks OK when it's installed, but when running mdk4 from the command line of the Mk7 it just started attacking other APs than the one I had specified in the blacklist file (or at command line using -B). I did the same from one of my Kali boxes and that went all fine. So, I compared the mdk4 version
  8. What kind of MDK4 attack are you trying to get to work? What have you tried so far when it comes to CLI?
  9. Some modules are for sure obsolete but not because the modules themselves are obsolete, it's because of the fact that the methods (or whatever you like to call it) are obsolete/not working as a concept. I see a fair amount of "yelling" about SSLStrip, but that hasn't been working for years in practical use. Try running it on the Nano/Tetra and see how efficient it is. That along with other modules for the 6th generation that probably doesn't work anymore even if they are in the "list". Without me knowing how the Hak5 crew has been working during the development of the Mk7, my qualified guess i
  10. Ask in the proper forum section when it's about Mk7 modules https://forums.hak5.org/forum/109-mark-vii-mods-modules/
  11. There are different ways to accomplish this, I didn't do all the steps as per above, but if it gets the job done, it's all good
  12. Does the machine have access to the internet or is it "airgapped"? Tried different browsers? Any plugins active in the browser(s) that might affect the browsing experience?
  13. Looking at the errors you posted and checking the bash script, it's pretty obvious that it will throw errors. That bash script needs some adjustments to work properly. Just follow the errors and match them with the bash script and you'll see where it needs some changes.
  14. You can check a "howto" I put together on my blog if you need some inspiration https://soruhius.blogspot.com/2021/03/hak5-cloud-c2-as-windows-service.html
  15. What specific Android app are you looking for? What is it supposed to do?
  16. OK, then set it up as a Windows service. Note though that the C2 Windows binary most likely is a "non-service" binary which needs some extra steps to make it run as a service (compared to executable files that are designed to run as services).
  17. You need to run it as a service, what OS are you on?
  18. It's possible that a firmware recovery might solve it. Sounds a bit strange though that it should be needed, but if such a simple and basic thing as getting access to the Shark doesn't seem to work, maybe it's the way to go. I've never had such issues with my Shark, but if I had tried all possible (and logic) ways to solve the problem, I would do a firmware recovery to try to get it working.
  19. I haven't reacted on this post before since USB-C phones was the subject. However, I just want to add that you don't necessarily need a USB-C phone to interact with the Plunder Bug. I use the Bug with a Samsung phone that just has a MicroUSB port. It's a Samsung A3 2016 with rooted LineageOS 17.1 and it captures packets with success using the Hak5 Plunder Bug app. I.e. Samsung phone > MicroUSB male to Type A female USB OTG cable > Type A male to USB-C male cable > Plunder Bug.
  20. Try to avoid involving any virtual environment in arming mode before you know that it actually works with a "real life" computer. Disable all other network interfaces so that the network that the Shark offers is the only network that the computer can see/connect to.
  21. Don't expect an old field guide to cover a new variant of the Pineapple even though there are similarities between them. It's like bringing forward a Nokia 8110 manual when you have a brand new iPhone. It will for sure be vague in some aspects. What modules have you seen in videos that you can't find? Link/reference please... What exact modules from previous generations would you like to have? Is it on a "nice to have basis" or on a "need to have" basis? What are you going to do with modules that are based on concepts that are obsolete since years? I posted this on Discord yeste
  22. Is the Shark in arming mode when you try to connect to it, or is the switch still in attack mode?
  23. yes, of course it is that button! you have to liberate the hacker within yourself! 😉 don't restrict your actions, if you can't find a software button, then look for the hardware one and if you can't see it, pick the thing apart... well... you don't need to pick the Mk7 apart since the button is there in plain sight on the "front" along with the USB ports, you may want to change the script though if you want to try it out so that you avoid the Mk7 to reboot, perhaps something like: #!/bin/bash echo "Hak5 WiFi Pineapple Mk7 hardware button pressed!" >> /root/mk7_btn_actions.log
  24. The Croc is kind of picky when it comes to keyboards sometimes. I've looped through a bunch. Some keyboards work perfectly fine, others work as a keyboard but nothing gets caught by the Croc and some keyboards just don't work at all with the Croc in between.
×
×
  • Create New...