mirror of
https://github.com/gmh5225/awesome-game-security
synced 2026-06-21 13:56:22 +00:00
Add 15 archive-based English project descriptions
Co-authored-by: gmh5225.eth <gmh5225@users.noreply.github.com>
This commit is contained in:
@@ -0,0 +1,4 @@
|
||||
Malimite is a desktop decompiler tool for analyzing iOS IPA files and macOS application bundles.
|
||||
It is primarily written in Java and built around Ghidra-based decompilation workflows.
|
||||
The project includes features such as automatic Apple resource decoding, Swift class reconstruction, and support for Swift and Objective-C binaries.
|
||||
Its main use case is reverse engineering and security research on Apple applications, including malware analysis and code auditing.
|
||||
@@ -0,0 +1,4 @@
|
||||
Shellcrypt is a cross-platform shellcode obfuscation utility that transforms raw payload bytes into ready-to-paste source code formats.
|
||||
It is implemented in Python and supports multiple encryption ciphers including AES, ChaCha20, RC4, Salsa20, and XOR variants.
|
||||
The tool can chain encoding and compression stages, then emit output for languages such as C, C#, Go, Rust, Nim, Python, and PowerShell.
|
||||
It is mainly used in offensive security and game security research workflows for payload packing, format conversion, and loader prototyping.
|
||||
@@ -0,0 +1,4 @@
|
||||
Lazenca S is an Android anti-cheating engine designed to detect common game tampering behaviors.
|
||||
The project combines Java Android components with native C/C++ shared libraries loaded through JNI.
|
||||
Its exported checks cover debugging, rooting, speed-hack behavior, binary modification, and virtual-machine related indicators.
|
||||
It is intended for mobile game protection experiments and for studying anti-cheat detection techniques on Android.
|
||||
@@ -0,0 +1,4 @@
|
||||
This project is a Python-based real-time CS2 overlay that detects enemy players with a YOLOv8 ONNX model.
|
||||
It uses ONNX Runtime for inference, mss for screen capture, and Pygame plus Win32 APIs to render a transparent topmost overlay window.
|
||||
The implementation includes optional CUDA acceleration, confidence filtering, hotkeys, and a smooth aim-assist routine.
|
||||
Its primary use case is computer-vision cheat prototyping and related anti-cheat research on AI-assisted detection behavior.
|
||||
@@ -0,0 +1,4 @@
|
||||
On All Fronts is an Unreal Engine 5 tactical FPS and RTS prototype focused on very large-scale combined AI and player battles.
|
||||
The codebase is primarily C++ with Unreal plugin content and uses the Mass Entity ECS framework to simulate tens of thousands of entities.
|
||||
It includes systems and examples for AI soldier control, command workflows, and large-map gameplay architecture.
|
||||
Its main audience is engine and gameplay programmers who want to study high-scale simulation patterns that can also inform multiplayer security and anti-abuse design.
|
||||
@@ -0,0 +1,4 @@
|
||||
Speed Hack by Letomaniy is a Windows C++ DLL project that manipulates in-game time speed after injection into a target process.
|
||||
It follows a Cheat Engine style approach and is built with Visual Studio, including Detours-based hooking components.
|
||||
The sample exposes keyboard controls for slowdown, accelerated speed, and restoring normal speed, with configurable values in code.
|
||||
It is mainly used for cheat development practice and for researching how games and anti-cheat systems handle time manipulation.
|
||||
@@ -0,0 +1,4 @@
|
||||
AutoHotkey is an open-source Windows automation and macro scripting platform with a custom hotkey-focused language.
|
||||
The repository is mostly C and C++ source code for building interpreter binaries, self-contained script runtimes, and related tooling.
|
||||
It also includes an experimental DLL hosting interface for embedding the interpreter in other applications.
|
||||
Its primary use case is task automation and input scripting, including game-adjacent macro experimentation and defensive analysis of script-driven behavior.
|
||||
@@ -0,0 +1,4 @@
|
||||
LibreHardwareMonitor is an open-source hardware telemetry project that provides both a Windows desktop monitor and a reusable .NET library.
|
||||
It is primarily written in C# and reads temperatures, fan speeds, voltages, loads, and clock data from CPUs, GPUs, storage devices, and other components.
|
||||
The project ships with WinForms UI code and library APIs that can be integrated into other applications.
|
||||
Its main use case is system diagnostics and sensor collection, and it is often useful in game performance monitoring or environment-aware security tooling.
|
||||
@@ -0,0 +1,4 @@
|
||||
BEClient is a small C++ proof-of-concept client that demonstrates how to initialize and call a BattlEye client DLL interface.
|
||||
It defines game and anti-cheat data structures, registers callback functions, and invokes exported routines such as run, command, and exit handlers.
|
||||
The sample is set up as a Visual Studio Windows project and includes structure headers for client communication fields.
|
||||
Its primary use case is reverse engineering and research on anti-cheat client integration behavior in game processes.
|
||||
@@ -0,0 +1,4 @@
|
||||
Win32.Nebula is a proof-of-concept packed and protected module loader framework for Windows.
|
||||
It is written mainly in C++ and separates a lightweight loader library from a builder utility that patches, encrypts, and packs binaries.
|
||||
The design includes SDK-style APIs, a dynamic service manager concept, and low-level Windows internals oriented implementation choices.
|
||||
Its main use case is research into software protection, loader architecture, and anti-analysis techniques used in malware and anti-cheat ecosystems.
|
||||
@@ -0,0 +1,4 @@
|
||||
delete-self-poc is a C proof of concept that shows how a running or locked executable can delete itself from disk on Windows.
|
||||
The technique renames the file primary data stream and then sets file disposition flags through SetFileInformationByHandle APIs.
|
||||
It demonstrates handle sequencing, deletion semantics, and practical edge cases around locked file removal.
|
||||
Its primary use case is low-level Windows internals research relevant to anti-forensics, secure cleanup, and defensive detection engineering.
|
||||
@@ -0,0 +1,4 @@
|
||||
This project is a C proof of concept for stealth-oriented code injection using NtQueueApcThreadEx and random NTDLL gadgets.
|
||||
It searches executable sections of ntdll for suitable pop-and-return sequences and uses them so APC execution returns into shellcode.
|
||||
The approach makes routine pointers appear more legitimate than classic direct APC injection while documenting likely detection vectors.
|
||||
Its main use case is offensive tradecraft research and evaluation of anti-cheat or EDR telemetry around APC-based execution.
|
||||
@@ -0,0 +1,4 @@
|
||||
shellcode-plain-sight is a C demonstration of hiding shellcode inside a large randomized memory region before execution.
|
||||
The method allocates oversized read-write memory, fills it with random bytes, places payload data at a random offset, and then flips protection to executable.
|
||||
It also includes cleanup logic to zero memory before freeing so artifacts are reduced after runtime.
|
||||
Its primary use case is evasion research and testing memory-analysis or anti-cheat detection strategies against concealed payload placement.
|
||||
@@ -0,0 +1,4 @@
|
||||
wsb-detect is a C library and sample program for detecting whether code is running inside Windows Sandbox.
|
||||
It implements multiple fingerprinting checks such as sandbox-specific processes, usernames, device paths, DNS suffixes, registry artifacts, and timing clues.
|
||||
The project exposes modular detection functions that can be combined depending on false-positive tolerance.
|
||||
Its main use case is anti-analysis research and environment awareness for malware studies, red-team simulation, and defensive countermeasure testing.
|
||||
@@ -0,0 +1,4 @@
|
||||
Yuzu Archive is a placeholder repository that no longer provides emulator source code.
|
||||
Its contents are primarily documentation files, including a brief README and a DMCA notice record.
|
||||
The archive serves as a historical snapshot of takedown context rather than a development codebase.
|
||||
Its primary use case is legal and ecosystem reference for researchers tracking emulator enforcement events.
|
||||
Reference in New Issue
Block a user