<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reverse-Engineering on P01NT</title><link>https://outofsrvc.github.io/en/categories/reverse-engineering/</link><description>Recent content in Reverse-Engineering on P01NT</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 09 Aug 2026 12:00:00 +0300</lastBuildDate><atom:link href="https://outofsrvc.github.io/en/categories/reverse-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>The Reverse Engineer's Mindset</title><link>https://outofsrvc.github.io/en/workshop/thinking-lab/</link><pubDate>Mon, 23 Mar 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/thinking-lab/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;p>The reverse engineer does not perceive code merely as complex programming instructions, but rather as a &amp;ldquo;black box&amp;rdquo; with inputs and outputs. In this article, we discuss how the reverse engineer&amp;rsquo;s mindset is built and how to infer the hidden programmatic logic.&lt;/p>
&lt;hr>
&lt;h2 id="the-scenario">The Scenario&lt;/h2>
&lt;p>Imagine we are confronted with a locked electronic door. This door opens only if a single correct character is entered from the keyboard. We have only the keyboard and a small screen that displays a single message upon each input attempt.&lt;/p></description></item><item><title>Static Lab</title><link>https://outofsrvc.github.io/en/workshop/static-lab/</link><pubDate>Tue, 24 Mar 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/static-lab/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;p>In this article, we will solve a simple lab challenge that relies entirely on static analysis (Static Analysis). The objective here is to apply the concepts learned previously to decrypt the flag hidden within the program.&lt;/p>
&lt;blockquote>
&lt;p>Lab environment setup: You may download the executable for this lab from the following link &lt;a href="https://outofsrvc.github.io/assets/binaries/5t4t1c_cr4ckm3.7z">5t4t1c_cr4ckm3&lt;/a> in the course repository. The archive password is: &lt;strong>p01nt&lt;/strong>&lt;/p>&lt;/blockquote>
&lt;hr>
&lt;blockquote>
&lt;p>To open this file you must open it inside a &lt;strong>VM&lt;/strong>. Although I am the one who designed this file, never trust the cyber community. We will run the file with the following command&lt;/p></description></item><item><title>Dynamic Lab</title><link>https://outofsrvc.github.io/en/workshop/dynamic-lab/</link><pubDate>Wed, 25 Mar 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/dynamic-lab/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;p>In this article, we will solve a simple lab challenge that relies entirely on dynamic analysis using the x64dbg debugger. We assess that the exercise demonstrates how to bypass anti-debugging mechanisms and how to patch the program&amp;rsquo;s execution flow so that it accepts any key we provide.&lt;/p>
&lt;blockquote>
&lt;p>Lab environment setup: The executable for this lab can be downloaded from the following link &lt;a href="https://outofsrvc.github.io/assets/binaries/dyn4m1c_cr4ckm3.7z">dyn4m1c_cr4ckm3&lt;/a> in the course repository. Archive password: &lt;strong>p01nt&lt;/strong>&lt;/p></description></item><item><title>After That</title><link>https://outofsrvc.github.io/en/workshop/after-that/</link><pubDate>Thu, 26 Mar 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/after-that/</guid><description>&lt;p>Bismillah, and peace and blessings upon the Messenger of Allah, and upon his family and companions and those who follow him.&lt;/p>
&lt;p>Praise be to Allah, Lord of the worlds, by whose favor and guidance the &lt;strong>Entry P01NT&lt;/strong> workshop has been completed. I ask Allah to record for you beneficial knowledge and righteous deeds through it, and that it be a good beginning for you.&lt;/p>
&lt;hr>
&lt;h2 id="the-road-ahead">The Road Ahead&lt;/h2>
&lt;p>Reverse engineering is not merely reading articles; it is practice, experimentation, and building muscle memory in handling tools and analyzing code. Accordingly, we have prepared a simple roadmap for you:&lt;/p></description></item><item><title>Flare-On 2015: Solving Challenge 1</title><link>https://outofsrvc.github.io/en/posts/flare-on15-1/</link><pubDate>Sun, 09 Aug 2026 12:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/posts/flare-on15-1/</guid><description>&lt;p>بسم الله&lt;/p>
&lt;p>In this article, we are going to solve the first challenge of &lt;strong>Flare-On (2015)&lt;/strong>. As usual, we will rely on the &lt;strong>Learning-by-Doing&lt;/strong> methodology and the &lt;strong>Just-in-Time Learning&lt;/strong> approach.&lt;/p>
&lt;h2 id="1-downloading-and-running-the-challenge">1. Downloading and Running the Challenge&lt;/h2>
&lt;p>First, we download the challenge from the official website: &lt;a href="https://flare-on.com/">flare-on.com&lt;/a>&lt;/p>
&lt;blockquote>
&lt;p>Archive password: &lt;strong>flare&lt;/strong>.&lt;/p>&lt;/blockquote>
&lt;p>Let&amp;rsquo;s start by running the file we have in front of us:&lt;/p>
&lt;p>&lt;img alt="Running the file for the first time" decoding="async" loading="lazy" src="https://outofsrvc.github.io/assets/img/flareon15/run1.png">
&lt;em>Figure (1): Running the file for the first time&lt;/em>&lt;/p></description></item><item><title>Flare-On 2014: Solving Challenge 1</title><link>https://outofsrvc.github.io/en/posts/flare-on-14-1/</link><pubDate>Fri, 07 Aug 2026 00:30:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/posts/flare-on-14-1/</guid><description>&lt;p>بسم الله&lt;/p>
&lt;p>In this article, we are going to solve the first challenge of &lt;strong>Flare-On (2014)&lt;/strong>. We will rely — for this challenge and for most of the upcoming ones — on the &lt;strong>Just-in-Time Learning&lt;/strong> methodology, also known as &lt;strong>Learning-by-Doing&lt;/strong>.&lt;/p>
&lt;h2 id="why-did-we-start-with-flare-on">Why Did We Start with Flare-On?&lt;/h2>
&lt;p>Because these challenges are built around real-world techniques, and they are not just artificial CTF puzzles as commonly presented in competitions.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Important note:&lt;/strong> CTF challenges are only a bridge between theoretical learning and hands-on practice. They do not, in any way, prove that you are an expert in the field. Real experience is gained by working with real-world programs — whether malware, games, or software we reverse engineer.&lt;/p></description></item></channel></rss>