Exetools

Exetools (https://forum.exetools.com/index.php)
-   x64 OS (https://forum.exetools.com/forumdisplay.php?f=44)
-   -   VirtualBox Hardened Loader x64 (kernelmode.info) (https://forum.exetools.com/showthread.php?t=16681)

Insid3Code 05-27-2015 16:29

I Agree with you!

I appreciate a lot his works (old and new) (open source/closed source/PoCs and more...) and specially his coding style (Delphi 5/C/C++/Native API).

Repo recently created!
PHP Code:

https://github.com/hfiref0x?tab=repositories 

Also DrvMon coded together with you, unfortunately (release 2.x not available for public)
PHP Code:

http://www.kernelmode.info/forum/viewtopic.php?f=11&t=217 

Quote:

We decided to do not release newer version (2.x) to the public. Overall it's now completely different application than that attached here.

Ahmed18 08-06-2015 05:04

thanks bro ;)

Sakaroz 01-08-2018 06:04

it doesn't work correctly very unstable .. VMWare Workstation has a lot of secret options by manually editing the .vmx file you can make it almost undetectable .. changing the CPU IDs, disabling the VMWARE Tools, reflecting the host information to virtual machine .. using the Actual Hard drive instead of Virtual Machine controller .. , changing the ethernet mac address, memory addresses, ........ I was unable to get this software to work but by Modifying Vmware using a Custom BIOS I was able to defeat all the targets with virtual machine detection in VMWare Environment ..

TechLord 01-08-2018 11:01

Quote:

Originally Posted by Sakaroz (Post 111806)
it doesn't work correctly very unstable .. VMWare Workstation has a lot of secret options by manually editing the .vmx file you can make it almost undetectable .. changing the CPU IDs, disabling the VMWARE Tools, reflecting the host information to virtual machine .. using the Actual Hard drive instead of Virtual Machine controller .. , changing the ethernet mac address, memory addresses, ........ I was unable to get this software to work but by Modifying Vmware using a Custom BIOS I was able to defeat all the targets with virtual machine detection in VMWare Environment ..

Maybe you can share a sample .VMX file for all of us to know better.

Yes, even I do some of the stuff that you mentioned but a sample VMX file (as well as the custom BIOS taht actually works) as an example would be nice :)

Maybe as a PoC, we can see if it can bypass the Anti-VMWare/VM functions of the VMProtect v3.xx without needing to make any changes to the actual protected executable.
Am sure would be an interesting exercise ...

Thank you..

Stingered 01-10-2018 02:50

Quote:

Originally Posted by TechLord (Post 111810)
Maybe you can share a sample .VMX file for all of us to know better.

Yes, even I do some of the stuff that you mentioned but a sample VMX file (as well as the custom BIOS taht actually works) as an example would be nice :)

Maybe as a PoC, we can see if it can bypass the Anti-VMWare/VM functions of the VMProtect v3.xx without needing to make any changes to the actual protected executable.
Am sure would be an interesting exercise ...

Thank you..

YES!!! Sakaroz, if you could proved a PoC that could be what would make me switch over the VMware.

Sakaroz 01-12-2018 08:51

I will make an article and will share it ..

You can verify your system file with this :
https://github.com/LordNoteworthy/al-khaser

there are two main difficulty .. assigning actual hard drive to virtual machine to avoid using the VMWare IDE/SCSI/SATA Controller

and BIOS patching .. you need to extract the BIOS and Change the VMWare values in the BIOS , modify the .vmx file to read your modified BIOS ..

I will share everything in that article ..

TechLord 01-12-2018 10:40

Quote:

Originally Posted by Sakaroz (Post 111852)
You can verify your system file with this :
https://github.com/LordNoteworthy/al-khaser

...

Yes, I'd shared that on this very forum at least twice ... Here and here for example :)



Quote:

Originally Posted by Sakaroz (Post 111852)
there are two main difficulty .. assigning actual hard drive to virtual machine to avoid using the VMWare IDE/SCSI/SATA Controller

and BIOS patching .. you need to extract the BIOS and Change the VMWare values in the BIOS , modify the .vmx file to read your modified BIOS ..
..

Yes, not only me but many others are also aware of these practical difficulties ... After all, this is a forum for members advanced in RE :)

What I ( and I presume others following this thread) are looking for, is mainly an account of how you actually managed to achieve it, so that we could possibly replicate it .

Articles are numerous and while they are useful, since you'd specifically stated earlier in this thread that "I was unable to get this software to work but by Modifying Vmware using a Custom BIOS I was able to defeat all the targets with virtual machine detection in VMWare Environment .. " , we are looking to see a practical example of how you managed to accomplish it...

In fact, content from this repo is still relevant but seems to fail when attempting to bypass the VM Check of VMP 3.1 ..
These steps still continue to work on a majority of targets...

As I said earlier, a good PoC would be if you could show us an example of how a VM Check of an executable protected with VMProtect >v3.1 could be bypassed without any modification to the executable (or to its image in memory using a loader etc) itself, as we are already well aware of how to do so when we are allowed to patch the executable or its memory space.

Thank you :)


All times are GMT +8. The time now is 04:08.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX