<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Deobfuscation on pnasis</title>
    <link>https://pnasis.gitlab.io/tags/deobfuscation/</link>
    <description>Recent content in Deobfuscation 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/deobfuscation/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>
  </channel>
</rss>
