Exetools - 【 Reproduction】VMProtect Leaked Source Code Full

Exetools (https://forum.exetools.com/index.php)

- Source Code (https://forum.exetools.com/forumdisplay.php?f=46)

- - 【 Reproduction】VMProtect Leaked Source Code Full (https://forum.exetools.com/showthread.php?t=20778)

【 Reproduction】VMProtect Leaked Source Code Full

h-t-t-ps://www.lanzoul.com/iyzIC1h3acxc

h-t-t-ps://pixeldrain.com/u/fKn1dZqK

Just in case the link is dead I upload it here.

package includes missing intel.cc file!

Quote:

Originally Posted by WhoCares (Post 129496)

leak of the year?

I think the shared zip archive is this repo:

Code:

https://github.com/jmpoep/vmprotect-3.5.1

Git is missing files and folders

Quote:

Originally Posted by blue_devil (Post 129499)

I think the shared zip archive is this repo:

Code:

https://github.com/jmpoep/vmprotect-3.5.1

If you need original content, then download full archive and not from GitHub.

The person who uploaded the archive content to GitHub didn't check the `.gitignore' file, so the public git repo is missing some files from the original archive.

Quote:

Originally Posted by blue_devil (Post 129495)

package includes missing intel.cc file!

core contain intel.cc not the right one?

Quote:

Originally Posted by bolo2002 (Post 129503)

core contain intel.cc not the right one?

included in git package, with 'processors.cc' and 'licensing_manager.cc', etc.

Could anyone get this to compile?
Details from anyone who could get it to successfully compile?

It appears to be the source files from the VMP source code leak earlier in May this year with the missing processors.cc and others added in from other sources.
Can anyone confirm that this is the source for the actual VMP 3.5.1?

The dates of file have been changed to show year 1970 but check the html files in the "help" folder.
The copyright dates in the html files show that they are all actually from around 2015. No later.

According to sh3dow's post, the very first leak already has some missing parts:

Quote:

intel.cc
arm.cc
arm.h
processors.cc
gcc-demangle.cc
gcc-demangle.h
msvc-demangle.cc
msvc-demangle.h
dprint.c
dprint.h
def.h

The latest leak/link contains some of those above:

Code:

| file             | Shared: 12/05/2023 | Shared: 07/12/2023 |

|------------------+--------------------+--------------------|

| intel.cc         | no                 | yes                |

| arm.cc           | no                 | no                 |

| arm.h            | no                 | no                 |

| processors.cc    | no                 | yes                |

| gcc-demangle.cc  | no                 | no                 |

| gcc-demangle.h   | no                 | no                 |

| msvc-demangle.cc | no                 | no                 |

| msvc-demangle.h  | no                 | no                 |

| dprint.c         | no                 | no                 |

| dprint.h         | no                 | no                 |

| def.h            | no                 | no                 |

Quote:

Originally Posted by th3tuga (Post 129507)

Could anyone get this to compile?
Details from anyone who could get it to successfully compile?
....

i maked next steps for GIT release:
redirected projects from vs2008 to vs2010, from v141_xp to v140_xp, dotnet from 4.8 to 4.7.2 ans start compile with the vs2015.

console,

Code:

...\vmprotect-3.5.1-master\bin\32\Ultimate>VMProtectCon.exe

VMProtect Ultimate v 1.0.0 (build 0) Copyright 2003-2021 VMProtect Software

Unregistered Version



Usage: VMProtectCon.exe File [Output File] [-pf Project File] [-sf Script File] [-lf Licensing parameters file] [-bd Build Date (yyyy-mm-dd)] [-wmatermark] [-we]

libs, dlls and utilities also is compiled.

swears on the runtime source Win32.cs
type designs
NtQueryInformationProcess(CurrentProcess, PROCESSINFOCLASS.ProcessDebugObjectHandle, out _, IntPtr.Size, out _)
but we can fix it =)

or when there is an announcement in the Win32.cs public
class IntelObfuscation : public IObject
{
public:
explicit IntelObfuscation();
void Compile(IntelFunction *func, size_t index);
...
}
and then in the body:
void IntelObfuscation::Compile(IntelFunction *func, size_t index, size_t end_index = -1, bool for_virtualization = false)
{
...
}

maybe for dotnet 4.8 is fine, but 4.7.2 give error for me.

for the GUI version you need QT headers and libs...

@FoxB Can you post compilable code with fixes as zip? Fails completely with VS 2022.

The QT 5.6 have to be installed the same way the author installed it or the GUI version will not compile.

Anyone know if this is the same as listed here? https://breachforums.is/Thread-FREE-VMProtect-Source-Code-LEAK

same sources as previous leak, no any file changed
have compared today