<?xml version="1.0"?>
<rss version="2.0"><channel><title>Debuggers Latest Topics</title><link>https://decodehub.org/forum/28-debuggers/</link><description>Debuggers Latest Topics</description><language>en</language><item><title>KozVM v1.0 &#x2014; VMProtect Anti-Anti-VM Plugin for x64dbg (No Kernel Driver Required)</title><link>https://decodehub.org/topic/157-kozvm-v10-vmprotect-anti-anti-vm-plugin-for-x64dbg-no-kernel-driver-required/</link><description><![CDATA[<p>After going through the VMProtect anti-VM checks version by version, I put the handling into an x64dbg plugin.</p><p>This is <strong>KozVM v1.0</strong>. It covers the researched versions from <strong>VMProtect 3.3.1 to 3.10.1</strong>, with a separate profile for each tested version.</p><p><strong>No kernel driver is required.</strong> The plugin runs inside x64dbg in user mode. It handles supported checks in the debugged process without changing the VM configuration globally.</p><p>Native <strong>x64 targets only</strong> for now. x32 development has not started.</p><p>[Hidden Content] · [Hidden Content]<br></p><h2>The demo</h2><p>One small test program here: <strong>BasicProbe</strong>.</p><p>The video starts with protecting it using different VMProtect versions. Then I open the protected files inside VirtualBox under x64dbg, select the matching KozVM profile and run them.</p><p>[Hidden Content]<br></p><h2>Supported versions</h2><div class="ipsRichText__table-wrapper"><table style="min-width: 505px;"><colgroup><col style="min-width:20px;"><col style="min-width:20px;"><col style="min-width:20px;"><col style="width:445px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>VMProtect</p></th><th colspan="1" rowspan="1"><p>Profile ID</p></th><th colspan="1" rowspan="1"><p>x64</p></th><th colspan="1" rowspan="1"><p>Handling</p></th></tr><tr><td colspan="1" rowspan="1"><p>3.3.1</p></td><td colspan="1" rowspan="1"><p>331</p></td><td colspan="1" rowspan="1"><p>Tested</p></td><td colspan="1" rowspan="1"><p>CPUID checks</p></td></tr><tr><td colspan="1" rowspan="1"><p>3.4.0</p></td><td colspan="1" rowspan="1"><p>340</p></td><td colspan="1" rowspan="1"><p>Tested</p></td><td colspan="1" rowspan="1"><p>CPUID checks</p></td></tr><tr><td colspan="1" rowspan="1"><p>3.5.0</p></td><td colspan="1" rowspan="1"><p>350</p></td><td colspan="1" rowspan="1"><p>Tested</p></td><td colspan="1" rowspan="1"><p>CPUID checks</p></td></tr><tr><td colspan="1" rowspan="1"><p>3.6.0</p></td><td colspan="1" rowspan="1"><p>360</p></td><td colspan="1" rowspan="1"><p>Tested</p></td><td colspan="1" rowspan="1"><p>Version-specific CPUID flow</p></td></tr><tr><td colspan="1" rowspan="1"><p>3.8.0</p></td><td colspan="1" rowspan="1"><p>380</p></td><td colspan="1" rowspan="1"><p>Tested</p></td><td colspan="1" rowspan="1"><p>Version-specific CPUID flow</p></td></tr><tr><td colspan="1" rowspan="1"><p>3.9.4</p></td><td colspan="1" rowspan="1"><p>394</p></td><td colspan="1" rowspan="1"><p>Tested</p></td><td colspan="1" rowspan="1"><p>CPUID, firmware scanner and Sandboxie module query</p></td></tr><tr><td colspan="1" rowspan="1"><p>3.10.1</p></td><td colspan="1" rowspan="1"><p>3101</p></td><td colspan="1" rowspan="1"><p>Tested</p></td><td colspan="1" rowspan="1"><p>CPUID, firmware scanner and Sandboxie module query</p></td></tr></tbody></table></div><p>All seven listed versions were tested with our protected x64 samples. This does not mean every intermediate VMProtect build or every protected program was tested.</p><p>KozVM does not select the VMProtect version automatically. Select the profile for the version you are working with.<br></p><hr><h2><br>Installation</h2><p>Download [Hidden Content]. With x64dbg closed, copy the contents of the archive's plugins folder into the plugins directory next to x64dbg.exe:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>plugins/
    KozVM.dp64
    KozVM.dp64.ini
    KozVM/
        unicorn.dll
        COPYING
        COPYING.LGPL2
        README.txt</code></pre><p><strong>Do not copy only KozVM.dp64.</strong> Keep the KozVM runtime directory beside it. This contains Unicorn, which is used for fast discovery.</p><p>Unicorn requires the Microsoft Visual C++ x64 runtime. Python is not required to use the plugin.</p><p>Start x64dbg. <strong>KozVM x64</strong> should appear under Plugins.</p><p><img src="https://i.ibb.co/Nn1B7v6t/image.png" alt="KozVM plugin menu" class="ipsRichText__align--block" width="161" height="30" loading="lazy"></p><p>The default profile is <strong>3.3.1</strong>, with auto-enable turned on. Change the profile before loading a target protected with another version.</p><h2><br>Selecting a profile</h2><p>Select the version directly from <strong>Plugins &gt; KozVM x64</strong>. There is no need to open Settings every time.</p><p><img src="https://i.ibb.co/KzpymM4s/image.png" alt="KozVM profile selection" class="ipsRichText__align--block" width="206" height="307" loading="lazy"></p><p>Load the program after selecting the profile. At the system breakpoint, check the profile and setup messages in the log, then press <strong>F9</strong>. If x64dbg stops at the protected entry point or a TLS entry point, press F9 again.</p><p><strong>If setup fails, read the error before continuing. Selecting a profile after the program has already performed its checks cannot undo those checks.</strong><br></p><hr><h2><br>The settings</h2><p>The settings window exposes the individual options. Hover over the question mark beside a checkbox for a short explanation.</p><p><img src="https://i.ibb.co/dw6dggL9/image.png" alt="KozVM settings" class="ipsRichText__align--block" width="492" height="416" loading="lazy"></p><p><strong>Enable KozVM</strong><br>Enables or disables the plugin.</p><p><strong>Auto-enable on start</strong><br>Automatically enables the selected profile when a new debugging session starts.</p><p><strong>CPUID compatibility</strong><br>Handles the supported CPUID-based anti-VM checks.</p><p><strong>Firmware scanner</strong><br>Handles the firmware scanner in the 3.9.4 and 3.10.1 profiles.</p><p><strong>Sandboxie module (sbiedll.dll)</strong><br>Handles the Sandboxie module query in the 3.9.4 and 3.10.1 profiles. Sandboxie does not need to be installed.</p><p>The firmware and Sandboxie options are available only for the applicable profiles. They are greyed out for the others.</p><p>Use <strong>Save &amp; apply</strong> to save your settings. Pause a running target before applying them.</p><p><strong>No kernel component is installed. The handling applies to the target process inside the debugger.</strong><br></p><hr><h2><br>Addresses and startup speed</h2><p>The plugin discovers control points in the loaded program. It does not select targets by filename, hash or a sample-specific fixed address.</p><p>Monitoring many pages during protected startup can produce a large number of debugger events and make startup slow.</p><p>KozVM uses <strong>Unicorn</strong> for bounded emulation of an isolated memory snapshot to discover CPUID sites. It then follows those sites in the live target using hardware breakpoints.</p><p>This discovery does not emulate a complete Windows environment. Unrecognized paths can fall back to slower guarded discovery, which is reported in the log.</p><p>Available hardware-breakpoint slots and the protected code layout can affect setup. Different protection settings can also change startup time. Passing these examples is not a guarantee for every protected executable.<br></p><hr><h2><br>Profiles and saved settings</h2><p>Each supported version has its own profile:</p><p>331 / 340 / 350 / 360 / 380 / 394 / 3101</p><p>The selected profile, auto-enable setting and check options are saved in <strong>KozVM.dp64.ini</strong>, next to the plugin.</p><p>The INI stores settings. It does not contain the complete implementation for a new VMProtect version. Adding a new check or version requires changing the C++ source and rebuilding.<br></p><h2>Updating</h2><p>Close x64dbg completely before replacing files. Copy over the updated plugin and runtime files.</p><p><strong>Keep your existing KozVM.dp64.ini.</strong> Replacing it with the default file discards your saved settings.<br></p><hr><h2><br>What this tool does</h2><p>KozVM handles the anti-VM checks covered by its profiles. Once those checks pass, you can continue examining the program in the debugger.</p><p>It does not unpack the executable, remove code virtualization or bypass the program's password check. It is a separate project from [Hidden Content], which handles anti-debug checks.</p><p>The source is available under <strong>GPLv2</strong>. The release source package also includes the corresponding Unicorn sources and license texts.</p><p><img src="https://i.ibb.co/4nwYzxQh/image.png" alt="About KozVM" class="ipsRichText__align--block" width="412" height="211" loading="lazy"></p><h2>Anti-VM analyses</h2><p>The implementation follows these analyses:</p><ul><li><p>[Hidden Content]</p></li><li><p>[Hidden Content]</p></li><li><p>[Hidden Content]</p></li></ul><h2>Links and contact</h2><p>[Hidden Content] · [Hidden Content] · [Hidden Content]</p><p>For bug reports, include the VMProtect version, protection options, selected profile and relevant KozVM logs.</p><p>[Hidden Content]<br></p><hr><h5 style="text-align:center;"><span data-ips-font-size="200"><span style='font-family: Georgia, "Times New Roman", serif;'> </span></span><strong><span data-ips-font-size="200"><span style='font-family: Georgia, "Times New Roman", serif;'>IVAN KOZLOVSKY</span></span></strong><span data-ips-font-size="200"><span style='font-family: Georgia, "Times New Roman", serif;'> </span></span></h5><p style="text-align:center;">Discord: kariexscontxct<br><a rel="" href="mailto:contact@ivankozlovsky.com">contact@ivankozlovsky.com</a> - [Hidden Content]</p>]]></description><guid isPermaLink="false">157</guid><pubDate>Sun, 15 Nov 2026 14:10:31 +0000</pubDate></item><item><title>KozDbg v1.1.2 &#x2014; VMProtect Anti-Anti-Debug Plugin for x64dbg (No Kernel Driver Required)</title><link>https://decodehub.org/topic/133-kozdbg-v112-vmprotect-anti-anti-debug-plugin-for-x64dbg-no-kernel-driver-required/</link><description><![CDATA[<p>After going through the VMProtect anti-debug checks version by version, I put the handling into a plugin for x64dbg and x32dbg.</p><p>This is <strong>KozDbg v1.1.2</strong>. It covers the researched versions from <strong>VMProtect 3.3.1 to 3.10.1</strong>, with a separate profile for each tested version.</p><p><strong>No kernel driver is required.</strong> The plugin runs inside x64dbg or x32dbg and handles the supported user-mode checks and kernel-debugger queries from user mode. Native <strong>x64 and x32</strong> targets are supported. The x32 build runs under WOW64 on 64-bit Windows. <strong>Neither build needs a kernel driver, including the 3.10.1 profile.</strong></p><p>[Hidden Content] · [Hidden Content]<br></p><h2>The demo</h2><p>Three small programs here: BasicProbe, RiddleGame and KeyCheck.</p><p>The video starts with protecting them using the different VMProtect versions. Then I open the protected files in x64dbg, select the matching KozDbg profile and run them.<br><br>[Hidden Content]</p><p>The x32 demo shows protected 32-bit programs running in x32dbg with the matching KozDbg profiles.</p><p>[Hidden Content]</p><h2><br>Supported versions</h2><div class="ipsRichText__table-wrapper"><table style="min-width: 100px;"><colgroup><col style="min-width:20px;"><col style="min-width:20px;"><col style="min-width:20px;"><col style="min-width:20px;"><col style="min-width:20px;"></colgroup><tbody><tr><th colspan="1" rowspan="1" style="text-align: left;"><p>VMProtect</p></th><th colspan="1" rowspan="1" style="text-align: left;"><p>Profile ID</p></th><th colspan="1" rowspan="1" style="text-align: left;"><p>x64</p></th><th colspan="1" rowspan="1" style="text-align: left;"><p>x32</p></th><th colspan="1" rowspan="1" style="text-align: left;"><p>x64 handling</p></th></tr><tr><td colspan="1" rowspan="1" style="text-align: left;"><p>3.3.1</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p><code>331</code></p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>API interception</p></td></tr><tr><td colspan="1" rowspan="1" style="text-align: left;"><p>3.4.0</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p><code>340</code></p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>API interception</p></td></tr><tr><td colspan="1" rowspan="1" style="text-align: left;"><p>3.5.0</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p><code>350</code></p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>API interception</p></td></tr><tr><td colspan="1" rowspan="1" style="text-align: left;"><p>3.6.0</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p><code>360</code></p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Clustered direct syscalls</p></td></tr><tr><td colspan="1" rowspan="1" style="text-align: left;"><p>3.8.0</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p><code>380</code></p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Scattered direct syscalls</p></td></tr><tr><td colspan="1" rowspan="1" style="text-align: left;"><p>3.9.4</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p><code>394</code></p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Scattered direct syscalls and extended checks</p></td></tr><tr><td colspan="1" rowspan="1" style="text-align: left;"><p>3.10.1</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p><code>3101</code></p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Tested</p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>Scattered direct syscalls and extended checks</p></td></tr></tbody></table></div><p>All seven listed versions were tested with both x64 and x32 programs, including samples with additional protection options. These are the actual tested versions. The 3.3.x–3.10.x range does not mean every intermediate build was tested.</p><p>The handling column describes the x64 build. In x32, later profiles also track WOW64 transitions into native code using hardware breakpoints and memory guards. A free hardware slot is needed for the return; existing user breakpoints are retained.</p><p>KozDbg does not detect the VMProtect version automatically. Select the profile for the version you are working with.<br></p><h2>Installation</h2><p>For x64, download [Hidden Content] and extract the three files into the <code>plugins</code> directory next to <code>x64dbg.exe</code>:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>plugins/
    KozDbg.dp64
    KozDbg.dp64.ini
    KozDbg.dp64.ini.profiles.ini
