<?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 Mina Max on Medium]]></title>
        <description><![CDATA[Stories by Mina Max on Medium]]></description>
        <link>https://medium.com/@0xAnub1sX?source=rss-88a221271230------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*l-aNa9cZAV22hWWv</url>
            <title>Stories by Mina Max on Medium</title>
            <link>https://medium.com/@0xAnub1sX?source=rss-88a221271230------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:15:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@0xAnub1sX/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[LUXSAI CTF DFIR Challenges]]></title>
            <link>https://medium.com/@0xAnub1sX/luxsai-ctf-df-challenges-f0f95062697b?source=rss-88a221271230------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0f95062697b</guid>
            <dc:creator><![CDATA[Mina Max]]></dc:creator>
            <pubDate>Sun, 15 Mar 2026 02:19:34 GMT</pubDate>
            <atom:updated>2026-03-15T02:25:37.353Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Challenge 1:<br></strong> History<strong><br> Category:<br> </strong>DFIR<strong><br> Difficulty:<br></strong> so easy</p><p><strong>Description:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/1*livJ20PYmWWFst4FCHp7nw.png" /></figure><blockquote><em>An employee is under investigation after a phishing campaign targeted the company. When confronted, they claimed: “I never visited that site — check my browser history if you don’t believe me.”</em></blockquote><blockquote><em>We pulled a copy of their Firefox profile from their Linux workstation. History looks clean, but we’re not convinced.</em></blockquote><blockquote><em>Prove they visited the phishing site and recover the full URL containing the flag</em></blockquote><p>هنا بيقول ان الشركه كانت بتعرض ل حملة phishing عليها و صادت موظف هناك عشان داس علي اللينك<br> و عمنا الموظف جابوه و بيستجوبوه و طبعا انكر انه داس علي اي حاجه<br> راح جابو History بتاع الفايرفوكس بتاعه عشان يتاكدوا من كلامه<br> و دي مهمتنا بقا<br> هنلاقي ف اللينك دا اللي المعلم دا داس عليها موجود فيه الفلاج</p><p>Tools Used:</p><ul><li>DB Browser (SQLite)</li></ul><p>Investigation Steps:</p><ol><li>طبعا هتنزل DB Browser (SQLite) و الفايل قبل اي حاجه</li><li>نفك الضغط بتاعه هيطلعلك الفايلز بتاعت البروازر</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_zCxKEswzTit74ZkRsh1aA.png" /></figure><p>هتلاقي فيه فايلين اسمهم places.sqlite favicons.sqlite و دول الي تقدر تفتحهم ب DB Browser (SQLite)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nj_nHMflJPLKV-EAuBQF5g.png" /></figure><blockquote><strong>places.sqlite</strong> يحتوي على:</blockquote><ul><li>Browsing History</li><li>Bookmarks metadata<br> يعني دا المصدر الأساسي لمعرفة اللينكات اللي المستخدم دخل عليها بس لو دخلت عليها مش هتلاقي اي حاجة ليها فايدة ف ممكن تكون اتمسحت ف ندخل علي التاني</li></ul><blockquote><strong>favicons.sqlite</strong> و اللي بيحتوي :</blockquote><ul><li><strong>Favicon metadata</strong></li><li>أيقونات المواقع الصغيرة</li></ul><p>و <strong>وجود favicon ممكن يقول ان الموقع اتفتح قبل كدا</strong> لأن المتصفح حمل ال icon</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1XlE5_-rUUOYn16zD9OODQ.png" /></figure><p>ف لما دخلت عليه و دخلت علي moz_pages_w_icons table هتلاقي الفلاج<br> وادي اهو الفلاج</p><blockquote>CyCTF{f168079bd163a3153e05a81bb8f07087}</blockquote><p>و كدا اثبتنا ان المعلم دا داس علي اللينك و اتفصل و قطعنا بعيشه</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p><strong>Challenge 2:</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0f95062697b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MBR_Analysis_For_Investigators]]></title>
            <link>https://medium.com/@0xAnub1sX/mbr-analysis-for-investigators-85253b952d5b?source=rss-88a221271230------2</link>
            <guid isPermaLink="false">https://medium.com/p/85253b952d5b</guid>
            <dc:creator><![CDATA[Mina Max]]></dc:creator>
            <pubDate>Thu, 21 Aug 2025 01:17:41 GMT</pubDate>
            <atom:updated>2025-08-21T01:17:41.784Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>MBR Analysis For Investigators</strong></p><p><strong>By MINA MAX (0xAnub1sX)</strong></p><p>Before we dive into it:</p><p>We should know <strong>HOW DOES THE COMPUTER START UP</strong>?</p><p>Boot process:</p><blockquote>Power on -&gt; POST -&gt; local bootable devices -&gt; Read MBR/GPT -&gt; load boot-loader -&gt; load OS</blockquote><h3><strong>1.</strong> <strong>Power on</strong></h3><p>When you click the power button it will send electrical signals to the CPU, and it will need the knowledge for the next step so it will use BIOS/UEFI to do it.</p><p><strong>BIOS =&gt; MBR =&gt; 2TB =&gt; 16-bit</strong></p><p><strong>UEFI =&gt; GPT =&gt; 9ZB =&gt; 32-bit, 64-bit</strong></p><blockquote><em>NOTE: if you want to know it in your PC click (WIN+R) and write (msinfo32) -&gt; you will find it in your bios mode</em></blockquote><p>— — -</p><h3><strong>2.</strong> <strong>POST (Power-On-Self-Test)</strong></h3><p>- Now the system is powered ON</p><p>- The CPU executed the instructions from the BIOS/UEFI</p><p>- Now the BIOS/UEFI checking that all hardware is ok by “Power-On-Self-Test”</p><p>(you may hear some beeps in this stage 😂)</p><p>— — -</p><h3><strong>3.</strong> <strong>Locate the bootable devices</strong></h3><p>- Check the bootable devices like SSD, HDD, USB if any has an os installed.</p><p>- Read the bootable device</p><p>- From now the MBR/GPT will take the role to make the next action</p><h3>………………………….…..MBR…………………..………….</h3><p>We will find it the 1st sector (sector number “0”)</p><p>The size of this sector = 512 byte</p><h4><strong>The structure of MBR</strong></h4><p>1. Boot strap code =&gt; 446 byte</p><p>2. Partition table =&gt; 64 byte</p><p>3. MBR signature =&gt; 2 byte</p><h4><strong><em>a.</em></strong> <strong><em>Boot strap code “0–445”</em></strong></h4><p>- It contains the initial boot-loader</p><p>- The bootstrap code usually contains the first stage of the boot-loader (Stage 1), which is responsible for locating and loading the second stage or the operating system loader from the bootable partition.</p><h4><strong><em>b.</em></strong> <strong><em>Partition Table “446–509”</em></strong></h4><p>- Contain the details of the partitions on the disk</p><p>- The partition table in the MBR supports a maximum of 4 primary partitions. Alternatively, you can have 3 primary partitions and 1 extended partition, which can contain multiple logical partitions.</p><p>- One of these partitions has all OS files =&gt; bootable partition</p><blockquote><strong><em>(partitions &lt;= “4” * “16” =&gt; byte = 64 byte)</em></strong></blockquote><p>— —</p><p><strong>We will take one partition to dive into it.</strong></p><h4><strong>Every partition has:</strong></h4><p>- Boot indicator</p><p>- Starting CHS address</p><p>- Partition type</p><p>- Ending CHS address</p><p>- Starting LBA address</p><p>- Number of sectors</p><h3><strong>1.</strong> <strong>Boot indicator: “1 Byte Length”</strong></h3><p>- Tell you if it is bootable or not</p><p>If you find this byte (0x80) -&gt; bootable</p><p>If you find (0x00) -&gt; non-boot</p><p>— — -</p><h3><strong>2.</strong> <strong>Starting CHS address: “3 Byte Length”</strong></h3><p>(Cylinder Header Sector)</p><p>It tells you where the partition starts on the disk</p><blockquote>NOTE: “It’s not important now because we use LBA -&gt; we’ll see why in a few minutes”</blockquote><p>— — -</p><h3><strong>3.</strong> <strong>Partition type “1 Byte Length”</strong></h3><p>- It indicates the file system of the partition</p><p>- Common partition values:</p><p>0x01 FAT12 &lt;32MB</p><p>0x84 Windows hibernation partition</p><p>0x04 FAT16 &lt;32MB</p><p>0x85 Linux extended</p><p>0x06 FAT16B</p><p>0xA5 FreeBSD slice</p><p>0x07 NTFS, HPFS, exFAT</p><p>0xA6 OpenBSD slice</p><p>0x0B FAT32 CHS</p><p>0xAB Mac OS X boot</p><p>0x0C FAT32 LBA</p><p>0xAF HFS, HFS+</p><p>0x0E FAT16 LBA</p><p>0xEE MS GPT</p><h3><strong>4.</strong> <strong>Ending CHS address: “3 Byte Length”</strong></h3><p>- It tells you where the partition ends on the disk</p><p>- Modern systems largely ignore the CHS values and rely on LBA instead, but the CHS fields are still present for backward compatibility with older BIOS systems.</p><p>— — -</p><h3><strong>5.</strong> <strong>Starting LBA address: “4 Byte Length”</strong></h3><p>- It tells you where the partition starts on the disk “Logically”</p><p>and we use it instead of CHS -&gt; LBA is faster, simpler, and scales to modern storage sizes, while CHS was tied to old hardware limits and unnecessary complexity</p><p>— — -</p><h3><strong>6.</strong> <strong>Number of sectors “4 Byte Length”</strong></h3><p>- Tells us the number of sectors in the current partition</p><p>You can use it to calculate the size of the partition</p><p><strong>Let’s calculate it 😉</strong></p><p>Before we calculate this, we should know about “endian format”</p><p><strong>Endian format</strong> is about how a system stores the bytes of multi-byte data in memory.</p><h4><strong>Two main types</strong></h4><h4>· <strong>Little Endian</strong></h4><p>o Least significant byte stored first (at the lowest memory address)</p><p>o Example: 0x12345678 stored as 78 56 34 12</p><p>o Common on Intel x86, x86–64</p><h4>· <strong>Big Endian</strong></h4><p>o Most significant byte stored first (at the lowest memory address)</p><p>o Example: 0x12345678 stored as 12 34 56 78</p><p>o Common in some network protocols, older CPUs like Motorola 68k</p><p>So, we will use the <strong>little endian</strong> now</p><p>- Last 4 bytes = number of sectors = 00 B0 23 03</p><p>- Stored in little endian → reverse → 03 23 B0 00</p><p>- Convert to decimal → 52,670,464 sectors</p><p>- Sector size = 512 bytes</p><p>- Partition size = 52,670,464 × 512 = 26,967,277,568 bytes</p><blockquote><strong>NOTE: You can also determine the last sector address of the partition by using:<br> “Last sector = Starting LBA + Number of Sectors — 1”</strong></blockquote><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><h3><strong><em>c.</em></strong> <strong><em>MBR signature “510–511”:</em></strong></h3><p>55 AA is a magic number marking the end of the MBR.<br> <strong>If changed, the system won’t boot</strong>.<br> Corruption can occur from bad sectors or be done intentionally by malware.</p><p>When read as a single 16-bit value on little-endian systems, the bytes 0x55AA appear as 0xAA55 in memory.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85253b952d5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>