- Notifications
You must be signed in to change notification settings - Fork51
Modified Cheat Engine DBK64 driver
License
dmarov/chamd
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
This project provides a modified version of the Cheat Engine DBK64 kernel driver aimed at bypassing detection by anti-cheat systems.It has been tested with EAC and BattlEye, potentially working with other systems as well.
Current version is based on Cheat Engine version 7.5
As shown below, the driver successfully bypasses EAC detection in Robocraft.
Even if you manage to use this driver successfully, it does not guarantee that you will not be suspected of cheating.The usage of this software and any actions outlined in this document are entirely at your own risk.
Please note that using these instructionsposes a significant security risk to your system.It is highly recommended to use an isolated computer for this purpose. Additionally, isolating the machine within a local network may further enhance security.
- Operating System: Windows 11 only. This method will not work on Windows 10.
- Disable Anti-Virus Software: Turn off Virus and Threat Protection in Windows settings, as well as any other anti-virus or anti-malware programs. These can block the required files
- InstallCheat Engine 7.5 by compiling it fromsource, which is preferred method, or using theinstaller.
2.1.Download the Compiled DriverVisitGitHub to download the compiled driver, which includes a multibuild file.
2.2.Extract the ArchiveOnce downloaded, extract the archive containing over 1000+ drivers. This extensive number of drivers is strategically provided to minimize the chances of multiple users using the samedriver instance, thereby reducing detection risk.
2.3.Select and Copy the DriverFrom the extracted files, choose any one random driver. Copy all three associated files to the directory wherecheatengine-x86_64.exe
is located.
Why Multiple Drivers?Using a unique driver decreases the chances of your setup being flagged or blacklisted by anti-cheat systems.The way anti-cheat works, is that it develops signatures for popular cheats and flags it in the database. Of cousre there's more to anti-cheat.
For better reliability, consider compiling your own driver following the instructions in Section 7. This process creates a custom driver, reducing the chances ofdetection.
At this point you have driver signed with untrusted certificate.There are a few options to load it.In this section the method based on bypass ofPatchguard andDigital Signature Enforcement will be explained.Refer to section 8 for some extra method.
3.1. Create bootable usb drive
3.1.1. DownloadEfiGuard version >= 1.4.
3.1.2. Mount you usb drive. 2GB drive should be more than enough.
3.1.3. Format your usb drive asFAT32
.be carefull to format the correct device, because it will erase all data on USB drive
3.1.4. Partition your device as bootableGPT
withEFI
partition.be carefull to partition the correct device!!!
Open command prompt as administrator and perform the following commands:
diskpartlist disk // detect your USB driveselectdisk {put number of your USB drive here} // SELECTING CORRECT DISK!!!list disk // make sure correct disk is selectedclean // wipe out your drivecreate partition primary size=512 // create EFI partitionlist partitions // created partition shoud be displayedselectpartition 1 //selectcreated partitionactive // mark partition as activeformat quick fs=fat32 // create filesystemassign // disk should be mountedexit
3.1.5. Copy files to USB drive
CopyEFI
directory from the extracted archive to the root of created partition.
3.1.6. Rename bootloader
LocateEFI/Boot/Loader.efi
on the USB drive, than rename it toEFI/Boot/bootx64.efi
.
3.2. Boot your system from USB drive.
Restart your computer and enter the UEFI settings (usually by pressing F2, F12, or DEL during startup).Set the first boot option to your USB drive (UEFI). The second option should be your windows drive (UEFI).Ensure Secure Boot is disabled since EFIGuard rootkit isn't signed.
3.3. Copy files for digital signature enforcement bypass
3.3.1. In the directory containingcheatengine-x86_64.exe
, create a new file namedrun.bat
with the following content:
"%~dp0\EfiDSEFix.exe" -dstart /d"%~dp0" cheatengine-x86_64.exetimeout /t 20"%~dp0\EfiDSEFix.exe" -e
Before doing that, make sure that file explored is not configured to hide known file extensions.
3.3.2. CopyEfiDSEFix.exe
from the archive to the same directory ascheatengine-x86_64.exe
.
Make sure that
Edit
>Settings
>Extra
>Query memory region routines
is checked
Edit
>Settings
>Extra
>Read/Write process memory
is checked
ClickOK
.
It might end up with errors. Close Cheat Engine.
Runrun.bat
as Administrator.
Do not close the window that pops out manually!!! Wait for it to close automatically.
After the driver has been successfully loaded, you can directly runcheatengine-x86_64.exe
without needing to executerun.bat
.
Runcheatengine-x86_64.exe
You have successfully loaded the DBK64 driver signed with an untrusted certificate.This allows kernel mode anti-cheat (EAC) to permit starting the game and performing operations on thegame memory. Note: The last tested version was confirmed on EAC as of April 19, 2025.
Anti-cheat systems may collect signatures of suspicious drivers used by a small number of users to block them. To mitigate this, it is recommended to compile your own version of thedriver with a unique signature.
Use PowerShell or Cmder for these steps.
7.1. Clone this repository
git clone https://github.com/dmarov/chamd.gitcd chamd
Ensure you have Git installed on your system before cloning.
7.2. Installnodejs. Version>=19
is required.
7.3. Install packagesRun the following command in your terminal:
npm install
This will install all required packages for building the driver.
7.4. Copy.env.tpl
to.env
Create a copy of the template environment file by running:
cp .env.tpl .env
7.5. Optionaly setCHAMD_DBK_DRIVER_NAME
in.env
.
Edit the.env
file and set theCHAMD_DBK_DRIVER_NAME
variable to a unique name if desired.
Example:
CHAMD_DBK_DRIVER_NAME=mysupercooldrv
7.6. Install Visual Studio
InstallVisual Studio 2022 (Community or Enterprise) with support for C++ development.
Ensure you select the following components during installation:
- Desktop Development with C++
- MSVC v143 (C++ Compiler)
7.7. InstallWindows SDK and WDKCarefully follow the instructions from the link. It is important that SDK and WDK have the same version.Correct versions of spectre mitigated libraries should be installed in the process.
7.8. Install openssl. The most straightforward way is to use Chocolatey package manager.
choco install openssl
This command has to be performed as Admininstrator.
7.9. Run build
npm run all
Note:
You can useEV certificateto sign driver. You could skip digital signature enforcement bypass this way. They are costly though and can be revoked when misused.
7.10. Copy all files from the 'dist' directory to directory wherecheatengine-x86_64.exe
is located.
7.11. If you've managed to compile this driver successfully and want to share fewrandomized copies then runnpm run multibuild 10
.dist
directory willcontain10
randomized drivers.
Then go to section 3.
If you want to bypass digital signature enforcement temporarily (for testing purposes only), follow these steps:
8.1. Enable Test Signing Mode:
bcdedit /set testsigning on
This command modifies the boot configuration to allow loading of unsigned or self-signed drivers.
8.2. Reboot Your System:The changes take effect after a system reboot.
8.3. Proceed with Section 4:Load the driver as outlined in section 4.
8.4. Disable Test Signing Mode:After testing, disable test signing mode to restore normal security settings.
bcdedit /set testsigning off
Enabling test signing mode is intended for development and troubleshooting purposes only.It temporarily reduces the system's security by allowing unsigned drivers to load.This method does not work with anti-cheat systems, as they typically enforce strict driver signature requirements.
About
Modified Cheat Engine DBK64 driver
Topics
Resources
License
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Packages0
Uh oh!
There was an error while loading.Please reload this page.