TryHackMe | OhSINT

Another box down on TryHackMe! Now admittedly, this is a much more beginner-oriented box, but it is a great introduction to OSINT (Open-Source Intelligence). There were some cool challenges, but some of it I find out a little funky/cheesy (like the final question). But overall, it was a fun experience.

It starts off by giving us an image to download. So, unless the message is directly hidden in the picture itself, the next step would be to take a look at the EXIF/XMP info that is stored on this image. This can include info like the type of camera used to take the photo, the geo-location, the name of the author, and much more!

So what you end up needing to do, is you can either use your computer to use this data, or some type of tool that can display this EXIF/XMP data for us.

In the copyright for the photo, we can see the name “OWoodflint”. Since there isn’t much else popping out right now, let’s just plug it into Google.

And the top three results are exactly what we are looking for! I just pulled them all up right away to take a quick scan over them.

On his Twitter page we can see that the profile picture is of a cat, so that answers our first question. The next question is to see what city they live in.

Scrolling through the Twitter page, there is a BSSID for a network there. Since he mentions that his house is near this network and that he can access it, if we can find where this network is, we can find his rough location.

Online there are lots of different ways and tools to do this, but I chose Wiggle to check and see if it was recorded in their database. Wiggle is a war-driving program. When people are on the go, they can turn on Wiggle, and it will scan all of the WiFi networks around them, and upload the data that they grab to this service. By inputting his BSSID, I was able to track down the city that he was located in, along with the info for the next question, which was regarding what the SSID of the WAP he was connected to is.

Our next quest is to find his email address. We’ve bled his twitter page pretty dry, so let’s take a look at his GitHub page.

There you have it! Easy enough to find. This info answers the next question as well. Now we are going to attempt to find out where he went on Holiday. Since there is no other info on the GitHub page, we are going to go to the last resource we have; his WordPress site.

Aaaaaaaand it says it right there on the front page, easy-peasy. The final question was a little rougher, because so far in my exploration, I haven’t found this to be a useful thing to do when doing OSINT challenges, but it is included in here. It is to find his password.

This is why I thought it was a bit cheesy. Most of the time, you probably will not run into situations where the user has their password publicly posted, just slightly hidden/white text on a white background. Taking a look at the HTML we see:

That it is just a new paragraph on the post, the text has no color, and is just sitting there. Normally, we might be looking more towards password dumps/breaches to find old passwords for people, but I guess this works too!

Overall, a great beginner box, and a great one to do when you only have a little bit of time and still want some fun.

TryHackMe | Blue

So recently I started to try my hand at vulnerable boxes, and some of my friends recommended a website called “TryHackMe” because it’s a little nicer to beginners than some VulnHub/HackTheBox boxes are, so I decided to go for it! Here is a short overview of my journey exploiting this box.

If you have any questions, feel free to leave a comment. Some of my answers/explanations may not match up to the answers I gave on TryHackMe, and that is just because they expected a very linear approach and I accidentally went off and used an exploit that did basically the same thing, just in a different way.

So our first task is to scan the machine. TryHackMe gives you an IP, so I booted up Kali, started using ZenMap (yeah I know, I’m a pleb), and hit the machine with an intense scan. The only reason I started with the intense scan is because this is just a box challenge, a normal scenario would require a bit more finesse.

And as you can see outlined in red, I was able to find the three ports that are open that were under 1000.

So, since this box is based off of EternalBlue, and there is an nmap scan specifically for these vulnerabilities, I created a new custom ZenMap profile and did a custom scan looking for these vulnerabilities, plus a few other things.

Now, you can see that this box is definitely vulnerable to the vulnerabilities we were looking for.

In this pic, you can see what options are available in Metasploit to use to get into this box. I would recommend attempting this exploit in any other way than using Metasploit (just for the sake of experience), or at the very least, find a small script yourself (like a python one), study the script a bit, and then use it to exploit the box. The only reason I didn’t, was because I was racing a friend on this box.

Also, you’ll see that I set all of the options for Metasploit to exploit the box successfully.

Hitting “run”, and we’ve got a successful session on the machine, we will want to background this session, just to check a couple other things out real quick.

Running ifconfig, it comes back successfully identifying that we are on the machine now.

getsystem also identifies that we have Admin as well.

Starting a shell, and running whoami, shows that kind of system we are on, and what authority we have.

And we migrated our session to a different service ID on the system successfully. During this though, our process may or may not die, so we might need to restart it!

The three main reasons for migrating the process is:

  1. You have an unstable shell and might need to move to a more “robust” process.
  2. Some exploits require an interactive session (AKA not session 0).
  3. You need to migrate from a 32-bit process to a 64-bit operating system.

You can read more about process migration here.

Using hashdump, we can see that there are three users on the computer. We want into the “Jon” user account though, so we are going to grab that hash and try to crack it.

Luckily, the hash itself is pretty easy to crack using an online database, and we get the password, which is “alqfna22”.

And just as a side note, sites like crackstation don’t usually actively crack hashes for you. They just match the hash up to a preexisting one in their database and give you the result. So it’s a quick and easy way to do it if you don’t feel like actually going through the cracking process, and sometimes you get lucky and find matches.

Now we are on the hunt for flags. Using search search -f flag*.txt we were able to find all of the text files with the word “flag” on the box. The asterisk at the end before “.txt” is a wildcard, which is why flag1, flag2, and flag3 all showed up. All that’s really left is to traverse to those parts of the directory and see what’s inside those files.

This box was a great experience for a beginner like me, and I had a ton of fun working on it! It took me just barely under an hour, and was very short but sweet, and has encouraged me to continue to try out more boxes.

Thanks for giving this a read!