<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>P01NT</title><link>https://outofsrvc.github.io/en/</link><description>Recent content 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/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction to Reverse Engineering</title><link>https://outofsrvc.github.io/en/workshop/introduction-to-re/</link><pubDate>Mon, 16 Mar 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/introduction-to-re/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>From childhood, human beings possess an innate curiosity to understand &lt;em>&amp;ldquo;how things work?&amp;rdquo;&lt;/em>. It is this curiosity that drives a child to break apart a favorite toy in order to see the small motor inside it. In the advanced world of technology, this curiosity evolves into a precise and critical engineering discipline known as reverse engineering.&lt;/p>
&lt;p>Most computer users may not have heard of reverse engineering before, perhaps because it is not as widespread as the field of hacking, or perhaps because they know it by another term, namely &amp;ldquo;cracking&amp;rdquo;.&lt;/p></description></item><item><title>Fundamentals of Reverse Engineering</title><link>https://outofsrvc.github.io/en/workshop/fundamentals-of-re/</link><pubDate>Tue, 17 Mar 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/fundamentals-of-re/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;p>In this article we will review the foundational disciplines that must be learned before embarking on the field of reverse engineering. We have distilled this knowledge from several international references and formulated it into Arabic explanations and series that we published on the &amp;ldquo;Arabic Shell Network&amp;rdquo; (Shabakat Shill al-Arabiya), and we append them here along with the original references at the end of each section.&lt;/p>
&lt;p>To begin, every field has fundamentals that cannot be overlooked, and learning them is an obligation, for they will be the launching point of the journey of empowerment that we strive toward, God willing.&lt;/p></description></item><item><title>Windows Architecture &amp; PE Format</title><link>https://outofsrvc.github.io/en/workshop/windows-architecture-and-pe/</link><pubDate>Wed, 18 Mar 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/windows-architecture-and-pe/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;p>Have you ever wondered how programs operate within systems? Or has the following thought occurred to you: what is the difference between an ordinary user and a developer in terms of their understanding of the systems they interact with?&lt;/p>
&lt;p>God willing, in this article we will clarify the executable file format in Windows and discuss some important matters regarding Windows architecture that we must not be ignorant of.&lt;/p>
&lt;blockquote>
&lt;p>Before beginning, if you do not have sufficient knowledge of operating systems, we advise you to review the following series:
🔗 &lt;a href="https://sh3ll.cloud/xf2/threads/4230/">Operating Systems Series on the Shell Network&lt;/a>&lt;/p></description></item><item><title>Recognizing C Code Constructs in Assembly</title><link>https://outofsrvc.github.io/en/workshop/c-constructs-in-assembly/</link><pubDate>Thu, 19 Mar 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/c-constructs-in-assembly/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;p>When beginning to work with Assembly language, one invariably perceives a degree of difficulty owing to its low-level nature, in contrast to higher-level languages such as C or Python. In this research, we attempt to simplify assembly code so that it may be more readily understood.&lt;/p>
&lt;p>The premise of this article is that we will author a simple program in C, compile it into x86 Assembly, and then explain the operations that occur in order to analyze the control flow.&lt;/p></description></item><item><title>Cyber Attack Lifecycle</title><link>https://outofsrvc.github.io/en/workshop/cyber-attack-lifecycle/</link><pubDate>Fri, 20 Mar 2026 11:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/cyber-attack-lifecycle/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;p>When engaging with malicious software (malware) that warrants examination, one must understand the mindset of the adversary and the objectives they pursue. Therefore, in this research we examine the attack lifecycle and explain several fundamental concepts in malware development.&lt;/p>
&lt;p>The attack cycle is divided into three principal stages:&lt;/p>
&lt;p>&lt;img alt="Attack Lifcycle" decoding="async" loading="lazy" src="https://outofsrvc.github.io/assets/img/workshop/lifecycle/lifecycle.png">
&lt;em>Figure (1): Illustration of the attack lifecycle.&lt;/em>&lt;/p>
&lt;hr>
&lt;h2 id="stage-1-initial-access">Stage 1: Initial Access&lt;/h2>
&lt;p>This stage focuses on breaching the initial defensive perimeter and gaining a foothold within the target system.&lt;/p></description></item><item><title>Basic Reconnaissance</title><link>https://outofsrvc.github.io/en/workshop/basic-reconnaissance/</link><pubDate>Sat, 21 Mar 2026 12:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/basic-reconnaissance/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;p>Whenever we intend to analyze any file, we follow the steps below, irrespective of whether the objective is to determine whether the file is benign or contains malware, or even whether we intend to crack its protection:&lt;/p>
&lt;h2 id="the-4-stages-of-analysis">The 4 Stages of Analysis&lt;/h2>
&lt;ol>
&lt;li>
&lt;p>&lt;strong>Basic Static Analysis:&lt;/strong> This analysis does not require deep technical expertise, but relies entirely on tools that operate automatically (such as VirusTotal). It reveals indicators that show whether the file is a virus or not.&lt;/p></description></item><item><title>RE Toolkit: Disassemblers &amp; Debuggers</title><link>https://outofsrvc.github.io/en/workshop/re-toolkit/</link><pubDate>Sun, 22 Mar 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/workshop/re-toolkit/</guid><description>&lt;p>Bismillah&lt;/p>
&lt;p>Having completed the basic analysis (Basic Analysis), we proceed to the advanced analysis (Advanced Analysis). In this article, we examine the principal disassembler and debugger tools employed to analyze binaries, providing a concise and rapid overview. During hands-on application, these tools will be explored in greater depth and detail.&lt;/p>
&lt;hr>
&lt;h2 id="disassemblers">Disassemblers&lt;/h2>
&lt;p>These tools are used to read a program without executing it (Static Analysis), analogous to reading a map to identify directions and terrain before commencing a journey.&lt;/p></description></item><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><item><title>About</title><link>https://outofsrvc.github.io/en/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://outofsrvc.github.io/en/about/</guid><description>&lt;p>I&amp;rsquo;m &lt;strong>P01NT&lt;/strong> (&lt;a href="https://github.com/outofsrvc">@outofsrvc&lt;/a>), a technical researcher specializing in reverse engineering, malware analysis, and low-level systems.&lt;/p>
&lt;p>My focus is on dissecting executables (PE Format), analyzing malware encryption, and studying system behavior. I created the &lt;strong>Entry P01NT&lt;/strong> workshop to make reverse engineering and disassembly concepts approachable. I have also published many technical articles that have exceeded &lt;strong>10,000+ views&lt;/strong> on the &lt;a href="https://sh3ll.cloud/xf2/members/4161/">&lt;strong>Arab Shell Network&lt;/strong>&lt;/a>.&lt;/p>
&lt;p>This blog is where I write down what I learn: technical articles, analyses, and a complete teaching workshop.&lt;/p></description></item><item><title>Search</title><link>https://outofsrvc.github.io/en/search/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://outofsrvc.github.io/en/search/</guid><description>search</description></item></channel></rss>