Enderman
โœ”
5.72K subscribers
388 photos
25 videos
7 files
140 links
A software engineer, a malware enthusiast and most importantly, a weird tall creature.

https://enderman.ch
https://youtube.com/endermanch
Download Telegram
Channel created
This media is not supported in your browser
VIEW IN TELEGRAM
๐Ÿคฏ128๐Ÿค”19โค14โšก5๐Ÿ‘Ž5๐Ÿคฉ4๐Ÿ˜ฑ3๐Ÿ‘2๐Ÿคฌ1
Hello everyone, Enderman here. This is the first post on this channel. I'll think of something more interesting to post later on. ๐Ÿ˜‰

https://malwarewatch.org
๐Ÿ‘114๐ŸŽ‰15โค10๐Ÿ”ฅ10๐ŸŒš9โšก7๐Ÿคฏ5๐Ÿ˜ฑ3๐Ÿคฌ2๐Ÿ‘Ž1
๐Ÿงช Beyond the limitations of the Virtual Environment I

It doesn't matter if you're an amateur malware tester or a professional cyber-sec expert, you've surely had a problem where a sample just wouldn't run on your virtual environment, be it a Sandbox, or a Virtual Machine. Regardless of your struggle, there exists a common technique used to detect any suspicious environment, and it allows for developers to filter hardware their applications can run on, be it for malicious or defensive purposes. It's commonly called an Anti-VM and there are various proprietary and open-source solutions (e. g. VMProtect, Safengine) providing a wide range of application protection utilities.

Despite all the expenses developers go for to secure their application, the Anti-VM mechanisms are very predictable and relatively easy to bypass. Their weakest point is the fact that a virtual environment isn't so much different from a real one. The only potential fruitful ways to detect a virtual environment are hardware signatures and drivers for that specific set of hardware. Some cheeky paid tools go as far as searching for generic patterns and strings in the local network, known VM files in your system directory, but such checks are far more strict and can't ever warrant a Virtual Machine on the other end.

I will not get into technical side of things in this post, and we don't really need them to bypass basic Anti-VM checks and evade even some of the paid solutions out there. Essentially, we will be cooking up an Anti-Anti-VM environment to trick pesky programs to run without the need of real hardware.

The cornerstone of that endeavor will be the VMware Hardened Loader by hzqst. As the name suggests, you will need a VMware machine to pull this off. I'll boil down the tutorial to a few simple steps down below. You can find the original text in the readme file attached in the repository.

โ–ช๏ธ Create a virtual machine with a SCSI hard disk
โ–ช๏ธ Replace all the optical drives with SCSI ones
๐Ÿ”ป Paste the following settings inside the .vmx file of your newly created VM:

    hypervisor.cpuid.v0 = "FALSE"
board-id.reflectHost = "TRUE"
hw.model.reflectHost = "TRUE"
serialNumber.reflectHost = "TRUE"
smbios.reflectHost = "TRUE"
SMBIOS.noOEMStrings = "TRUE"
isolation.tools.getPtrLocation.disable = "TRUE"
isolation.tools.setPtrLocation.disable = "TRUE"
isolation.tools.setVersion.disable = "TRUE"
isolation.tools.getVersion.disable = "TRUE"
monitor_control.disable_directexec = "TRUE"
monitor_control.disable_chksimd = "TRUE"
monitor_control.disable_ntreloc = "TRUE"
monitor_control.disable_selfmod = "TRUE"
monitor_control.disable_reloc = "TRUE"
monitor_control.disable_btinout = "TRUE"
monitor_control.disable_btmemspace = "TRUE"
monitor_control.disable_btpriv = "TRUE"
monitor_control.disable_btseg = "TRUE"
monitor_control.restrict_backdoor = "TRUE"

They will minimize the hardware signature presence inside your VM.
Now you want to rename virtual drives to remove VMware from their name:

    scsi0:0.productID = "Samsung SSD"
scsi0:0.vendorID = "Samsung"
scsi0:X.productID = "Matshita DVD-RAM" // X is the DVD slot
scsi0:X.vendorID = "Matshita"

The rest of the steps are in the next post.
๐Ÿคฏ44๐Ÿ‘17โค4๐Ÿค”3โšก2๐Ÿ˜2๐Ÿ˜ฑ1๐Ÿคฌ1
๐Ÿงช Beyond the limitations of the Virtual Environment II

๐Ÿ”ป Open NAT settings, click Advanced and modify the MAC address. The MAC address cannot start with the following sequences (they signify VMware):

    00:05:69
00:0C:29
00:1C:14
00:50:56

