Skip to content
View in the app

A better way to browse. Learn more.

DECODEHUB - Software and reverse engineering community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Decodehub.org rank system
New badge system

KozDbg v1.1.2 — VMProtect Anti-Anti-Debug Plugin for x64dbg (No Kernel Driver Required)

Featured Replies

After going through the VMProtect anti-debug checks version by version, I put the handling into a plugin for x64dbg and x32dbg.

This is KozDbg v1.1.2. It covers the researched versions from VMProtect 3.3.1 to 3.10.1, with a separate profile for each tested version.

No kernel driver is required. The plugin runs inside x64dbg or x32dbg and handles the supported user-mode checks and kernel-debugger queries from user mode. Native x64 and x32 targets are supported. The x32 build runs under WOW64 on 64-bit Windows. Neither build needs a kernel driver, including the 3.10.1 profile.

This is the hidden content, please
·
This is the hidden content, please

The demo

Three small programs here: BasicProbe, RiddleGame and KeyCheck.

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.

This is the hidden content, please

The x32 demo shows protected 32-bit programs running in x32dbg with the matching KozDbg profiles.

This is the hidden content, please


Supported versions

VMProtect

Profile ID

x64

x32

x64 handling

3.3.1

331

Tested

Tested

API interception

3.4.0

340

Tested

Tested

API interception

3.5.0

350

Tested

Tested

API interception

3.6.0

360

Tested

Tested

Clustered direct syscalls

3.8.0

380

Tested

Tested

Scattered direct syscalls

3.9.4

394

Tested

Tested

Scattered direct syscalls and extended checks

3.10.1

3101

Tested

Tested

Scattered direct syscalls and extended checks

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.

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.

KozDbg does not detect the VMProtect version automatically. Select the profile for the version you are working with.

Installation

For x64, download

This is the hidden content, please
and extract the three files into the plugins directory next to x64dbg.exe:

plugins/
    KozDbg.dp64
    KozDbg.dp64.ini
    KozDbg.dp64.ini.profiles.ini

For x32, download

This is the hidden content, please
and extract the two files into the plugins directory next to x32dbg.exe:

plugins/
    KozDbg.dp32
    KozDbg.dp32.ini

Start the matching debugger. The Plugins menu should contain KozDbg in x64dbg or KozDbg x32 in x32dbg. Each build uses its own INI files.

The screenshots below show the x64 build. Available x32 controls depend on the selected profile.

KozDbg plugin menu

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.

Selecting a profile

You can select the version directly from Plugins > KozDbg in x64dbg or Plugins > KozDbg x32 in x32dbg. There is no need to open the settings window every time.

image

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.

If setup fails, read the error before continuing. Selecting a profile after the program has already performed its checks cannot undo those checks.


The settings

The settings window exposes the individual options. Hover over the question mark beside a checkbox for a short explanation.

image

The available controls depend on the selected version:

  • PEB and debugger API checks.

  • Remote debugger, debug object and kernel debugger queries.

  • Thread hiding, driver names and supported invalid-handle checks.

  • Trap-flag exception delivery and saved debug registers.

  • Instrumentation callback and remote-breakin protection in later profiles.

  • The TitanHide device check in 3.9.4 and 3.10.1.

  • Decoder acceleration for recognized packed layouts in the x64 build.

The kernel-debugger option handles the query result seen by the protected program. It does not install a kernel component.

The TitanHide option also does not require TitanHide. It handles the device-open check used by those later VMProtect versions.


Addresses and packed programs

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.

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.

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.

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.

The x32 build does not have a separate decoder-acceleration option. WOW64 transition handling is selected by the version profile.

Different protection settings can produce different layouts, so passing these examples is not a guarantee for every protected executable.


Custom profiles

In the x64 build, click Profiles INI in Settings. The file is KozDbg.dp64.ini.profiles.ini, next to the plugin.

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.

Restart x64dbg after editing profile definitions. Your new profile appears in the menu and settings dropdown.

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.

The x32 build stores settings for its seven built-in profiles in KozDbg.dp32.ini. Change the checkboxes and use Save & apply to save them. Custom named profiles and the x64 profile-definition file are not used by the x32 build.

The full format is in the repository's

This is the hidden content, please
.


Commands

The same controls are available from the command bar in x64dbg and x32dbg:

kz_settings
kz_profile 331
kz_status

kz_profile MyProfile selects a custom named profile in the x64 build only.

kz_apply applies the current profile while the target is paused. kz_profile off disables the plugin.

Repeated informational messages are counted instead of printed continuously. kz_status shows the state and counters. Errors still appear; the debugger's own exception messages are separate.


Updating

Close x64dbg completely before replacing KozDbg.dp64, or x32dbg before replacing KozDbg.dp32.

Keep your existing INI files when updating. Replacing them with the defaults would discard your saved settings and custom profiles.


What this tool does

KozDbg handles the anti-debug checks covered by its profiles. Once startup passes, you continue with normal debugging.

It does not unpack the executable, remove virtualization or bypass the program's password check.

The source is available under the MIT license.

image

Anti-debug analyses

The implementation follows these analyses:


Links and contact

This is the hidden content, please

This is the hidden content, please
·
This is the hidden content, please
·
This is the hidden content, please
·
This is the hidden content, please


IVAN KOZLOVSKY

Discord: kariexscontxct
[email protected] -

This is the hidden content, please

