OhSINT
Overview — OhSINT is an Easy open-source-intelligence challenge. You receive a single image and nothing else; by reading its metadata, pivoting on the username found there, locating a Wi-Fi access point by its BSSID, and reading the persona's public code and blog pages, you reconstruct a fictional person's avatar, city, network name, email, holiday destination and a password hidden on a web page. It teaches the OSINT habit of turning one small artifact into the next lead. The persona is fictional and belongs to the room, so only the method is described here.
| Platform | TryHackMe |
| Category | Offensive |
| Difficulty | Easy |
| Room | OhSINT |
Attack map
[Image file] exiftool
| Copyright field = a username (alias)
v
[Alias search] search engine pivots -> social account, code-hosting profile, blog
| social profile picture -> avatar question
| a post containing a BSSID -> Wi-Fi geolocation (Wigle)
v
[Wigle.net] BSSID lookup -> city + SSID of the access point
| code-hosting repository -> email address
v
[Blog] travel post -> holiday destination ; select-all reveals white-on-white text -> password
Task 1 — Metadata and the user's avatar
Image files carry more than pixels. EXIF and XMP blocks can store the camera model, timestamps, GPS coordinates and free-text fields such as author or copyright. When an image is published, those fields often go with it. The standard tool for inspecting them is exiftool:
exiftool WindowsXP.jpg
Among the usual file attributes (type, size, dimensions) two groups of fields stand out:
- GPS Latitude / Longitude — coordinates embedded in the image. They are a lead, but not the answer to the room's city question, which is solved through the Wi-Fi route below.
- Copyright — a free-text field that holds a handle (
OWoodflint). People tend to reuse the same handle across services, so this string is the pivot for everything that follows.
Searching the handle in a general search engine returns several profiles: a social microblog account, a code-hosting profile and a WordPress blog. Always confirm a hit belongs to the same person (matching name, theme, links between profiles) before trusting it; here the accounts reference each other. The social account's profile picture shows the answer to the first question.
Q: What is this user's avatar of?
A: cat
Task 2 — Geolocating the Wi-Fi network
A post on the persona's social account says they can get free Wi-Fi from home and publishes the access point's BSSID. The BSSID is the MAC address of the access point's radio, and it is globally unique per device. Crowdsourced wardriving databases such as Wigle.net map BSSIDs to coordinates and store the network name (SSID) seen at that location.
The procedure:
- Create a free Wigle account and sign in.
- Open the Basic Search under the View menu and enter the BSSID from the post.
- The map may not centre on the result; zoom out, re-centre and zoom back in on the marker.
- Read the matching entry: its position tells you the city, and the entry itself lists the SSID of the access point. If several rows appear, the one for the exact BSSID is the one you want.
Q: What city is this person in?
A: the city the Wigle marker for that BSSID falls in (read it from the map)
Q: What is the SSID of the WAP he connected to?
A: the network name listed in the Wigle entry for that BSSID
This is why publishing a BSSID is risky: it turns a home router into a precise location beacon, no GPS needed.
Task 3 — Email address from a code repository
The handle also matches a profile on a code-hosting site, with a repository that looks unremarkable. Public repositories frequently leak contact details: the README, the profile bio, or the author metadata in commits. In this room the persona's email address is shown in that repository.
Q: What is his personal email address?
A: the address displayed in the persona's repository on the code-hosting site
Q: What site did you find his email address on?
A: the code-hosting site (GitHub)
Developers who reuse a personal email for commits expose it permanently, since git history is public and cannot be edited away once cloned. Using the host's noreply address avoids that.
Task 4 — The blog and the hidden password
The WordPress blog has a travel post written when the persona set off on holiday. Reading it answers the destination question directly.
Q: Where has he gone on holiday?
A: the destination named in the blog's travel post
The final question asks for a password. Nothing visible on the page looks like one, which is the hint: text can be hidden simply by colouring it the same as the background. Pressing Ctrl + A highlights every text node on the page, including white-on-white text, which then becomes legible against the selection colour. Viewing the page source or disabling CSS in the browser's developer tools gives the same result.
Q: What is this persons password?
A: the string revealed by selecting all text on the blog post
Quick reference
| Technique / tool | What it gives you | Where it appears |
|---|---|---|
| exiftool | Metadata such as the Copyright handle and GPS fields | Task 1 |
| Handle search | Links the social account, code-hosting profile and blog | Task 1 |
| Wigle.net BSSID lookup | City and SSID of the access point | Task 2 |
| Public repository | Leaked personal email address | Task 3 |
| Blog travel post | Holiday destination | Task 4 |
| Select All (Ctrl + A) | Reveals text hidden by matching the background colour | Task 4 |
Key takeaways
- Start every image-based OSINT task with
exiftool: author, copyright and GPS fields can hand you the first pivot for free. - A single handle searched across platforms links accounts; verify matches before treating them as the same person.
- BSSIDs can be geolocated with Wigle-style wardriving databases, so sharing a router's MAC address publicly reveals where you live.
- Repositories, commit history and blogs leak emails and hobbies; hidden page text (same-colour fonts, HTML comments) is worth checking with Select All or View Source.
- Defensively: strip metadata before publishing images, avoid reusing handles, never post network identifiers, and never keep credentials in page content, hidden or not.
- Document every pivot as you go; OSINT findings are only as strong as the chain that links them.