โ–ช๏ธ Install any 64-bit Windows version starting from Vista on the VM.
โ–ช๏ธ DO NOT INSTALL VMWARE TOOLS, that defeats the purpose of this project.
โ–ช๏ธ Use ISO files and your virtual SCSI optical drive to transfer data between the host and guest. Despite the inconvenience and added hassle, it adds another layer of isolation, which is always good when you're working with malware.
โ–ช๏ธ Download the repository and transfer the 3 files from the bin folder to your VM. Place vmloader.sys inside the root of the C:\ drive and open install.bat with administrator rights. It will install the virtual signature remover as a service to your virtual system.
โ–ช๏ธ Reboot your machine. Last, but not least, open the registry editor and search for "VMware". You may find lots of values referring to VMware, but the only one that can actually trigger the Anti-VM mechanism is the BIOS Information, or something along these lines. If you do find it, go ahead and change the value to American Megatrends or anything else that comes to your mind first.

Once you've completed all the steps listed here, you should be golden. Now that your virtual machine is tweaked accordingly, the apps with Anti-VM integrated should run perfectly fine, as if that's real hardware.

I will definitely make a video on that topic soon. Hope you learned something interesting, happy circumventing!

@endermanch
๐Ÿ‘50๐Ÿคฏ9โšก8๐Ÿคฉ4๐Ÿค”3โค2๐Ÿ˜ฑ1๐Ÿคฌ1
๐Ÿ Python 3.10.1 for Windows 7

In case you're still running Windows 7, which is a great operating system, you might have noticed the developers are slowly but surely starting to drop Windows 7 compatibility for arguably more convenient API that was introduced with Windows 8.

The project aims to bring the newest Python features back to Windows 7, which isn't a painstakingly difficult thing to do, considering localizing and reverting the syntax sugar API from Windows 8 to improve backwards compatibility is simply trial and error until you get the interpreter running. Patience and understanding are the key.

Nonetheless, I'm happy NulAsh spent hours worth of elbow grease to treat us with a powerful tool, developers of which weren't patient enough to hold onto Windows 7 for a little bit more, until its official ESU end of life, which will occur on January 10th, 2023.

๐Ÿ“Ž Download here!
๐Ÿ˜35๐Ÿ‘14โšก8๐Ÿ‘7โค4๐ŸŽ‰3๐Ÿคฌ1
This media is not supported in your browser
VIEW IN TELEGRAM
420 subscribers ๐Ÿ˜„
๐Ÿ‘72๐Ÿคฉ18โค13๐ŸŽ‰11๐Ÿ˜9๐Ÿค”8๐Ÿ‘5โšก4๐Ÿ‘Ž4๐Ÿ˜ฑ4๐Ÿคฌ1
๐Ÿคฏ161๐Ÿ‘24๐Ÿ˜ฑ15๐Ÿค”14๐Ÿคฉ10โšก7๐Ÿ˜7๐Ÿ‘5โค4๐ŸŽ‰2๐Ÿคฌ1
Update your Windows XP computer in 2022

Do you still own an older Windows computer that you'd like to fully update, but don't want to spend your time manually searching for the packages?
You can get the free robust update manager at https://legacyupdate.net/

That's an awesome community project that brings Windows Update back to life.
๐Ÿคฏ72๐Ÿ‘13๐Ÿคฉ6โšก4๐Ÿ‘3๐Ÿ˜ฑ3๐Ÿค”2๐Ÿ˜1๐Ÿคฌ1๐ŸŽ‰1
And by the way, MERRY CHRISTMAS, my fellow subscribers! ๐ŸŽ„๐Ÿ”ฅ
๐ŸŽ‰97โค26โšก4๐Ÿ˜3๐Ÿ‘1๐Ÿ‘1๐Ÿคฌ1
๐Ÿคฏ108๐Ÿ˜26๐Ÿค”10๐Ÿคฉ9๐Ÿคฌ5โšก4๐Ÿ‘4๐Ÿ‘3โค1
This is what happens when you try to load Windows Boot Manager on 4MB of RAM.
๐Ÿ‘59๐Ÿคฏ31๐Ÿ˜ฑ6๐Ÿ˜5โšก3๐Ÿ‘2๐Ÿค”2๐Ÿคฌ1๐Ÿคฉ1
๐Ÿ‘51๐Ÿคฏ43โšก12โค9๐Ÿ˜5๐Ÿ˜ฑ1๐Ÿคฌ1๐Ÿ˜ข1
Happy new 2023! ๐Ÿ˜Ž๐ŸคŸ
๐ŸŽ‰118๐Ÿ‘18โšก8๐Ÿคฉ5๐Ÿคฏ3๐Ÿ˜ข2๐Ÿค”1๐Ÿคฌ1