<?xml version="1.0"?>
<rss version="2.0"><channel><title>Unpackers Latest Topics</title><link>https://decodehub.org/forum/38-unpackers/</link><description>Unpackers Latest Topics</description><language>en</language><item><title><![CDATA[C++ Enigma Protector 5.x–7.x Dumper & PE Fixer Tool [Dump + Auto IAT + EP Repair]]]></title><link>https://decodehub.org/topic/31-c-enigma-protector-5x7x-dumper-pe-fixer-tool-dump-auto-iat-ep-repair/</link><description><![CDATA[<p><span class="ipsEmoji" title="">🚀</span> This C++ tool helps you dump and fix Enigma Protector–protected EXE files (tested from v5.x up to v7.80).</p><p>It automatically dumps the main executable from memory, resets critical PE structures like IAT, OEP, relocations, and more.</p><p><span class="ipsEmoji" title="">⚠️</span> Note: As of Enigma v7.80, the dumped EXE may not run correctly due to deeper anti-dump mechanisms. The tool still extracts valid memory and headers — allowing you to continue manually.</p><p><span class="ipsEmoji" title="">✅</span> What This Tool Does:</p><p>Performs multiple anti-debug checks (PEB, DebugPort, IsDebuggerPresent).</p><p>Suspends other threads for stable dumping.</p><p>Identifies and validates the main module in memory.</p><p>Detects inline hooks to prevent faulty dumps.</p><p>Dumps the full memory image of the main EXE.</p><p>Rebuilds PE headers:</p><p>Sets new OEP</p><p>Clears relocations, TLS, and resource sections</p><p>Resets checksum</p><p>Finds the section where OEP resides and logs it.</p><p>Performs a basic Import Address Table (IAT) rebuild.</p><p>Dumps all loaded DLLs into a Dumps/ folder for further analysis.</p><p><span class="ipsEmoji" title="">❌</span> Why the Dumped EXE May Not Work (Especially in 7.x):</p><p>Enigma uses dynamic unpacking, loading code in stages.</p><p>Real EntryPoint (OEP) may only be valid after several layers finish.</p><p>Some APIs remain encrypted or virtualized in memory, and aren’t dumped cleanly.</p><p>IAT fixing is basic — no redirection or advanced import fixing is handled.</p><p>.reloc, .tls, and .rsrc are cleared to avoid loader errors but may affect app logic.</p><p><span class="ipsEmoji" title="">🛠️</span> Manual Fixing Instructions:</p><p>If the dumped fixed_dump.exe doesn’t run:</p><p>Use a debugger like x64dbg:</p><p>Run the target until all UI/windows show.</p><p>Dump process memory manually from that point.</p><p>Get the actual OEP from the execution trace.</p><p>Use tools like:</p><p>Scylla or ImpREC to rebuild IAT manually.</p><p>PE-bear to fix headers or corrupt sections.</p><p>Patch anti-debug or integrity checks:</p><p>Most failures are due to runtime checks on dumped memory.</p><p>Patch .text or .vmp sections if needed.</p><p><span class="ipsEmoji" title="">🔮</span> Future Improvements:</p><p>Full IAT reconstruction with thunk redirection</p><p>Delayed import and forwarded DLL fix</p><p>Resource rebuild or extraction</p><p>VM section cleanup (devirtualizer plugins)</p><p><span class="ipsEmoji" title="">📁</span> Output Files:</p><p>File Description</p><p>dump_raw.bin Raw dumped memory of EXE</p><p>fixed_dump.exe PE header–repaired executable</p><p>Dumps/*.dll All loaded dependent DLLs dumped</p><p><span class="ipsEmoji" title="">🧪</span> Tested On:</p><p><span class="ipsEmoji" title="">✅</span> Enigma 5.70</p><p><span class="ipsEmoji" title="">✅</span> Enigma 6.30</p><p><span class="ipsEmoji" title="">✅</span> Enigma 7.80</p><p><span class="ipsEmoji" title="">⚠️</span> Enigma</p><p><span class="ipsEmoji" title="">⚠️</span> Disclaimer:</p><p>This tool is meant for educational and reverse-engineering research purposes only.</p><p>Use it only on software you own or have legal rights to reverse-engineer.</p><p>Author is not responsible for misuse or any resulting damages.</p><p>[Hidden Content]</p>]]></description><guid isPermaLink="false">31</guid><pubDate>Sun, 30 Aug 2026 14:12:51 +0000</pubDate></item><item><title>Process Name Dumper x64 1.2</title><link>https://decodehub.org/topic/137-process-name-dumper-x64-12/</link><description><![CDATA[<p><img class="ipsImage ipsRichText__align--block" data-fileid="179" src="https://decodehub.org/uploads/monthly_2026_11/PNDx64.thumb.jpg.81c1e024d77b06ff39b2f40769d391c7.jpg.c003d7c368d252bd52a2f9a2a1618cc2.jpg" alt="PNDx64.thumb.jpg.81c1e024d77b06ff39b2f40769d391c7.jpg" title="" loading="lazy"></p><p>PE and PE+ (x86 and x64) files dump</p><p>EXE,SCR,DLL and OCX files are supported</p><p>Engine 1 and Engine 2 for packed and protected files dump</p><p>Dump Fix to repair like armadillo files</p><p>TUTORİALS</p><p>[Hidden Content]</p><p>DOWNLOAD</p><p>[Hidden Content]</p>]]></description><guid isPermaLink="false">137</guid><pubDate>Tue, 03 Nov 2026 02:15:01 +0000</pubDate></item><item><title>NETReactorSlayer-6.4.0.0 NETReactor Unpacker</title><link>https://decodehub.org/topic/75-netreactorslayer-6400-netreactor-unpacker/</link><description><![CDATA[<p>NETReactorSlayer-6.4.0.0_Fixed11</p><p>This is the version of netreactorslayer patched by codeexplorer to crack new versions of netreactor.</p><p>[Hidden Content]</p>]]></description><guid isPermaLink="false">75</guid><pubDate>Mon, 14 Sep 2026 20:58:59 +0000</pubDate></item><item><title>VMP 3.9.5 StaticUnpacker</title><link>https://decodehub.org/topic/82-vmp-395-staticunpacker/</link><description><![CDATA[<h1><strong>VMPStaticUnpacker</strong></h1><p>A static VMProtect unpacker for Windows PE files</p><p>It supports legacy plaintext <code>PACKER_INFO</code> metadata and the compact rotating-XOR format observed in VMProtect 3.9.5 PE32+ samples.</p><h2><strong>Usage</strong></h2><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>python vmpstaticunpacker.py packed.exe unpacked.exe</code></pre><h2><strong>VMProtect 3.9.5</strong></h2><p>The initial destination key is recovered from the first packed section RVA:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>key[0] = encoded_destination[0] XOR first_packed_section_rva
destination[i] = encoded_destination[i] XOR key[i]
key[i + 1] = ROL32(key[i], 7)
</code></pre><p>Each candidate table and LZMA stream is validated before rebuilding the PE.</p><h2><strong>Limitations</strong></h2><p>The output uses a memory-image layout for static analysis. This tool does not devirtualize protected functions, recover the original entry point, remove the VMProtect runtime, or repair imports</p><p>[Hidden Content]</p>]]></description><guid isPermaLink="false">82</guid><pubDate>Thu, 17 Sep 2026 15:17:47 +0000</pubDate></item><item><title>[.NET] DNGuard Static Unpacker By CodeExplorer</title><link>https://decodehub.org/topic/83-net-dnguard-static-unpacker-by-codeexplorer/</link><description><![CDATA[<p><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">For v3.9.0 I fail to find Methods Count in structures and also MethodOffset.</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">Method Offset changes when applied on same unpackme</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v3.9.6/v4.1/v4.2 284C</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v3.9.7/v4.0 2840</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v4.3 2848</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v4.6/v4.8 2858</span><br><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">LEHSize changes when applied on same unpackme:</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v3.9.0  1184 ???</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v3.9.6 1256</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v3.9.7 1212</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v4.0 1239</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v4.1 1216</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v4.2 1229</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v4.3 1203</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v4.6 1233</span><br><span style="font-family: Tahoma, Verdana, Arial, Helvetica, sans-serif;">v4.8 1220</span><br>[Hidden Content]</p>]]></description><guid isPermaLink="false">83</guid><pubDate>Thu, 17 Sep 2026 15:21:32 +0000</pubDate></item><item><title>VMProtectNoDelegates (.NET)</title><link>https://decodehub.org/topic/85-vmprotectnodelegates-net/</link><description><![CDATA[<p>VMProtectNoDelegatesFixed4<br>[Hidden Content]</p>]]></description><guid isPermaLink="false">85</guid><pubDate>Thu, 17 Sep 2026 15:29:35 +0000</pubDate></item><item><title>Pyarmor Static Unpack One-Shot Tool</title><link>https://decodehub.org/topic/80-pyarmor-static-unpack-one-shot-tool/</link><description><![CDATA[<p>[Hidden Content] is a popular tool to protect Python source code. It turns Python scripts into binary data, which can be regarded as an encrypted variant of pyc files. They can be decrypted by a shared library (pyarmor_runtime) and then executed by Python interpreter.</p><p>This project aims to convert armored data back to bytecode assembly and (experimentally) source code. We forked the awesome [Hidden Content] (aka pycdc), and added some processes on it like modifying abstract syntax tree.</p><p><strong>Important</strong></p><p>This tool should only be used on scripts you own or have permission to analyze. Please respect software licenses and terms of service. The author is not responsible for any misuse or damage caused by this tool.</p><p><strong>Note</strong></p><p>Like other decompilers, this tool is intended for professional users. You should have a basic understanding of Python bytecode. If not, you may need to ask for help from someone who does.</p><p><strong>Warning</strong></p><p><strong>Disassembly results are accurate, but decompiled code can be incomplete and incorrect.</strong> [Hidden Content]</p><h2><strong>Features</strong></h2><h3><strong>Static</strong></h3><p>You don't need to execute the encrypted script. We decrypt them using the same algorithm as pyarmor_runtime. This is useful when the scripts cannot be trusted.</p><h3><strong>Universal</strong></h3><p>Currently we are trying to support Pyarmor 8.0 to 9.2.x (latest), Python 3.7 - 3.13, on all operating systems, with obfuscating options as many as possible. (However, we only have limited tests.)</p><p>You can run this tool in any environment, no need to be the same with obfuscated scripts or runtime.</p><p><strong>Note</strong></p><p>If the data starts with <code>PY</code> followed by six digits, it is supported. Otherwise, if it starts with <code>PYARMOR</code>, it is generated by Pyarmor 7 or earlier, and is not supported.</p><h3><strong>Easy to use</strong></h3><p>The only thing you need to do is specifying where your obfuscated scripts are. The tool does everything like detecting armored data, parsing, disassembling, and decompiling. See "Usage" section below.</p><h2><strong>Build</strong></h2><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>mkdir build
cd build
cmake ../pycdc
cmake --build .
cmake --install .</code></pre><p>You can also download prebuilt binary files on [Hidden Content].</p><h2><strong>Usage</strong></h2><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>python /path/to/oneshot/shot.py /path/to/scripts</code></pre><p>Before running <code>shot.py</code>, make sure the executable <code>pyarmor-1shot</code> (<code>pyarmor-1shot.exe</code> on Windows) exists in <code>oneshot</code> directory.</p><p>You only need to specify the directory that contains all armored data and <code>pyarmor_runtime</code>. The tool finds and handles them recursively as much as possible.</p><p>When necessary, specify a <code>pyarmor_runtime</code> executable with <code>-r path/to/pyarmor_runtime[.pyd|.so|.dylib]</code>.</p><p>All files generated from this tool have a <code>.1shot.</code> in file names. If you want to save them in another directory instead of in-place, use <code>-o another/path/</code>. Folder structure will remain unchanged.</p><p>Note:</p><ul><li><p>Subdirectories will not be touched if the folder name is exactly <code>__pycache__</code> or <code>site-packages</code> or it directly contains a file named <code>.no1shot</code>, and symbolic links will not be followed, to avoid repeat or forever loop and save time. If you really need them, run the script later in these directories and specify the runtime.</p></li><li><p>Archives, executables generated by PyInstaller and so on, must be unpacked by other tools before decrypting, or you will encounter undefined behavior.</p></li></ul><h2><strong>Feedback</strong></h2><p>Feel free to open an issue if you have any questions, suggestions, or problems. Don't forget to attach the armored data and the <code>pyarmor_runtime</code> executable if possible.</p><h2><strong>Project Status</strong></h2><h3><strong>Current</strong></h3><p><strong>Bug fixes and minor improvements.</strong></p><p>The author is trying to design and implement a new pyc decompiler. After that, we can rewrite this tool with the new decompiler.</p><p>We will discard the current codebase based on pycdc, and after the new code becomes stable, expected in 2027, we will reach version 1.0.0.</p><h3><strong>Before v1.0.0</strong></h3><p><strong>The project is already functioning well, no need to wait for v1.0.0.</strong> The public API is still subject to change.</p><p>These are the features we are planning to implement before v1.0.0:</p><ul><li><p>Rewriting the codebase based on a new pyc decompiler. It will be more stable, maintainable, and extendable.</p></li><li><p>Wiki about the Pyarmor decryption algorithm, and how we analyzed it and implemented it in this tool.</p></li><li><p>The last piece of the puzzle: analysis tool for the native part of BCC Mode (the hardest obfuscating option in Pyarmor).</p></li><li><p>Packaging and distribution of the tool, for installation from package managers like pip.</p></li></ul><p>Maybe there are not many things to do after v1.0.0. We will maintain the project and fix bugs if necessary.</p><h2><strong>Original Intention</strong></h2><p>There are not many code protection tools for Python that are publicly available, and Pyarmor is one of the most popular ones. However, when I (Lil-Ran) was analyzing some specific Pyarmor-protected scripts, I found it not so difficult as I had imagined.</p><p>Just encrypting the code objects is not as irreversible as the project claims. To be honest, Python bytecode based protection is much less secure than native code based protection.</p><p>We definitely do not make profits by cracking. We ourselves had no other uses for this tool, so we published it, hoping to let people know that Pyarmor with default configuration is not as secure as they think.</p><p>The Pyarmor algorithm has not been changed, even a year after this unpacking tool is released. Perhaps it is due to considerations of backward compatibility.</p><p>We guarantee that once Pyarmor project changes the algorithm, we will <strong>not</strong> update this tool to support the new algorithm. Currently existing code generated by supported versions of Pyarmor can always be decrypted by this tool.</p><h3><strong>For CTF Challenge Makers</strong></h3><p>Please, don't make CTF (Capture The Flag) <strong>REVERSE</strong> challenges that are about finding and using existing <strong>TOOLS</strong>. It is not fun for anyone. It is more like a game of hide-and-seek, rather than a test of skill and ingenuity.</p><p>It is more meaningful to understand how Pyarmor or this tool works, and then try to improve them.</p><p>[Hidden Content]</p>]]></description><guid isPermaLink="false">80</guid><pubDate>Thu, 17 Sep 2026 15:09:01 +0000</pubDate></item><item><title>Nuitka Unpacker Latest Tool</title><link>https://decodehub.org/topic/69-nuitka-unpacker-latest-tool/</link><description><![CDATA[<p>Everything started from my idea to reverse of Nuitka executable is possible and this guy made insane breaktrough and created 5.86mb one file 132k lines file with full decompiling of Nuitka much as possible.</p><p>Static decomplication: </p><p>Dynamic decomplication (older but interesting):  </p><p>
[Hidden Content]</p>]]></description><guid isPermaLink="false">69</guid><pubDate>Mon, 14 Sep 2026 18:59:02 +0000</pubDate></item><item><title>unDUP2 - unpacker for diablo2oo2's Universal Patcher</title><link>https://decodehub.org/topic/24-undup2-unpacker-for-diablo2oo2s-universal-patcher/</link><description><![CDATA[<p>unDUP2 unpacker v0.9.1 | python to C++ port by Stingered (2026)</p><p>Usage:</p><p>Extract and dump the .dup2 and payload DLL to disk from a generated PE created by dUP 2.</p><p>The .dup2 file can be loaded into diabl2oo2's Universal Patcher tool for editing.</p><p>Sample output:</p><p>ndup2 MyPatcher.exe</p><p>unDUP2 unpacker v0.3 | python to C++ port by Stingered (2026)</p><p>original python code: [Hidden Content]</p><p>Usage: unDUP2.exe &lt;file name&gt;</p><p>[+] Generated: MyPatcher.dumped.dll</p><p>[+] Generated: MyPatcher.dUP2</p><p>(2 modules)</p><p>*original python code: [Hidden Content]</p><p>Note: As of now, this only works on Patchers, not Loaders generated by DUP2.</p><p>[Hidden Content]</p>]]></description><guid isPermaLink="false">24</guid><pubDate>Fri, 28 Aug 2026 17:36:25 +0000</pubDate></item><item><title>AgileDotNetSlayer</title><link>https://decodehub.org/topic/86-agiledotnetslayer/</link><description><![CDATA[<p>AgileDotNetSlayer is a simple and open source (GPLv3) deobfuscator for [Hidden Content].<br><br>[Hidden Content]</p><h3><strong>Usage:</strong></h3><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>AgileDotNetSlayer &lt;AssemblyPath&gt;
</code></pre><h3><strong>Supported protections:</strong></h3><ul><li><p>Control Flow</p></li><li><p>String Encryption</p></li><li><p>Resource Encryption</p></li><li><p>Method Call Obfuscation</p></li></ul><h3><strong>Out of scope:</strong></h3><ul><li><p>Code Virtualization (Contact me if you are interested in paid services)</p></li><li><p>Code Encryption</p><p>[Hidden Content]</p></li></ul>]]></description><guid isPermaLink="false">86</guid><pubDate>Thu, 17 Sep 2026 15:32:41 +0000</pubDate></item></channel></rss>
