A GitHub repository published under the username chriscodex1989b0 has released a prebuilt external cheat for the game Deadlock, labeled ‘Deadlock Cheat 2026’. The tool targets Windows 10 and 11 64-bit systems and includes features such as bone-level ESP (extra-sensory perception), aimbot, and soul auto-deny. It is distributed as a portable ZIP package requiring no compilation, lowering the barrier to use for non-developers.
The cheat operates as a native 64-bit application with no external dependencies. It uses a hot-reloadable JSON configuration file (config/settings.json), allowing users to adjust settings without restarting the program. The included release, version 1.2.0, supports DirectX 11 and 12 through a borderless overlay and runs with administrator privileges. A panic key (END) enables immediate unloading, reducing detection risk.
Technical architecture and capabilities
The cheat is modular, with distinct subsystems for rendering, input processing, and entity detection. The viewport overlay uses a DX11/DX12 composition swapchain with DPI scaling, designed to remain undetectable by blending into the game’s visual output. Entity and loot filtering rely on spatial bounding boxes, distance and health readouts, and rarity-based culling (configurable via min_rarity_tier). Input smoothing applies human-like curves within a set FOV radius, adjustable through the config.
The configuration file exposes key parameters: frame rate cap (144 FPS), VSync off, toggle key (INSERT), and compact HUD mode. Modules can be enabled or disabled individually, giving users fine control over behaviour and visibility. The low-overhead runtime suggests optimisation for performance-sensitive environments, typical of modern anti-cheat evasion strategies.
Distribution and accessibility
The tool is distributed via GitHub Releases as deadlock-cheat-v1.2.0-win64.zip, accompanied by a SHA256SUMS.txt checksum file for integrity verification. Users are instructed to extract the archive, keep the config file adjacent to the executable, and run it as administrator. No installation or terminal use is required, making it accessible even to technically inexperienced players.
The repository includes full source code (under src/ and config/), buildable using CMake, but explicitly positions the prebuilt release as the primary distribution method. This model mirrors trends in underground cheat development, where open code fosters trust while precompiled binaries maximise reach.
Anti-cheat implications and platform risks
As an external, user-mode overlay with memory reading and input manipulation, this tool likely violates Deadlock’s terms of service and may trigger detection by kernel-level anti-cheat systems such as BattlEye or Easy Anti-Cheat if memory access patterns are identified. However, its design—modular structure, runtime configurability, and clean unloading—suggests efforts to avoid heuristic or behavioural flags.
The use of JSON hot-reload and configurable FOV/smoothing may help mimic human variance, reducing the risk of pattern-based detection. Still, any unauthorised runtime injection or overlay in a competitive environment carries a high ban risk, particularly in ranked modes.
What it means
For game developers and platform operators, the appearance of such tools underscores the ongoing arms race between cheat developers and anti-cheat systems. The use of portable, configuration-driven external cheats lowers distribution friction and complicates detection. For players, the availability of prebuilt cheats threatens fair play and long-term game integrity.
Businesses involved in competitive gaming, esports, or game development should monitor such repositories not for adoption but for threat modelling. Understanding cheat architectures helps improve detection logic and safeguard user trust. In regions like the UK, UAE, US, and Kazakhstan, where digital entertainment and esports are growing, protecting game integrity is increasingly a technical and commercial priority.
The cheat’s open availability does not imply endorsement or legality. Its use may result in account suspension or legal action, depending on jurisdiction and platform policy. Developers are advised to avoid integrating or testing such tools in production environments.