Process Inspection & File-Integrity Checks
An experimental Rust project exploring Windows process inspection and SHA-256 file-integrity checks. The current code and tests demonstrate selected behaviors; they do not establish effective anti-cheat protection, zero performance cost, or production readiness.
Windows User Mode
The project explores user-mode inspection and does not require a kernel driver for the currently implemented paths. CPU and memory overhead have not been independently benchmarked.
SHA-256 File Hashing
Hashes can be compared with an expected value to detect file-content changes. Hashing alone does not detect every form of runtime memory tampering, injection, or cheating.
Integration Requires Validation
Native bindings and example snippets should be verified against the current build before use in Unity, Unreal, or a shipped game. Check the repository for the exact implemented exports.
// Unity (C#) — Drop anti_cheat_sdk.dll into Assets/Plugins/x86_64
using System;
using System.Runtime.InteropServices;
public class GGLoopAntiCheat : MonoBehaviour {
[DllImport("anti_cheat_sdk.dll", CallingConvention = CallingConvention.Cdecl)]
private static extern IntPtr ggloop_version();
[DllImport("anti_cheat_sdk.dll", CallingConvention = CallingConvention.Cdecl)]
private static extern int ggloop_verify_binary_sha256(string path, string expectedHash);
void Start() {
string version = Marshal.PtrToStringAnsi(ggloop_version());
Debug.Log($"[GG Loop] Anti-Cheat Sentry Initialized: v{version}");
// Validate game executable integrity before matchmaking
int isValid = ggloop_verify_binary_sha256("MyGame.exe", "3f2d1e0a...expected_hash");
if (isValid != 1) {
Debug.LogError("[SECURITY VIOLATION] Game binary has been modified!");
Application.Quit();
}
}
}
Current Project Status
Source & Experiments
For review and experimentation
- Inspect the source code
- Review available tests
- Experiment in a controlled environment
- No production support or SLA implied
Studio Pro Subscription
Commercial service not yet validated
- No verified production deployment
- No validated user-capacity tier
- No demonstrated alerting SLA
- Capabilities require implementation and testing
- Subscription offer paused pending validation
Custom Collaboration
Discuss a prototype review
- Review the current code and project goals
- Agree a specific prototype or test task
- Define measurable acceptance criteria
- No SOC 2 certification or uptime SLA claimed
- Any paid work requires written scope agreement