Active Members
  • Content count

  • Joined

  • Last visited

  • Days Won


About 3mrgnc3

  • Rank
    Hak5 Fan ++

Profile Information

  • Gender
  • Location
    The Untidied Kingdoms
  • Interests
    Electro Magnetism
    Emergent Phenomena
    Cognitive Dissonance
    Acoustic Guitar
    Coke Zero
    & Tropical Fruits

Recent Profile Visitors

1,371 profile views
  1. I think you are confused Ekber48 The Lan Turtle won't automatically hack into computers on the same lan. Rather, in the configuration you suggest, it gives you a foothold on the lan. Then from there you are able to conduct furter recon/spoofing/sniffing/mitm activity. The Lan Turtle can be used to attack a host directly via its usb in various ways but that requires a diferent use case from what you described. if you connect the turtle to any device via the RJ45/ethernet port, the network/computer/server (whatever you wish to call it) needs to assign an IP address to the turtle because it will request one via its dhcp client. It is possible to statically assign the ip beforehand if you know the target subnet is and what addresses are available. but that could cause problems.
  2. Hi digip, I sent you a DM on twitter mate. I messed up the clue for that flag. I've sent you a correction and will be updating the ova and my blog shortly today. As a point of note. The flags are not needed in order to root this box. They are really just designed as a parallel challenge to tackle. I have made some of the flags very tricky to find. Cheers.
  3. Still no walkthroughs submitted as of yet. If anyone has done one, please either tweet it to @3mrgnc3 or email me at 3mrgnc3@techie.com.
  4. That's a shame. Are you attacking from a VM with limited resources? What browser are you using? Going through the code will obviously work too though.
  5. Nice job :D ;D
  6. Nice :D Glad you like it digip.
  7. New VM just sent in... to Vulnhub.com but here is a link for anyone who is into all that and wants to try it out now. D0Not5top Boot2Root This is my second public Boot2Root, It’s intended to be a little more difficult that the last one I made. That being said, it will depend on you how hard it is :D It's filled with a few little things to make the player smile. Again there are a few “Red Herrings”, and enumeration is key. DIFFICULTY ????? CAPTURE THE FLAGS There are 7 flags to collect, designed to get progressively more difficult to obtain DETAILS File: D0Not5top_3mrgnc3_v1.0.ova OS: ????? VM Type: VirtualBox IP Address: DHCP Size: 700 MB DOWNLOAD https://3mrgnc3.ninja/files/D0Not5top_3mrgnc3_v1.0.ova SUPPORT Any support issues can be directed to 3mrgnc3@techie.com SCREENSHOT I hope you all enjoy it! 3mrgnc3 ;D P.s. my previous challenge can be found here. https://3mrgnc3.ninja/2016/12/64base/ ------------------------------------------- NOTE: I Origionally posted this in 'everything else' forum but wanted to move it here. Not sure how to do that... Mods please feel free to remove origional.
  8. Cheers :D
  9. themes

    Very nice job... I was gonna have a go at this one but got distracted with work and other stuff. Very cool theme.
  10. There is a project I found on github that is a fail2ban style solution for opewrt that would probably work on the pineapple https://github.com/robzr/bearDropper Edit: lol just saw this was the same as suggested above too :D However, the issue with fail2ban's blacklisting style solution to the problem is that it ends up appending hundreds and hundreds of IP addresses to an iptables rule list. Then this has to be loaded/parsed/compared whenever connection attempts are made. This could give a significant performance hit to you little old pineapple. The simplest and least CPU intensive solution to the problem is to switch ssh to a high port (eg. 61222) AND use RSA key authentication, STRICTLY disallowing password auth in your config. Then (as just_a_user alluded to) WHITELIST you own IP addresses using iptables. The ssh BOT/BOTS that are trying to brute you tend only to focus on port 22, and if they are smart enough to detect password auth is dsabled will give up quickly. But in 99.9% of cases I would put money on the problem going away if your using a non standard high port number for ssh. Hope this helps.
  11. lol, Oh Yeah , Forgot about that when thinking about what I saw on my VPS, cheers for posting and letting people know I was mistaken in suggesting those particular commands.
  12. I grep then use sed (No logs left in home dir)
  13. I don't know about the pineapple, as I don't leave any of mine connected to the internet for a long period of time. However, on the VPS I run my blog from I was seeing many connections 'ESTABLISHED' to port 22 in netstat output. After also looking at my auth.log files too I saw Chinese IP addresses attempting to brute force my ssh password (unlucky for them I disable passwords and only use rsa keys). Sadly, this is common behaviour now in this age of cyberwarfare. I changed my ssh port to a non-standard one and now I have no problems. Just so everyone is clear, a netstat connection 'ESTABLISHED' doesn't mean an ssh session has been 'AUTHENTICATED'. Check using the commands: 'w', 'last', & 'lastlog' Then you will see precisely who is/has connected to your server and when.
  14. Let Me Google That For You. http://bfy.tw/Anyb
  15. I googled it for you... Monitor Wi-Fi Client Probes In 10 Lines Of Python http://www.securitytube.net/video/7265 Or Just use airodump-ng with -w flag. Then you will have multiple file formats produced you can process/parse/filter/script against. Or wireshark capture on monitor interface. You can construct a capture or display filter to only show probes. google should have all the examples you need.