</code></pre><p>For x32, download [Hidden Content] and extract the two files into the <code>plugins</code> directory next to <code>x32dbg.exe</code>:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>plugins/
    KozDbg.dp32
    KozDbg.dp32.ini
</code></pre><p>Start the matching debugger. The Plugins menu should contain KozDbg in x64dbg or KozDbg x32 in x32dbg. Each build uses its own INI files.</p><p>The screenshots below show the x64 build. Available x32 controls depend on the selected profile.</p><p><img src="https://i.ibb.co/pjqpXrmd/image.png" alt="KozDbg plugin menu" class="ipsRichText__align--block" width="122" height="28" loading="lazy"></p><p>The package starts with the 3.3.1 profile and auto-enable turned on. Change the profile before loading a target protected with another version.</p><h2>Selecting a profile</h2><p>You can select the version directly from <strong>Plugins &gt; KozDbg</strong> in x64dbg or <strong>Plugins &gt; KozDbg x32</strong> in x32dbg. There is no need to open the settings window every time.</p><p><img src="https://i.ibb.co/99J5TPmq/image.png" alt="image" class="ipsRichText__align--block" width="176" height="279" loading="lazy"></p><p>Load the program after selecting the profile. At the system breakpoint, check that KozDbg reports the profile as armed, then press F9. If the debugger stops at the protected entry point or a TLS entry point, press F9 again.</p><p>If setup fails, read the error before continuing. Selecting a profile after the program has already performed its checks cannot undo those checks.</p><h2><br>The settings</h2><p>The settings window exposes the individual options. Hover over the question mark beside a checkbox for a short explanation.</p><p><img src="https://i.ibb.co/VpqmwmkM/image.png" alt="image" class="ipsRichText__align--block" width="562" height="460" loading="lazy"></p><p>The available controls depend on the selected version:</p><ul><li><p>PEB and debugger API checks.</p></li><li><p>Remote debugger, debug object and kernel debugger queries.</p></li><li><p>Thread hiding, driver names and supported invalid-handle checks.</p></li><li><p>Trap-flag exception delivery and saved debug registers.</p></li><li><p>Instrumentation callback and remote-breakin protection in later profiles.</p></li><li><p>The TitanHide device check in 3.9.4 and 3.10.1.</p></li><li><p>Decoder acceleration for recognized packed layouts in the x64 build.</p></li></ul><p>The kernel-debugger option handles the query result seen by the protected program. It does not install a kernel component.</p><p>The TitanHide option also does not require TitanHide. It handles the device-open check used by those later VMProtect versions.</p><h2><br>Addresses and packed programs</h2><p>The plugin resolves API addresses and syscall numbers in the running process. It does not select targets by filename, hash or a fixed protected-code address.</p><p>One issue appeared when testing the packed 3.3.1 RiddleGame. Breakpoints at the start of native API stubs changed bytes the protected startup depended on. Moving the interception point past the validated syscall-identification prefix allowed the program to reach its GUI. The older profiles now use that placement too.</p><p>Packing can also make the direct-syscall path slow. A memory guard on a page shared with a busy decoder loop causes a lot of debugger events.</p><p>In x64, decoder acceleration handles recognized layouts using available hardware-breakpoint slots. If it cannot allocate one safely, the memory-guard path remains in use. Startup can be slower in that case.</p><p>The x32 build does not have a separate decoder-acceleration option. WOW64 transition handling is selected by the version profile.</p><p>Different protection settings can produce different layouts, so passing these examples is not a guarantee for every protected executable.</p><h2><br>Custom profiles</h2><p>In the x64 build, click <strong>Profiles INI</strong> in Settings. The file is <code>KozDbg.dp64.ini.profiles.ini</code>, next to the plugin.</p><p>Copy an existing section, give it a unique ID and change its name and options. For example, start from the 331 preset if you want another configuration of the API engine.</p><p>Restart x64dbg after editing profile definitions. Your new profile appears in the menu and settings dropdown.</p><p>The INI configures the existing handling. It does not contain the entire implementation. Adding a new check requires changing the C++ source and rebuilding the plugin.</p><p>The x32 build stores settings for its seven built-in profiles in <code>KozDbg.dp32.ini</code>. Change the checkboxes and use <strong>Save &amp; apply</strong> to save them. Custom named profiles and the x64 profile-definition file are not used by the x32 build.</p><p>The full format is in the repository's [Hidden Content].</p><h2><br>Commands</h2><p>The same controls are available from the command bar in x64dbg and x32dbg:</p><pre spellcheck="" class="ipsCode language-plaintext" data-language="Plain Text"><code>kz_settings
kz_profile 331
kz_status
</code></pre><p><code>kz_profile MyProfile</code> selects a custom named profile in the x64 build only.</p><p><code>kz_apply</code> applies the current profile while the target is paused. <code>kz_profile off</code> disables the plugin.</p><p>Repeated informational messages are counted instead of printed continuously. <code>kz_status</code> shows the state and counters. Errors still appear; the debugger's own exception messages are separate.</p><h2><br>Updating</h2><p>Close x64dbg completely before replacing <code>KozDbg.dp64</code>, or x32dbg before replacing <code>KozDbg.dp32</code>.</p><p>Keep your existing INI files when updating. Replacing them with the defaults would discard your saved settings and custom profiles.</p><h2><br>What this tool does</h2><p>KozDbg handles the anti-debug checks covered by its profiles. Once startup passes, you continue with normal debugging.</p><p>It does not unpack the executable, remove virtualization or bypass the program's password check.</p><p>The source is available under the MIT license.</p><p><img src="https://i.ibb.co/RTFz90Gb/image.png" alt="image" class="ipsRichText__align--block" width="241" height="237" loading="lazy"></p><h2>Anti-debug analyses</h2><p>The implementation follows these analyses:</p><ul><li><p>[Hidden Content]</p></li><li><p>[Hidden Content]</p></li><li><p>[Hidden Content]</p></li><li><p>[Hidden Content]</p></li><li><p>[Hidden Content]</p></li></ul><h2><br>Links and contact</h2><p>[Hidden Content]<br>[Hidden Content] · [Hidden Content] · [Hidden Content] · [Hidden Content]</p><hr><h3 style="text-align:center;"><em><span style='font-family: Georgia, "Times New Roman", serif;'>IVAN KOZLOVSKY</span></em></h3><p style="text-align:center;"><span style="font-family: Helvetica, Arial, sans-serif;">Discord: kariexscontxct</span><br><a rel="" href="mailto:contact@ivankozlovsky.com">contact@ivankozlovsky.com</a><span style="font-family: Helvetica, Arial, sans-serif;"> - </span>[Hidden Content]</p>]]></description><guid isPermaLink="false">133</guid><pubDate>Thu, 29 Oct 2026 20:03:01 +0000</pubDate></item><item><title>x64dbg Assembly Code Translation Plugin</title><link>https://decodehub.org/topic/89-x64dbg-assembly-code-translation-plugin/</link><description><![CDATA[<p>In the past:</p><p>To understand assembly code, you first had to learn the assembly language itself, which was difficult for beginners.</p><p>Now:</p><p>With Doubao (a Chinese translation tool), beginners can easily copy and paste assembly code.</p><p>Therefore, I created an x64dbg plugin that implements this translation function to help all beginners understand assembly language.</p><p>## Plugin Name: AsmTranslator</p><p>## Function:</p><p>Adds a quick assembly code translation feature to x32dbg/x64dbg using Doubao for intelligent translation. Specifically: AsmTranslator.dp32 is for 32-bit programs; AsmTranslator.dp64 is for 64-bit programs.</p><p>## The results are as follows:<br><img class="ipsImage ipsImage_thumbnailed ipsRichText__align--block" data-fileid="120" src="https://decodehub.org/uploads/monthly_2026_09/150523uhrhze3z3ampd3ms.thumb.jpg.7cf53698b81c838defabd6f259d4958e.jpg" alt="150523uhrhze3z3ampd3ms.jpg" title="" width="1000" height="585" data-full-image="https://decodehub.org/uploads/monthly_2026_09/150523uhrhze3z3ampd3ms.jpg.8ed468069321be3ef19725062f78da8f.jpg" loading="lazy"></p><p>## Usage Instructions:</p><p>Step 1: Place the AsmTranslator.dp32 and AsmTranslator.dp64 files into the plugin directories of x32dbg and x64dbg, respectively.</p><p>Step 2: After loading the x32dbg or x64dbg program, select the code snippet you wish to analyze, right-click, and select the "Copy Assembly Code" option from the AsmTranslator plugin menu.</p><p>Step 3: Open Doubao, start a new chat, press CTRL+V within the chat, and click Send. Select the entire translated output from Doubao (address + Chinese translation) and press CTRL+C to copy it.</p><p>Step 4: Return to x32dbg or x64dbg, right-click, select the "Add Translation Comment" option from the AsmTranslator plugin menu, paste the translated code from Doubao into the Notepad window that appears by pressing CTRL+V, and click Save. This plugin is a small tool I wrote on a whim, designed for beginners; please overlook any shortcomings.</p><p><img class="ipsImage ipsImage_thumbnailed ipsRichText__align--block" data-fileid="121" src="https://decodehub.org/uploads/monthly_2026_09/152750vawxw6earlblw101.thumb.jpg.8e81055abb1dd5ddcf81c8d5ddeb830d.jpg" alt="152750vawxw6earlblw101.jpg" title="" width="1000" height="519" data-full-image="https://decodehub.org/uploads/monthly_2026_09/152750vawxw6earlblw101.jpg.83714a9f732b448573f5fe1439469831.jpg" loading="lazy"></p><p>[Hidden Content]</p>]]></description><guid isPermaLink="false">89</guid><pubDate>Thu, 17 Sep 2026 15:48:43 +0000</pubDate></item><item><title>Scylla v0.12.0 (x86/x64, EXE/DLL - 10/10/26, Self-compiled)</title><link>https://decodehub.org/topic/126-scylla-v0120-x86x64-exedll-101026-self-compiled/</link><description><![CDATA[<p>Note: Fork of Scylla with additional fixes and Python bindings.</p><p>*compiled binaries are not provided on the external [Hidden Content]site.</p><p>Scylla - x64/x86 Imports Reconstruction</p><p>This repository contains a fork of NtQuery/Scylla with tweaks from x64dbg/Scylla as well as additional </p><p>fixes, refactoring and bindings.</p><p>Scylla's key features:</p><p>x64 and x86 support</p><p>Unicode support</p><p>Plugin support</p><p>Works on Windows 7 and superior</p><p>License</p><p>Source code is licensed under GNU GENERAL PUBLIC LICENSE v3.0.</p><p>Known Bugs</p><p>Windows 7 x64</p><p>Sometimes the API kernel32.dll GetProcAddress cannot be resolved, because the IAT has an entry from apphelp.dll.</p><p>ImpREC plugin support</p><p>Some ImpREC Plugins don't work with Windows Vista/7 because they don't "return 1" in the DllMain function.</p><p>Stingered (2026)</p><p>
[Hidden Content]</p>]]></description><guid isPermaLink="false">126</guid><pubDate>Sat, 10 Oct 2026 19:33:56 +0000</pubDate></item><item><title>VMP (2.x) analysis plugin for OllyDBG</title><link>https://decodehub.org/topic/119-vmp-2x-analysis-plugin-for-ollydbg/</link><description><![CDATA[<p>v1.4</p><p>Detailed information included in the RAR file (too large to post here, translation from Chinese).</p><p>
[Hidden Content]</p>]]></description><guid isPermaLink="false">119</guid><pubDate>Tue, 29 Sep 2026 14:36:50 +0000</pubDate></item></channel></rss>
