Jump to content

chrizree

Active Members
  • Content Count

    402
  • Joined

  • Last visited

  • Days Won

    21

7 Followers

About chrizree

  • Rank
    Hak5 Pirate

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. How long did you wait? It takes a while to get the logs loaded if you have had the C2 instance running for some time.
  2. The only mistake I can spot is the fact that ppl get their traffic sniffed without them allowing it to happen. Other than that... there is no mistake. The module works as intended. The question to ask is: "How many ppl are using web services in 2021 that is based only on http?" My answer is, "not many" and probably the reason why nothing gets caught in the net.
  3. lol, spitting in the face of the forum members won't help your situation, not a very wise strategy... I'm opting out...
  4. it's nothing I will spend any time on either, I'm perfectly OK with using an ordinary text editor and the official tools in order to create ducky payload scripts and encoded files
  5. What language is your "victim" using and what language have you specified when creating the inject.bin file? What's the result if you use the payload ducky code and encode it with an official tool, same thing?
  6. It seems as if you have done the vital steps. The network interface that should be shared is not the Mk7 one, but it seems as if you've gotten that correct. When you say "i changed the MK7 ip to 172.16.42.42 subnet mask to 255.255.255.0", I guess you mean the Mk7 network interface on the Windows PC, not on the Mk7 itself.
  7. Then you have the incentive and driving force to start developing those modules, exactly what is needed to push community driven module development, if there's a need somewhere, there's need for a "product" (module), those that do not have this need won't put time in it though, so someone out there must take the lead if they want it to happen
  8. I have several modules installed at the same time, so it should be no problem. Not sure what you might have messed up (if it was you at all), but if I would get stuck in such a situation, I would most likely do a firmware recovery and start over fresh.
  9. Do you have problems to get the Ducky to hit F12 in that specific scenario or to get it to hit F12 at all? Have you tried to use the "JS Ducky Encoder" (non Java) along with the language files for the Bash Bunny (F12 is specified in those language files)? https://downloads.hak5.org/ducky https://github.com/hak5/bashbunny-payloads/tree/master/languages
  10. That sounds odd, I'm writing this connected to my Nano that is connected to an AP using an RT5370 USB NIC (as wlan2). What Nano firmware are you on? Shouldn't matter really, but it's a good thing to at least be running the latest fw. What VID/PID does that 5370 NIC identify itself with?
  11. Have you tried to install Kismet on the Tetra?
  12. -E, yes, but not -e and with -E you should use an ESSID, i.e. an AP name, not a MAC address Look at this thread on how to "upgrade" mdk4 on the Mk7, it may help https://forums.hak5.org/topic/54576-mdk4-on-mark-vii-from-terminal/
  13. -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
  14. BSSID isn't -e, is it?! For attack mode "d" it should be -B. What version of mdk4 are you running?
  15. 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
×
×
  • Create New...