{"id":38528190,"url":"https://github.com/dmarov/chamd","last_synced_at":"2026-01-18T13:46:12.702Z","repository":{"id":40327958,"uuid":"387022688","full_name":"dmarov/chamd","owner":"dmarov","description":"Modified Cheat Engine DBK64 driver","archived":false,"fork":false,"pushed_at":"2025-04-23T15:06:13.000Z","size":2931,"stargazers_count":249,"open_issues_count":5,"forks_count":57,"subscribers_count":10,"default_branch":"master","last_synced_at":"2026-01-17T17:28:22.516Z","etag":null,"topics":["driver","eac","windows"],"latest_commit_sha":null,"homepage":"","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/dmarov.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2021-07-17T19:30:55.000Z","updated_at":"2026-01-09T15:27:21.000Z","dependencies_parsed_at":"2025-04-18T20:24:49.741Z","dependency_job_id":"f81437e9-4fba-4bd8-bffe-e8dcff47a363","html_url":"https://github.com/dmarov/chamd","commit_stats":null,"previous_names":[],"tags_count":4,"template":false,"template_full_name":null,"purl":"pkg:github/dmarov/chamd","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dmarov%2Fchamd","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dmarov%2Fchamd/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dmarov%2Fchamd/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dmarov%2Fchamd/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/dmarov","download_url":"https://codeload.github.com/dmarov/chamd/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dmarov%2Fchamd/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28536804,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-18T13:04:05.990Z","status":"ssl_error","status_checked_at":"2026-01-18T13:01:44.092Z","response_time":98,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["driver","eac","windows"],"created_at":"2026-01-17T06:50:46.065Z","updated_at":"2026-01-18T13:46:12.669Z","avatar_url":"https://github.com/dmarov.png","language":"C","readme":"# Chamd (Chameleon DBK64)\n\n## Modified Driver Based on Cheat Engine DBK64\n\nThis project provides a modified version of the Cheat Engine DBK64 kernel driver aimed at bypassing detection by anti-cheat systems.\nIt has been tested with EAC and BattlEye, potentially working with other systems as well.\n\nCurrent version is based on Cheat Engine version 7.5\n\n![screen](images/screen.png \"Screen\")\n*As shown below, the driver successfully bypasses EAC detection in Robocraft.*\n\n## 0. Important Warning\n\nEven if you manage to use this driver successfully, it does not guarantee that you will not be suspected of cheating.\nThe usage of this software and any actions outlined in this document are entirely at your own risk.\n\nPlease note that using these instructions **poses a significant security risk** to your system.\nIt is highly recommended to use an isolated computer for this purpose. Additionally, isolating the machine within a local network may further enhance security.\n\n## 1. System Requirements and Preparation\n- **Operating System**: Windows 11 only. This method will not work on Windows 10.\n- **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\n- Install **Cheat Engine 7.5** by compiling it from [source](https://github.com/cheat-engine/cheat-engine/releases/tag/7.5), which is preferred method, or using the [installer](https://www.cheatengine.org/downloads.php).\n\n## 2. Obtain your driver\n\n2.1. **Download the Compiled Driver**\nVisit [GitHub](https://github.com/dmarov/chamd/releases/tag/v1.4) to download the compiled driver, which includes a multibuild file.\n\n2.2. **Extract the Archive**\nOnce 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 same\ndriver instance, thereby reducing detection risk.\n\n2.3. **Select and Copy the Driver**\nFrom the extracted files, choose any one random driver. Copy all three associated files to the directory where `cheatengine-x86_64.exe` is located.\n\nWhy Multiple Drivers?\nUsing a unique driver decreases the chances of your setup being flagged or blacklisted by anti-cheat systems.\nThe 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.\n\nFor better reliability, consider compiling your own driver following the instructions in Section 7. This process creates a custom driver, reducing the chances of\ndetection.\n\n## 3. Bypassing **Digital Signature Enforcement**\n\nAt this point you have driver signed with untrusted certificate.\nThere are a few options to load it.\nIn this section the method based on bypass of **Patchguard** and **Digital Signature Enforcement** will be explained.\nRefer to section 8 for some extra method.\n\n- [Video tutorial 1](https://www.youtube.com/watch?v=EJGuJp2fqpM)\n- [Video tutorial 2](https://www.youtube.com/watch?v=zsw3xoG3zgs)\n\n3.1. Create bootable usb drive\n\n3.1.1. Download [EfiGuard](https://github.com/Mattiwatti/EfiGuard/releases/) version \u003e= 1.4.\n\n3.1.2. Mount you usb drive. 2GB drive should be more than enough.\n\n3.1.3. Format your usb drive as `FAT32`. **be carefull to format the correct device**, because it will erase all data on USB drive\n\n3.1.4. Partition your device as bootable `GPT` with `EFI` partition.\n**be carefull to partition the correct device!!!**\n\nOpen command prompt as administrator and perform the following commands:\n\n```shell\ndiskpart\nlist disk // detect your USB drive\nselect disk {put number of your USB drive here} // SELECTING CORRECT DISK!!!\nlist disk // make sure correct disk is selected\nclean // wipe out your drive\ncreate partition primary size=512 // create EFI partition\nlist partitions // created partition shoud be displayed\nselect partition 1 // select created partition\nactive // mark partition as active\nformat quick fs=fat32 // create filesystem\nassign // disk should be mounted\nexit\n```\n\n3.1.5. Copy files to USB drive\n\nCopy `EFI` directory from the extracted archive to the root of created partition.\n\n3.1.6. Rename bootloader\n\nLocate `EFI/Boot/Loader.efi` on the USB drive, than rename it to `EFI/Boot/bootx64.efi`.\n\n3.2. Boot your system from USB drive.\n\nRestart your computer and enter the UEFI settings (usually by pressing F2, F12, or DEL during startup).\nSet the first boot option to your USB drive (UEFI). The second option should be your windows drive (UEFI).\nEnsure Secure Boot is disabled since EFIGuard rootkit isn't signed.\n\n3.3. Copy files for digital signature enforcement bypass\n\n3.3.1. In the directory containing `cheatengine-x86_64.exe`, create a new file named `run.bat` with the following content:\n\n```shell\n\"%~dp0\\EfiDSEFix.exe\" -d\nstart /d \"%~dp0\" cheatengine-x86_64.exe\ntimeout /t 20\n\"%~dp0\\EfiDSEFix.exe\" -e\n```\n\nBefore doing that, make sure that file explored is not configured to hide known file extensions.\n\n3.3.2. Copy `EfiDSEFix.exe` from the archive to the same directory as `cheatengine-x86_64.exe`.\n\n## 4. Configure Cheat Engine\n\nMake sure that\n\n`Edit` \u003e `Settings` \u003e `Extra` \u003e `Query memory region routines` is checked\n\n`Edit` \u003e `Settings` \u003e `Extra` \u003e `Read/Write process memory` is checked\n\nClick `OK`.\n\nIt might end up with errors. Close Cheat Engine.\n\n## 5. Run Cheat Engine.\n\n### If you followed section 3:\n\nRun `run.bat` as Administrator.\n\nDo not close the window that pops out manually!!! Wait for it to close automatically.\n\nAfter the driver has been successfully loaded, you can directly run `cheatengine-x86_64.exe` without needing to execute `run.bat`.\n\n### If you followed section 8:\n\nRun `cheatengine-x86_64.exe`\n\n## 6. Congratulations\n\nYou have successfully loaded the DBK64 driver signed with an untrusted certificate.\nThis allows kernel mode anti-cheat (EAC) to permit starting the game and performing operations on the\ngame memory. Note: The last tested version was confirmed on EAC as of April 19, 2025.\n\n## 7. [Extra] Compile the driver from source\n\nAnti-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 the\ndriver with a unique signature.\n\n#### **Note:**\nUse PowerShell or Cmder for these steps.\n\n[Video Tutorial](https://www.youtube.com/watch?v=7ARwpxZPpE8)\n\n7.1. Clone this repository\n\n```shell\ngit clone https://github.com/dmarov/chamd.git\ncd chamd\n```\n\nEnsure you have Git installed on your system before cloning.\n\n7.2. Install [nodejs](https://nodejs.org/en/). Version `\u003e=19` is required.\n\n7.3. Install packages\nRun the following command in your terminal:\n\n```shell\nnpm install\n```\n\nThis will install all required packages for building the driver.\n\n7.4. Copy `.env.tpl` to `.env`\nCreate a copy of the template environment file by running:\n\n```shell\ncp .env.tpl .env\n```\n\n7.5. Optionaly set `CHAMD_DBK_DRIVER_NAME` in `.env`.\n\nEdit the `.env` file and set the `CHAMD_DBK_DRIVER_NAME` variable to a unique name if desired.\n\nExample:\n```env\nCHAMD_DBK_DRIVER_NAME=mysupercooldrv\n```\n\n7.6. Install Visual Studio\n\nInstall **Visual Studio 2022** (Community or Enterprise) with support for C++ development.\n\n[Download Visual Studio](https://visualstudio.microsoft.com/downloads/)\n\nEnsure you select the following components during installation:\n- **Desktop Development with C++**\n- **MSVC v143 (C++ Compiler)**\n\n7.7. Install [Windows SDK and WDK](https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk)\nCarefully follow the instructions from the link. It is important that SDK and WDK have the same version.\nCorrect versions of spectre mitigated libraries should be installed in the process.\n\n7.8. Install openssl. The most straightforward way is to use Chocolatey package manager.\n\n```shell\nchoco install openssl\n```\n\nThis command has to be performed as Admininstrator.\n\n7.9. Run build\n\n```shell\nnpm run all\n```\n\nNote:\n\nYou can use [EV certificate](https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/code-signing-cert-manage)\nto sign driver. You could skip digital signature enforcement bypass this way. They are costly though and can be revoked when misused.\n\n7.10. Copy all files from the 'dist' directory to directory where `cheatengine-x86_64.exe`\nis located.\n\n7.11. If you've managed to compile this driver successfully and want to share few\nrandomized copies then run `npm run multibuild 10`. `dist` directory will\ncontain `10` randomized drivers.\n\nThen go to section 3.\n\n## 8. [Extra] Another Method of dealing with *Digital Signature Enforcement*\n\nIf you want to bypass digital signature enforcement temporarily (for testing purposes only), follow these steps:\n\n8.1. Enable Test Signing Mode:\n```shell\nbcdedit /set testsigning on\n```\nThis command modifies the boot configuration to allow loading of unsigned or self-signed drivers.\n\n8.2. Reboot Your System:\nThe changes take effect after a system reboot.\n\n8.3. Proceed with Section 4:\nLoad the driver as outlined in section 4.\n\n8.4. Disable Test Signing Mode:\nAfter testing, disable test signing mode to restore normal security settings.\n```shell\nbcdedit /set testsigning off\n```\n\nEnabling test signing mode is intended for development and troubleshooting purposes only.\nIt temporarily reduces the system's security by allowing unsigned drivers to load.\nThis method does not work with anti-cheat systems, as they typically enforce strict driver signature requirements.\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdmarov%2Fchamd","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdmarov%2Fchamd","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdmarov%2Fchamd/lists"}