Jump to content

chrizree

Active Members
  • Content Count

    248
  • Joined

  • Last visited

  • Days Won

    15

3 Followers

About chrizree

  • Rank
    Hak5 Zombie

Profile Information

  • Gender
    Male
  • Location
    localhost
  • Interests
    Anything IT related and... a lot of other stuff

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Have you verified that the Galaxy Note is rooted?
  2. Most likely not. In some other situation, I would be bothered, but not with the Pineapple. It's root anyway and it's a known fact that the user exists and it's just the web GUI, not affecting ssh.
  3. Most likely the 3 pack of these https://shop.hak5.org/products/9-dbi-dipole-antenna
  4. It will most likely make no difference at all, but since you seem out of options, why not try anything that is possible. Don't forget that you still need to connect to the Nano using the USB cable when trying to do a recovery so even if adding power, you need to put the other USB connector of the Y-cable into the computer. I'm sure you understand that, just want to be extra clear about it.
  5. I assume that you follow the procedure described in the docs https://docs.hak5.org/hc/en-us/articles/360010471774-Firmware-Recovery I haven't tried it when I have done firmware recoveries on my Nano, but I don't think that SSH is supposed to be available in that mode. Not that it should make any difference, but, have you tried different browsers when trying to connect to the Nano "recovery web server" @ 192.168.1.1? Incognito window? Making sure you aren't trying to use https? Making sure that the Nano gets sufficient power? I seldom trust that the Nano gets enough power even when using t
  6. That's not a USB Rubber Ducky related question, contact the maintainer of the digiQuack tool instead... For starters, you could step through the code, there are elements in it that will throw errors, but, again... that's not USB Rubber Ducky related, it's how you use the Windows OS to execute things
  7. As Rkiver suggested, there's a Bunny section of the forums that should be used, so I guess this thread should be moved. Anyway, there are some bits and pieces that could render possible problems in the original code (i.e. the first post, which seems based on the "official" nmapper payload and then adjusted). For starters how nmap is spelled, with a capital "N" that will throw a "Nmap: command not found". Regarding the latest submitted code suggestion; what is <yOur IP> supposed to be replaced with? The victim is in most situations a "black box" when it comes to knowledge about
  8. This won't give you all possible hosts, just the ones answering to ping, -Pn is needed imo, otherwise you miss some hosts that are out there, but do not tell they are because they are configured in that way. -sV... won't that just add to the time needed to scan? is it important to determine service/version info of the port? I would rather do that in a "second stage" if important and most likely on specific hosts -F is that really relevant when the port is specified?
  9. My guess is that this isn't really C2 related, it's about how the Pi handles IPv6 (it affects other services and daemons the same way). In what way have you tried to disable IPv6 in sysctl and grub?
  10. The shop text contains "Supports massive storage options from the MicroSD card reader hidden inside" and a picture of the Turtle where the SD card slot is in plain view.
  11. What kind of wireless network is your Google Home device on? 5 GHz? If so, you won't get any handshake with the Pineapple unless you have a 5 GHz NIC attached. But, I guess it's on 2.4 GHz since you say "i often don't get" (meaning you get it at least sometime). Handshakes aren't always like ordering from the McDonald's menu, i.e. a deauth won't automagically be equal to obtaining the handshake. Sometimes you can deauth like crazy and still not get it (deauthing too aggressive isn't a good thing either). An alternative less aggressive is to just sit and wait. The handshake will perhaps show up
  12. Correct, trying to connect a client that has previously connected to a secured network, to a network with the same SSID that is open/unprotected will keep you waiting for a long while (like... forever...)
  13. How far are you from the WiFi network that you are trying "mimic"? Are you sure that the clients aren't just reconnecting to the intended network (and not your spoofed one)? What kind of WiFi network are you trying to "mimic"? A PSK protected one?
  14. Look at the "PineAP Basics" video https://docs.hak5.org/hc/en-us/categories/360004116253-WiFi-Pineapple-Mark-VII PineAP main tab > PineAP Settings section > Advanced tab > Allow Associations or use the Active mode
  15. Are the filters set up properly? Associations allowed?
×
×
  • Create New...