<?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 00 00 00 00  on Medium]]></title>
        <description><![CDATA[Stories by 00 00 00 00  on Medium]]></description>
        <link>https://medium.com/@0x0s0u01?source=rss-f761860642da------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jp_HjjFTP-Mnzd-TmTwR5A.gif</url>
            <title>Stories by 00 00 00 00  on Medium</title>
            <link>https://medium.com/@0x0s0u01?source=rss-f761860642da------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:40:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@0x0s0u01/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[pico CTF series — 5 — Glory of the Garden]]></title>
            <link>https://medium.com/@0x0s0u01/pico-ctf-series-5-glory-of-the-garden-fee540df0a9c?source=rss-f761860642da------2</link>
            <guid isPermaLink="false">https://medium.com/p/fee540df0a9c</guid>
            <category><![CDATA[digital-forensics]]></category>
            <category><![CDATA[picoctf]]></category>
            <dc:creator><![CDATA[00 00 00 00 ]]></dc:creator>
            <pubDate>Sat, 02 Nov 2024 16:25:24 GMT</pubDate>
            <atom:updated>2024-11-02T16:25:24.127Z</atom:updated>
            <content:encoded><![CDATA[<h3>pico CTF series — 5 — Glory of the Garden</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*oJk153Jl_5sBhk9j5-neww.jpeg" /><figcaption>alas, the final</figcaption></figure><p>And the final challenge from the easy difficulty.</p><p><strong>Category:</strong> Forensics</p><p><strong>Difficulty:</strong> Easy</p><p><strong>Date:</strong> 16/10/2024</p><p><strong>Time:</strong> 21:39 PM</p><h3>Description</h3><p>This <a href="https://jupiter.challenges.picoctf.org/static/4153422e18d40363e7ffc7e15a108683/garden.jpg">garden</a> contains more than it seems.</p><p>Similar to our previous challenges, we check for strings.</p><p>Let’s “cat” out the contents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*ms5FUEiYP0WSabQrqsM3nw.png" /></figure><p>Binary.</p><p>Let’s move on with “more”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*1lTZ49LOpvSnzJ77KpkqpQ.png" /></figure><p>Binary here as well.</p><p>Did we hit a wall?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/165/1*mXIcK5pln4iAQMl6LXcDXA.gif" /><figcaption>My face when</figcaption></figure><p>No my friend.</p><p>There’s another command that we can use.</p><p>It’s called “strings”.</p><p>I know, I know, I am a wizard.</p><p>Let’s use it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*sLc1q8MTptqU3Z2UbG6oFQ.png" /></figure><p>And there it is.</p><p>Our flag.</p><h3>Note</h3><p>With this, concludes our set of easy challenges in the Forensics category.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*PlVManEZxxnwwHwwg5TiZg.png" /></figure><p>What a run huh?</p><p>Well, time to move on to the next difficulty.</p><p>Medium.</p><p>I hope everyone enjoyed this first round of writeups :D.</p><p>Still working on a standard, so please bear with me on that.</p><p>If anything, please provide feedback, I really appreciate it.</p><p><strong>Date:</strong> 16/10/2024</p><p><strong>Time:</strong> 21:55 PM</p><p><strong>Difficulty:</strong> Easy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fee540df0a9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[pico CTF Series — 4 — Information]]></title>
            <link>https://medium.com/@0x0s0u01/pico-ctf-series-4-information-a66bfb53cc4d?source=rss-f761860642da------2</link>
            <guid isPermaLink="false">https://medium.com/p/a66bfb53cc4d</guid>
            <category><![CDATA[picoctf]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <dc:creator><![CDATA[00 00 00 00 ]]></dc:creator>
            <pubDate>Sat, 02 Nov 2024 16:11:49 GMT</pubDate>
            <atom:updated>2024-11-02T16:11:49.156Z</atom:updated>
            <content:encoded><![CDATA[<h3>pico CTF Series — 4 — Information</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*oJk153Jl_5sBhk9j5-neww.jpeg" /><figcaption>car</figcaption></figure><p><strong>Category:</strong> Forensics</p><p><strong>Difficulty:</strong> Easy</p><p><strong>Date:</strong> 15/10/2024</p><p><strong>Time:</strong> 17:10 PM</p><h3>Description</h3><p>Files can always be changed in a secret way. Can you find the flag?</p><p>Before anything, let’s acknowledge the fact that the picture used for this challenge goes fucking hard.</p><p>Downloading the file, we get a “.jpg”.</p><p>Now let’s admire the picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LS7krFmos7VEYKQNxNoXKQ.png" /></figure><p>This goes hard ngl.</p><p>Now, back to work.</p><p>In the image, there’s nothing.</p><p>SO, we have to check for strings again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ca5ZEWYqoEMyFI5Pr75Jrw.png" /></figure><p>Binary data..</p><p>Let’s use “more”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*88EaUDdkjBY76CjUXP2ghA.png" /></figure><p>Bingo!</p><p>We have another base64 encoded string.</p><p>Again, since I am lazy, we’re gonna use Cyberchef — again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*b8eMhlV_sPoIvF2R4xVkOQ.png" /></figure><p>And we get our flag.</p><p>Indeed the metadata was modified.</p><h3>Note</h3><p>Yes, the previous challenges could’ve been solved by using “exiftool” which is a tool — given by the name, that checks for the metadata and displays it.</p><p>But I wanted to push myself, trying not to use any external tools when possible.</p><p>But after we finish the easy challenges and get on to much harder ones, we’d have to use our big man toys.</p><p><strong>Date:</strong> 15/10/2024</p><p><strong>Time:</strong> 17:23 PM</p><p><strong>Difficulty:</strong> Easy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a66bfb53cc4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[pico CTF Series — 3 — CanYouSee]]></title>
            <link>https://medium.com/@0x0s0u01/pico-ctf-series-3-canyousee-297650f1d754?source=rss-f761860642da------2</link>
            <guid isPermaLink="false">https://medium.com/p/297650f1d754</guid>
            <category><![CDATA[digital-forensics]]></category>
            <category><![CDATA[picoctf]]></category>
            <dc:creator><![CDATA[00 00 00 00 ]]></dc:creator>
            <pubDate>Sat, 02 Nov 2024 15:57:05 GMT</pubDate>
            <atom:updated>2024-11-02T15:57:05.629Z</atom:updated>
            <content:encoded><![CDATA[<h3>pico CTF Series — 3 — CanYouSee</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*oJk153Jl_5sBhk9j5-neww.jpeg" /><figcaption>i can’t see</figcaption></figure><p><strong>Category:</strong> Forensics</p><p><strong>Difficulty:</strong> Easy</p><p><strong>Date:</strong> 15/10/2024</p><p><strong>Time:</strong> 16:32 PM</p><h3>Description</h3><p>How about some hide and seek?</p><p>We download the file, and we get an archive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/108/1*9r6u4aSlxzJusX36a1uhIA.png" /></figure><p>We extract it, and we get our image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/127/1*O5ObKGfe5tcUAH44qr6H6g.png" /></figure><p>If we remember from our last challenge, let’s see what we can find about this image, by searching through it’s strings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RUBulV1iFUbJHV6pbQYnTw.png" /></figure><p>Not much, only binary data.</p><p>Now what?</p><p>Well, we’ve only used one way to check for strings.</p><p>What we did now, we just “cat” out the file content, by using the command “cat”.</p><p>Let’s use the command “more” to see what we get.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vMGoZ767DB-fsPFvAH8bsg.png" /></figure><p>Oop — there’s something.</p><p>Some metadata info.</p><p>Can you see something that sticks out?</p><p>…</p><p>Bingo.</p><p>There’s a weird string made of combined letters and numbers in quotes.</p><p>Not the first one, the second one.</p><p>It seems to be base64 enconded.</p><p>So, that means, we have to decode it.</p><p>But, I am lazy as usual, so we’re gonna google a tool to decode it.</p><p>Im using Cyberchef — a good resource.</p><p>AND BOOM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/1*mSokL0dF-rrihVCmc5pmFQ.png" /></figure><p>Our flag.</p><p>A very easy and another interesting challenge nonetheless.</p><p><strong>Date:</strong> 15/10/2024</p><p><strong>Time:</strong> 16:40 PM</p><p><strong>Difficulty:</strong> Easy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=297650f1d754" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[pico CTF Series — 2 — Secret of the Polyglot]]></title>
            <link>https://medium.com/@0x0s0u01/pico-ctf-series-2-secret-of-the-polyglot-59f286c52b70?source=rss-f761860642da------2</link>
            <guid isPermaLink="false">https://medium.com/p/59f286c52b70</guid>
            <category><![CDATA[picoctf]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <dc:creator><![CDATA[00 00 00 00 ]]></dc:creator>
            <pubDate>Thu, 31 Oct 2024 17:27:06 GMT</pubDate>
            <atom:updated>2024-10-31T17:27:39.458Z</atom:updated>
            <content:encoded><![CDATA[<h3>pico CTF Series — 2 — Secret of the Polyglot</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*oJk153Jl_5sBhk9j5-neww.jpeg" /><figcaption>we go crazy</figcaption></figure><p>This one is an interesting challenge.</p><p><strong>Category:</strong> Forensics</p><p><strong>Difficulty:</strong> Easy</p><p><strong>Date:</strong> 15/10/2024</p><p><strong>Time:</strong> 16:01 PM</p><h3>Description</h3><p>The Network Operations Center (NOC) of your local institution picked up a suspicious file, they’re getting conflicting information on what type of file it is. They’ve brought you in as an external expert to examine the file. Can you extract all the information from this strange file?</p><p>By downloading the file, we have a “.pdf” file called “flag2of2-final”.</p><p>By opening it, we get our last part of the flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*9WYWT1T06zCiwt77Ue-dzA.png" /><figcaption>do you see a hint in the flag?</figcaption></figure><p>Question: do you see a hint in the flag?</p><p>I will wait…</p><p>Bingo! Yes, “pn9_&amp;_pdf” — sounds weird right?</p><p>Something “pn” and “pdf”?</p><p>What could the first part mean — OH!</p><p>Could mean “png_&amp;_pdf”.</p><p>Meaning, this file has a hidden extension.</p><p>But how do we check if it truly has a hidden extension?</p><p>Well, we’re checking for strings inside the file to see anything related to a “.png” format.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FJAw2Pp9MhyPOUAQkPqe-g.png" /></figure><p>We see some “.pdf” format things, let’s scroll up and see…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wGCPW9Or6Y8JPKrr2wGkzA.png" /></figure><p>Oh?</p><p>We see some weird data.</p><p>Can you see something in particular?</p><p>No?</p><p>The screenshot is too blurry?</p><p>No worries, here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*9iCXynlanbqz_soysukVhw.png" /></figure><p>This could mean, that there’s actually an image.</p><p>Let’s look more and see something that has more certain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/1*Gbb3TsAhFe4WajQB95TFaA.png" /></figure><p>Bingo.</p><p>But also this was obviously obvious lmao.</p><p>This means, there’s actually a hidden extension, and that extension is a “.png”.</p><p>Now, how are we gonna access it?</p><p>Well… by changing the extension.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/109/1*QHhpOf_1oysubpAEXu_-ow.png" /></figure><p>But nothing happened?</p><p>The thumbnail still remains as being a “.pdf” file.</p><p>Well, now you’re gonna see literal magic.</p><p>Let’s open it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/1*MtW_dTqtDhLn9slooCIi8A.png" /><figcaption>IMAGEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE</figcaption></figure><p>BEHOLD!!</p><p>An image.</p><p>A small one, but it’s an image indeed.</p><p>And there’s our first part of the flag.</p><p>Now let’s assemble our flag.</p><p>We combine our parts, and we get : “picoCTF{f1u3n7_1n_pn9_&amp;_pdf_2a6a1ea8}”.</p><p>A very interesting challenge.</p><h3>Note</h3><p>So the idea around this, given even from the title of the challenge, ironically it’s not a polyglot, more like a bilingual if anything lol.</p><p>Semantics aside, it revolves around Steganography.</p><p>What is Steganography?</p><p>In layman’s terms, a word ( and a “world” around this topic - because why not ) where it describes a whole set of techniques for hiding a message in plain sight.</p><p>In our case, a 2 part message, one part hidden in a “.png” format in a “.pdf” file that has the last part of the message.</p><p>The way it was hidden, it’s very technical, since it’s our of scope for this post.</p><p>I will add on to my “ideas for later” tab.</p><p>And the previous challenges that I did, revolved around in a way, steganography.</p><p><strong>Date:</strong> 15/10/2024</p><p><strong>Time:</strong> 16:25 PM</p><p><strong>Difficulty:</strong> Easy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59f286c52b70" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[pico CTF Series — 1 — Scan Surprise]]></title>
            <link>https://medium.com/@0x0s0u01/pico-ctf-series-1-scan-surprise-19dfe472bdaf?source=rss-f761860642da------2</link>
            <guid isPermaLink="false">https://medium.com/p/19dfe472bdaf</guid>
            <category><![CDATA[picoctf]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <dc:creator><![CDATA[00 00 00 00 ]]></dc:creator>
            <pubDate>Thu, 31 Oct 2024 17:06:10 GMT</pubDate>
            <atom:updated>2024-10-31T17:06:10.608Z</atom:updated>
            <content:encoded><![CDATA[<h3>pico CTF Series — 1 — Scan Surprise</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*oJk153Jl_5sBhk9j5-neww.jpeg" /><figcaption>speak no evil</figcaption></figure><p>Back to BACK, I’m getting more active.</p><p><strong>Category:</strong> Forensics</p><p><strong>Difficulty:</strong> Easy</p><p><strong>Date:</strong> 12/10/2024</p><p><strong>Time: </strong>19:48 PM</p><h3>Description</h3><p>I’ve gotten bored of handing out flags as text. Wouldn’t it be cool if they were an image instead?</p><p>Since it’s an image, we can download it directly and see what are the contents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*jYUEnYgzWmHsSn4VCX46_w.png" /></figure><p>As we can see, it’s a QR code.</p><p>We can with ease scan it using an online tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*A1by-3xmB5jbt-WvRQ23zw.png" /></figure><p>I used this weird one that I found from google.</p><p>And we got our flag.</p><p>Another easy one indeed.</p><h3>Additional Info</h3><p>For this challenge, if you were going to solve via the browser instance, or you don’t want to use any in-browser online tools, you’d have to use “zbar-tools” in order to convert the image into the string.</p><p><strong>Date:</strong> 12/10/2024</p><p><strong>Time:</strong> 19:50 PM</p><p><strong>Difficulty:</strong> Easy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19dfe472bdaf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[pico CTF Series — 0 — Verify]]></title>
            <link>https://medium.com/@0x0s0u01/pico-ctf-series-0-verify-0f0286e2e80c?source=rss-f761860642da------2</link>
            <guid isPermaLink="false">https://medium.com/p/0f0286e2e80c</guid>
            <category><![CDATA[digital-forensics]]></category>
            <category><![CDATA[picoctf]]></category>
            <dc:creator><![CDATA[00 00 00 00 ]]></dc:creator>
            <pubDate>Thu, 31 Oct 2024 16:56:03 GMT</pubDate>
            <atom:updated>2024-10-31T16:56:03.219Z</atom:updated>
            <content:encoded><![CDATA[<h3>pico CTF Series — 0 — Verify</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*oJk153Jl_5sBhk9j5-neww.jpeg" /><figcaption>what the dawg doing?</figcaption></figure><p>Yeah uhhh, everyone remember about what I said about me going on a crazy marathon on HTB?</p><p>Me neither ( I discovered that pico had more fun challenges, bored to do only endpoint forensics — the interesting ones are at the hard or insane difficulty there, and sadly there’s only few of those ), so let’s get to work, shall we?</p><p><strong>Category: </strong>Forensics</p><p><strong>Difficulty: </strong>Easy</p><p><strong>Date: </strong>12/10/2024</p><p><strong>Time: </strong>19:32 PM</p><h3>Description</h3><p>People keep trying to trick my players with imitation flags. I want to make sure they get the real thing! I’m going to provide the SHA-256 hash and a decrypt script to help you know that my flags are legitimate.</p><p>SSH-ing into the instance, we get 2 files and one directory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*CTTdVY_J5bIAQm7lprJLpg.png" /></figure><p>A “checksum.txt”; “decrypt.sh” and a folder called “files”.</p><p>Let’s check the contents of “checksum.txt”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*uhBuCO0a9CvD1eactqgmRw.png" /></figure><p>From the challenge description, indeed it is the SHA-256 provided.</p><p>We have the <em>decryptor</em>,<em> </em>now we need to find the file.</p><p>Let’s check first what’s inside the “files” folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*qlTUusT3c1FOLl0GXUeuzg.png" /></figure><p>We have a LOT of files.</p><p>Then let’s do a checksum and grep the associated file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/729/1*MOmEUSSVSISpinN20IgiVA.png" /></figure><p>We found our file.</p><p>Let’s check what type of file it is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*54VRw4Qwp_Md_Q-TTgAwew.png" /></figure><p>So indeed it is our needed file to decrypt.</p><p>Let’s run the <em>decryptor </em>to get our flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/1*oGei-hkUBiqYyUfn22peRw.png" /></figure><p>And that’s it.</p><p>A very easy challenge nonetheless.</p><p><strong>Date: </strong>12/10/2024</p><p><strong>Time: </strong>19:43 PM</p><p><strong>Difficulty:</strong> Easy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0f0286e2e80c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sherlocks Series — 0 Reaper]]></title>
            <link>https://medium.com/@0x0s0u01/sherlocks-series-0-reaper-ab558dfd68e4?source=rss-f761860642da------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab558dfd68e4</guid>
            <category><![CDATA[hackthebox]]></category>
            <category><![CDATA[dfir]]></category>
            <category><![CDATA[hackthebox-writeup]]></category>
            <category><![CDATA[network-forensics]]></category>
            <category><![CDATA[ad-forensics]]></category>
            <dc:creator><![CDATA[00 00 00 00 ]]></dc:creator>
            <pubDate>Mon, 09 Sep 2024 21:37:05 GMT</pubDate>
            <atom:updated>2024-09-09T21:37:05.278Z</atom:updated>
            <content:encoded><![CDATA[<h3>Sherlocks Series — 0 Reaper</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zQH-3MIm_5Atp6cvNS3AEw.png" /></figure><p>Some notes before; uhhh, I mostly have no idea on how i should format it, but, I will see throughout the series if I ever achieve a good format.</p><p>Till then, I hope that everyone can bear with me on this endevour, if anything, I am open to feedback, if there are any errors, or issues in comprehension, don’t hesitate to comment, as always.</p><p>Name: Reaper</p><p>Difficulty: Very Easy</p><p>Category: DFIR</p><p>Time: 22:16 PM</p><p>Date: 22.08.2024</p><h3><strong>Scenario</strong></h3><p>Our SIEM alerted us to a suspicious logon event which needs to be looked at immediately . The alert details were that the IP Address and the Source Workstation name were a mismatch. You are provided a network capture and event logs from the surrounding time around the incident timeframe. Corelate the given evidence and report back to your SOC Manager.</p><h3><strong>Files</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DJB_Z0uavhPjuub6dug_AQ.png" /><figcaption>Reaper.zip archive</figcaption></figure><p>Password: hacktheblue</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/263/1*8bF-2dpduyVTx7T8IcQ81w.png" /><figcaption>One packet-capture log and one event log.</figcaption></figure><h3><strong>Additional Info</strong></h3><p>NTLM Relay Attacks; AD Forensics; MITM Attack Detection; Network Forensics.</p><p>It’s gametime.</p><blockquote><strong>1. What is the IP Address for Forela-Wkstn001?</strong></blockquote><p>Checking through “ntlmrelay.pcapng”, we see with ease the workstation name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KRI14KixGA93jbIkNFXjuA.png" /><figcaption>list of addresses??? dunno how to describe this.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Mz95arI_07FZxWOTGvAXg.png" /><figcaption>im not even gonna bother anymore.</figcaption></figure><p>So we apply a filter and see if there are any other IP addresses connected to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M7vBzensQOF9vM6GglfBEg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*SGf2jii5aUSMukMR74ajSA.png" /></figure><p>Scrolling through, we see 3 protocols and 4 IP addresses. This means we should hop on the logs to filter out the whitelisted addresses.</p><p>Protocols:</p><ul><li>DNS</li><li>TCP</li><li>NBNS</li></ul><p>IP Addresses:</p><ul><li>172.17.79.129</li><li>172.17.79.135</li><li>172.17.79.136</li><li>172.17.79.4</li></ul><p>We will have to match the events by time to figure out the bogus address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/859/1*ZbHw92PRlMxqC4ob23NUTA.png" /></figure><p>So, we start off with the first Logon event that happened at around 7:54 AM.</p><p>2 Addresses are seen in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BBi607rwE_S82mB1_n772g.png" /></figure><p>But since the other is from a DNS protocol, we discard it, and we remain with the IP address of 172.17.79.129.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jVwimaFhXTlnqi19RE7Gvg.png" /></figure><p>Which is the one.</p><blockquote><strong>2. What is the IP Address for Forela-Wkstn002?</strong></blockquote><p>We go back at the network log, and we check for the second connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FM1utyyo5vn2kSx-gEhdSw.png" /></figure><p>We see that for the second connection started at around 7:54, meaning at the same time with the first connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*9fBz7sqDWGQaTypjmClMpA.png" /></figure><p>So we see that the only address that connects to the second workstation is 172.17.79.136.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y2SjoraIEOlXLD_aitx2sA.png" /></figure><blockquote><strong>3. Which user account’s hash was stolen by attacker?</strong></blockquote><p>There is no hash, HTB fucked up with the question. I had to lookup on a write-up for a sanity check.</p><p>On the both network logs and event logs, there is no hash associated, only the username.</p><p>On the network log, I filtered by only having the “ntlmssp” and as for the event log, by any “Logon”, and checked for a weird connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ochKbkBvEsNQqrsRNGQgQA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VZsB59PXk67CL4VKDtsS1Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*xmcUr22E6l_ruDoIJwUFhg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aRvPuYXXGA63ckwf_F3iBA.png" /></figure><p>So yeah, when you think something is wrong, always check.</p><blockquote><strong>4. What is the IP Address of Unknown Device used by the attacker to intercept credentials?</strong></blockquote><p>We go back at the network log, we see an unknown IP address trying to connect .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WkCQS0zcFv9O2OZjC_aJqQ.png" /></figure><p>Meaning this is our bogus address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UZksj4MRtCfSyLODGbg6cg.png" /></figure><blockquote><strong>5. What was the fileshare navigated by the victim user account?</strong></blockquote><p>For ease of use, we go back at the network log, we clear out the filters, and we search by string for any “\\” filepath.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uO-Zig6tJHIzhYbKJL51-w.png" /></figure><p>By going through any results with the string, we see some attempts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wxEm9G_yd0Ez-unV8aPGUw.png" /></figure><p>With a response packet of “STATUS_BAD_NETWORK_NAME”, meaning that this is our hit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DSta0cqkn-WiMqaVDbb5ig.png" /></figure><blockquote><strong>6. What is the source port used to logon to target workstation using the compromised account?</strong></blockquote><p>We go back, at the event log, and go back at the bogus Logon event that has the username “arthur.kyle”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/1*r73xUxG3bV8NQ-s1mixp3Q.png" /></figure><p>As we see, we got our bogus address, and the port.</p><p>Which is our hit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/717/1*a03N8hXv4r1p5APNeAzPQQ.png" /></figure><blockquote><strong>7. What is the Logon ID for the malicious session?</strong></blockquote><p>We go back again at our event, and check for the Logon ID.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*fyisWuelXGUhnAPju5vHfw.png" /></figure><p>Which is 0x64a799.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tE2U5fdjpanIPG2n7uSXKA.png" /></figure><blockquote><strong>8. The detection was based on the mismatch of hostname and the assigned IP Address.What is the workstation name and the source IP Address from which the malicious logon occur?</strong></blockquote><p>We again ( yes, we do it again ) go back at out event, and check for the workstation name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*MK1Cjhq2AOHHuejcqpCT7Q.png" /></figure><p>We already know our bogus address, so we only have to add the workstation name and it’s done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d_R8Ay6wFCyhvW3BwPrgEg.png" /></figure><blockquote><strong>9. When did the malicious logon happened. Please make sure the timestamp is in UTC?</strong></blockquote><p>WE GO AGAIN ;-; , at out event log, this time we check XML view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*RH4pZmtyGijMUqBpVueLzg.png" /></figure><p>And search till you see “TimeCreated SystemTime”, and since HTB is case sensitive, we gotta type it manually.</p><p>Meaning like this “2024–07–31 04:55:16”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*SvoHWfid_ROMTwN0BfuWNw.png" /></figure><blockquote><strong>10. What is the share Name accessed as part of the authentication process by the malicious tool used by the attacker?</strong></blockquote><p>This is the last time we have to go back….</p><p>But this time at our event log, and check for the file share event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*r0yrkRrP_Sosc93dE04dAg.png" /></figure><p>And we again hop on XML view, and scroll till we see “ShareName”.</p><p>Thus concluding this box with our hit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cmyknrq_lH0jbtmgglm0Ew.png" /></figure><p>HOOOORAYYYYYYYYYYYYYYYYYYYYYY!!!!!!!!!!!!!!!!!!!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P-vsfoLeIEZSCV2ZsDHYCQ.png" /></figure><p>What we learned? Kinda nothing since I went blind without documenting myself on NTLM Relay Attacks and on MITM Attack Detection.</p><p>I went somewhat unorthodox, indeed I could’ve done a better job at filtering information by having a more complex and well-thought approach, but I like the challenge of going blind and act like a real “detective”.</p><p>Also, HTB SHOULD UPDATE THEIR BOXES, I wasted a few hours by going MENTAL on the third question, since there wasn’t A HASH.</p><p>And some question were weirdly put.</p><p>As one genius put it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/366/1*UxNL2hL6CxK0fE84Kr3MCg.png" /></figure><p>Name: Reaper</p><p>Difficulty: Very Easy</p><p>Category: DFIR</p><p>Time: 01:05 AM</p><p>Date: 23.08.2024</p><h3>Ending note</h3><p>I hope everyone enjoyed this weird write-up that I made.</p><p>Even tho it’s my first write-up, improvements could be made.</p><p>But I will improve throughout the series.</p><p>Again, I am open to feedback, if there are any errors, or issues in comprehension, don’t hesitate to comment, as always.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab558dfd68e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome]]></title>
            <link>https://medium.com/@0x0s0u01/welcome-6d950112e7df?source=rss-f761860642da------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d950112e7df</guid>
            <dc:creator><![CDATA[00 00 00 00 ]]></dc:creator>
            <pubDate>Wed, 21 Aug 2024 16:57:32 GMT</pubDate>
            <atom:updated>2024-08-21T16:58:32.475Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/549/1*5nhlNl86pN_K5f8LyaoSLQ.jpeg" /><figcaption>real</figcaption></figure><p>Welcome again! I go by many names, so it’s up to you which name you will give me :).</p><p>This is my first post, so I will start by listing some goals I set for myself.</p><p>I will be focusing on consolidating my knowledge in Digital Forensics, by attempting to do the Sherlocks series from HTB ( Well, without the VIP boxes, since fuck freemium-based services, sorry HTB, but it is what it is. ).</p><p>Second, I will post from time to time, some reports from old labs that I made.</p><p>Third, I will post ( again from time to time ), some academic-focused write-ups on some cryptographic algorithms ( mostly some thought experiments on old ciphers and reinventing the wheel ).</p><p>Fourth, I don’t know, never went that far into the thought, it’s still a work in progress tho.</p><p>So yeah, I will see what I will do soon, outside from what I have listed.</p><p>Stay tuned for my future posts, where I will go on a full-on mental disaster of a marathon on the Sherlocks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d950112e7df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>