<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reversing on pnasis</title>
    <link>https://pnasis.gitlab.io/tags/reversing/</link>
    <description>Recent content in Reversing on pnasis</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 05 Apr 2026 22:55:12 +0300</lastBuildDate>
    <atom:link href="https://pnasis.gitlab.io/tags/reversing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>RITSEC CTF 2026 - Reversing Writeups (Part 4): obfpyscated</title>
      <link>https://pnasis.gitlab.io/posts/ritsec-ctf-2026-reversing-writeups-part-4-obfpyscated/</link>
      <pubDate>Sun, 05 Apr 2026 22:55:12 +0300</pubDate>
      <guid>https://pnasis.gitlab.io/posts/ritsec-ctf-2026-reversing-writeups-part-4-obfpyscated/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;    The fourth and final challenge in the series was named &lt;em&gt;&lt;strong&gt;&amp;ldquo;obfpyscated&amp;rdquo;&lt;/strong&gt;&lt;/em&gt;, a title that already hinted at deliberate code obfuscation and an intentionally painful reversing experience. This was the last challenge I solved from the reversing track and it pushed the analysis beyond straightforward decompilation into progressively more behavior driven investigation.&lt;/p&gt;&#xA;&lt;p&gt;    I participated in this challenge as part of the &lt;a href=&#34;https://ctfd.ritsec.club/&#34;&gt;RITSEC CTF 2026&lt;/a&gt; Jeopardy style competition, working within the same reversing track as the previous challenges in this series. At this point, after having already dealt with multiple layers of packed logic, custom encryption schemes and runtime generated behavior, I expected this challenge to focus less on clarity and more on hiding intent through structure rather than complexity alone.&lt;/p&gt;</description>
    </item>
    <item>
      <title>RITSEC CTF 2026 - Reversing Writeups (Part 3): Buried Treasure</title>
      <link>https://pnasis.gitlab.io/posts/ritsec-ctf-2026-reversing-writeups-part-3-buried-treasure/</link>
      <pubDate>Sun, 05 Apr 2026 11:54:26 +0300</pubDate>
      <guid>https://pnasis.gitlab.io/posts/ritsec-ctf-2026-reversing-writeups-part-3-buried-treasure/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;    Continuing my participation in &lt;a href=&#34;https://ctfd.ritsec.club/&#34;&gt;RITSEC CTF 2026&lt;/a&gt;, this third part of the series focuses on another reversing challenge titled &lt;em&gt;&lt;strong&gt;“Buried Treasure”&lt;/strong&gt;&lt;/em&gt;. As with the previous writeups, this post documents the full process of analyzing the binary, understanding its internal logic and extracting the solution.&lt;/p&gt;&#xA;&lt;p&gt;    The name of the challenge already suggests something intentionally hidden rather than immediately visible, which typically hints at logic that is either obscured, layered, or embedded in an unusual part of the program flow.&lt;/p&gt;</description>
    </item>
    <item>
      <title>RITSEC CTF 2026 - Reversing Writeups (Part 2): not quite optimal</title>
      <link>https://pnasis.gitlab.io/posts/ritsec-ctf-2026-reversing-writeups-part-2-not-quite-optimal/</link>
      <pubDate>Sat, 04 Apr 2026 13:35:13 +0300</pubDate>
      <guid>https://pnasis.gitlab.io/posts/ritsec-ctf-2026-reversing-writeups-part-2-not-quite-optimal/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;    Continuing my participation in &lt;a href=&#34;https://ctfd.ritsec.club/&#34;&gt;RITSEC CTF 2026&lt;/a&gt;, this second part of the series focuses on another challenge from the Reversing category titled &lt;em&gt;&lt;strong&gt;“not quite optimal”&lt;/strong&gt;&lt;/em&gt;. As with the previous writeup, the goal here is to document the full thought process behind solving the challenge, from initial inspection of the binary to understanding its underlying logic and ultimately deriving the solution.&lt;/p&gt;&#xA;&lt;p&gt;    This challenge immediately gave the impression that the solution would not come from following the code literally, but rather from simplifying what the program was actually doing and stripping away unnecessary complexity.&lt;/p&gt;</description>
    </item>
    <item>
      <title>RITSEC CTF 2026 - Reversing Writeups (Part 1): T-reasure Chest</title>
      <link>https://pnasis.gitlab.io/posts/ritsec-ctf-2026-reversing-writeups-part-1-t-reasure-chest/</link>
      <pubDate>Sat, 04 Apr 2026 03:04:29 +0300</pubDate>
      <guid>https://pnasis.gitlab.io/posts/ritsec-ctf-2026-reversing-writeups-part-1-t-reasure-chest/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;    Participating in &lt;a href=&#34;https://ctfd.ritsec.club/&#34;&gt;RITSEC CTF 2026&lt;/a&gt;, a &lt;strong&gt;Jeopardy-style&lt;/strong&gt; CTF of &lt;strong&gt;intermediate difficulty&lt;/strong&gt;, was a great opportunity to sharpen my skills across different areas of cybersecurity. I took part in the competition with the team &lt;a href=&#34;https://ctftime.org/team/431287&#34;&gt;Echelon Obscura&lt;/a&gt;, where I served as the team captain and we ultimately placed &lt;strong&gt;147th out of 663 teams&lt;/strong&gt;. The event was both challenging and highly enjoyable, offering a well-balanced mix of problems that required both technical depth and creative thinking under time pressure.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
