mirror of
https://github.com/gmh5225/awesome-game-security
synced 2026-06-21 13:56:22 +00:00
Add archived descriptions for Y-Z repositories
Co-authored-by: gmh5225.eth <gmh5225@users.noreply.github.com>
This commit is contained in:
@@ -0,0 +1,4 @@
|
||||
Phoenix-Valorant-Cheat is an external Valorant cheat project focused on ESP, aimbot, and rage-mode style features.
|
||||
It is implemented mainly in C++ with a Visual Studio solution and uses OpenGL/GLFW plus ImGui for rendering the on-screen menu and overlay.
|
||||
The codebase includes offset definitions, vector math utilities, and external memory-interaction logic commonly used in Windows game hacking tools.
|
||||
Its primary use case is game security research and experimentation with external cheat architecture for Riot's shooter environment.
|
||||
@@ -0,0 +1,4 @@
|
||||
nigusFN is a Fortnite external cheat source that recreates the nigusFN-style interface and feature set.
|
||||
The project is written in C++ for Windows and uses DirectX9 and ImGui for menu rendering, with additional driver and utility components.
|
||||
Its structure includes item definitions, configuration headers, and menu logic typically used in external cheat frameworks.
|
||||
The repository is mainly useful for game security researchers studying external cheat UI design and EAC-oriented tooling workflows.
|
||||
@@ -0,0 +1,4 @@
|
||||
ue4_base is a C++ Unreal Engine 4 cheat base that provides reusable SDK wrappers and hook infrastructure.
|
||||
It hooks UE4 rendering paths such as PostRender with MinHook and exposes helpers for world, actor, and canvas interactions.
|
||||
The code uses libraries like lazy_importer and xorstr, and demonstrates world-to-screen drawing of in-game actors.
|
||||
Its main use case is game security research and rapid prototyping of external or internal UE4 analysis tools.
|
||||
@@ -0,0 +1,4 @@
|
||||
fastDbg is a high-speed x64 ELF debugger implemented in Go for Linux environments.
|
||||
It supports breakpoint management, memory inspection, register operations, disassembly, and ptrace-based process control from a command interface.
|
||||
The project also includes eBPF tracing support and QEMU-related modules for advanced low-level analysis workflows.
|
||||
Its primary audience is reverse engineers and security researchers who need a lightweight but feature-rich debugging toolchain.
|
||||
@@ -0,0 +1,4 @@
|
||||
YimMenu is now a documentation-focused repository for Lua scripting interfaces and support features related to the menu ecosystem.
|
||||
The original source code was removed, and the remaining content centers on Lua API references, command documentation, and utility guides.
|
||||
It includes practical setup instructions for services such as LibreTranslate used by the chat translation feature.
|
||||
The repository is most useful for script developers and users maintaining Lua-based extensions rather than core menu development.
|
||||
@@ -0,0 +1,4 @@
|
||||
Florida is an automation project that patches upstream Frida and builds an anti-detection variant of frida-server for Android.
|
||||
It contains patch sets that modify recognizable Frida strings, symbols, and artifact naming to reduce straightforward detection signatures.
|
||||
The repository focuses on scripted patch application and reproducible build workflows around Frida core components.
|
||||
Its main use case is mobile reverse-engineering research where analysts test anti-instrumentation and anti-detection techniques.
|
||||
@@ -0,0 +1,4 @@
|
||||
hardware-breakpoint is a Linux kernel project for ARM64 that implements configurable hardware breakpoints through exported APIs and proc interfaces.
|
||||
It supports adding and removing execution or watch breakpoints by symbol or address, listing active breakpoints, and collecting trigger statistics.
|
||||
The project also provides utilities to resolve symbol values and map physical IO addresses to related virtual mappings.
|
||||
Its primary use case is kernel-level debugging and security research on Android or embedded systems that require fine-grained runtime monitoring.
|
||||
@@ -0,0 +1,4 @@
|
||||
Anti-Debugger-Protector-Loader is a Windows C++ anti-debugging and protection example project.
|
||||
It continuously scans for debugger executables, window titles, and related drivers, and includes multiple debugger-detection checks with optional automatic termination behavior.
|
||||
The implementation includes configurable scan intervals and optional protection actions, along with VMProtect SDK integration artifacts.
|
||||
Its main audience is software protection and game security researchers studying practical anti-debugging patterns.
|
||||
+4
@@ -0,0 +1,4 @@
|
||||
Rust-Auto-Weapon-Detection-OpenCV-Example is a sample project that demonstrates automatic weapon detection for Rust using OpenCV.
|
||||
It is written in C++ and includes Visual Studio project files, image assets, and code for color filtering and weapon index mapping.
|
||||
The implementation shows a basic computer-vision pipeline for screen-based state recognition rather than direct game memory manipulation.
|
||||
Its primary use case is educational experimentation with CV-assisted game automation and telemetry tooling.
|
||||
@@ -0,0 +1,4 @@
|
||||
Dwm-Overlay is a Windows C++ overlay framework that combines DWM/DirectX rendering with an ImGui-based interface.
|
||||
The project includes low-level hook components, including assembly stubs for dispatch interception and present-path handling.
|
||||
Its code structure provides a minimal base for external overlay drawing, UI widgets, and runtime hook integration.
|
||||
The primary use case is graphics-hooking research and prototyping overlay tooling in game security contexts.
|
||||
@@ -0,0 +1,4 @@
|
||||
gzdoom is a modder-friendly source port of the classic Doom engine with modern OpenGL and Vulkan rendering support.
|
||||
The codebase is primarily C and C++, spans many engine subsystems, and is distributed under GPLv3 with active community maintenance.
|
||||
It provides tooling and infrastructure for gameplay extensions, content mods, scripting, and cross-platform engine development.
|
||||
Its core use case is open-source game engine and modding work, and it is relevant to researchers analyzing real-world game runtime architecture.
|
||||
@@ -0,0 +1,4 @@
|
||||
Overwatch-2-TOPE-EXTERNAL-CHEAT is a C++ external cheat framework targeting Overwatch 2.
|
||||
It includes configurable aimbot and visual overlay functionality, with ImGui rendering helpers and numerous gameplay tuning options.
|
||||
The project also provides memory access utilities, pattern-scanning routines, offsets, and Windows input handling in a Visual Studio setup.
|
||||
Its primary audience is game security researchers examining external cheat design and reverse-engineering workflows.
|
||||
@@ -0,0 +1,4 @@
|
||||
bloodhunt_External is a C++ external cheat project for Bloodhunt built as a Visual Studio solution.
|
||||
It combines an ImGui and DirectX9 overlay layer with memory-access helpers, offsets, and configuration headers for runtime targeting.
|
||||
The repository also includes mhyprot-related driver utility components that support low-level process interaction patterns used by external tools.
|
||||
Its primary use case is game security research into external cheat architecture and anti-cheat evasion-oriented implementation details.
|
||||
@@ -0,0 +1,4 @@
|
||||
CS2-External is a Counter-Strike 2 external cheat project implemented in C#.
|
||||
It emphasizes a read-only memory model with overlay drawing and includes helper modules for entities, offsets, view matrices, and runtime cheat logic.
|
||||
The solution also contains authentication and subscription handling components alongside the core gameplay feature code.
|
||||
Its intended use case is educational exploration of external game memory analysis and overlay-based tooling for CS2.
|
||||
@@ -0,0 +1,4 @@
|
||||
UE4Injector is a proof-of-concept C++ injector that demonstrates an Unreal Engine 4 vulnerability for loading shellcode or DLL payloads into target game processes.
|
||||
It ships as a Visual Studio project with command-line usage patterns, build guidance, and practical notes about privilege requirements and deployment.
|
||||
The repository documents how the injection workflow works and frames the code as legacy research that may still affect unpatched UE4 titles.
|
||||
Its main use case is security research into UE4 process-injection vectors and their anti-cheat implications.
|
||||
Reference in New Issue
Block a user