Edited by ivankozlovsky
Version update

  • Replies 42
  • Views 2.3k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Stingered
    Stingered

    @ivankozlovsky Good to see ypu here! v1.0.1 is out! D/L This is the hidden content, please Sign In or 637805da6

  • ivankozlovsky
    ivankozlovsky

    KozDbg v1.1.2 is out. Added x32 support alongside x64. Tested VMProtect 3.3.1, 3.4.0, 3.5.0, 3.6.0, 3.8.0, 3.9.4 and 3.10.1 on both architectures. Fixed the startup pause in the 3.6 x32 profile. Fi

  • I appreciate you, my friend; thanks for your contributions to our website.

30 minutes ago, ivankozlovsky said:

Rica ederim cambaz bey, o şahıssız bir forum çok daha temiz gözüküyor.

Daha yeni tanıdım seni hoşgeldin :) evet artık aramızda olmayacak yedeklerimizi kaybettik sorumsuz ortaklar yüzünden tekrar toparlanacağız inşallah

PROFESSIONAL

Thanks for sharing!
21 hours ago, ivankozlovsky said:

After going through the VMProtect anti-debug checks version by version, I put the handling into an x64dbg plugin.

This is KozDbg v1.0. It covers the researched versions from VMProtect 3.3.1 to 3.10.1, with a separate profile for each tested version.

No kernel driver is required. The plugin runs inside x64dbg and handles the supported user-mode checks and kernel-debugger queries from user mode. Native x64 targets only.

Hidden Content
Give reaction AND comment to see this hidden content!

·

Hidden Content
Give reaction AND comment to see this hidden content!


The demo

Three small programs here: BasicProbe, RiddleGame and KeyCheck.

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.

Hidden Content
Give reaction AND comment to see this hidden content!


Supported versions

VMProtect

Profile ID

Handling

3.3.1

331

API interception

3.4.0

340

API interception

3.5.0

350

API interception

3.6

360

Clustered direct syscalls

3.8.0

380

Scattered direct syscalls

3.9.4

394

Scattered direct syscalls and extended checks

3.10.1

3101

Scattered direct syscalls and extended checks

These are the actual tested versions. The 3.3.x–3.10.x range does not mean every intermediate build was tested.

KozDbg does not detect the VMProtect version automatically. Select the profile for the version you are working with.

Installation

Download

Hidden Content
Give reaction AND comment to see this hidden content!

and extract the three files into the plugins directory next to x64dbg.exe:

plugins/
    KozDbg.dp64
    KozDbg.dp64.ini
    KozDbg.dp64.ini.profiles.ini


Start x64dbg. KozDbg should appear under Plugins.

KozDbg plugin menu

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.

Selecting a profile

You can select the version directly from Plugins > KozDbg. There is no need to open the settings window every time.

image

Load the program after selecting the profile. At the system breakpoint, check that KozDbg reports the profile as armed, then press F9. If x64dbg stops at the protected entry point or a TLS entry point, press F9 again.

If setup fails, read the error before continuing. Selecting a profile after the program has already performed its checks cannot undo those checks.


The settings

The settings window exposes the individual options. Hover over the question mark beside a checkbox for a short explanation.

image

The available controls depend on the selected version:

  • PEB and debugger API checks.

  • Remote debugger, debug object and kernel debugger queries.

  • Thread hiding, driver names and supported invalid-handle checks.

  • Trap-flag exception delivery and saved debug registers.

  • Instrumentation callback and remote-breakin protection in later profiles.

  • The TitanHide device check in 3.9.4 and 3.10.1.

  • Decoder acceleration for recognized packed layouts.

The kernel-debugger option handles the query result seen by the protected program. It does not install a kernel component.

The TitanHide option also does not require TitanHide. It handles the device-open check used by those later VMProtect versions.


Addresses and packed programs

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.

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.

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.

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.

Different protection settings can produce different layouts, so passing these examples is not a guarantee for every protected executable.


Custom profiles

Click Profiles INI in Settings. The file is KozDbg.dp64.ini.profiles.ini, next to the plugin.

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.

Restart x64dbg after editing profile definitions. Your new profile appears in the menu and settings dropdown.

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.

The full format is in the repository's

Hidden Content
Give reaction AND comment to see this hidden content!

.


Commands

The same controls are available from the command bar:

kz_settings
kz_profile 331
kz_profile MyProfile
kz_status

kz_apply applies the current profile while the target is paused. kz_profile off disables the plugin.

Repeated informational messages are counted instead of printed continuously. kz_status shows the state and counters. Errors still appear; x64dbg's own exception messages are separate.


Updating

Close x64dbg completely before replacing KozDbg.dp64.

Keep your existing INI files when updating. Replacing them with the defaults would discard your saved settings and custom profiles.


What this tool does

KozDbg handles the anti-debug checks covered by its profiles. Once startup passes, you continue with normal debugging.

It does not unpack the executable, remove virtualization or bypass the program's password check.

The source is available under the MIT license.

image

Anti-debug analyses

The implementation follows these analyses:

  • Hidden Content
    Give reaction AND comment to see this hidden content!

  • Hidden Content
    Give reaction AND comment to see this hidden content!

  • Hidden Content
    Give reaction AND comment to see this hidden content!

  • Hidden Content
    Give reaction AND comment to see this hidden content!

  • Hidden Content
    Give reaction AND comment to see this hidden content!


Links and contact

Hidden Content
Give reaction AND comment to see this hidden content!


Hidden Content
Give reaction AND comment to see this hidden content!

·

Hidden Content
Give reaction AND comment to see this hidden content!

·

Hidden Content
Give reaction AND comment to see this hidden content!



IVAN KOZLOVSKY

Discord: kariexscontxct
[email protected] -

Hidden Content
Give reaction AND comment to see this hidden content!

Thank you for sharing things like that.

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.