finds.dev

adem-hosni/AtomicShieldServer

Advanced Game AntiCheat Master Server — Real-time cheat detection, HWID fingerprinting, encrypted WebSocket protocol, and management dashboard

View on GitHub

★ 2Pythonupdated Jul 2026

// the take

AtomicShieldServer is the Django backend for a commercial FiveM/MTA:SA anti-cheat platform: it runs an encrypted WebSocket protocol between game servers and client agents, handles HWID fingerprinting and cheat detections, and ships a full admin dashboard with subscriptions, moderator roles, and Discord alerting. It's built for game server owners who want a hosted anti-cheat service, not for developers looking for a library to build on — and per the README the project has already been sold, so it isn't something you can actually adopt.

The strict/unstrict detection severity model is a sensible design choice for anti-cheat specifically — it lets operators auto-ban on high-confidence signals while gating noisier checks (debug mode, secure boot disabled) behind server-side policy instead of hard-coding false positives into bans. The WebSocket protocol design (separate packet ID enums for server vs. agent, timestamp-based anti-replay, key rotation across a pool of AES keys) shows real thought about the wire-level threat model, not just slapping TLS on JSON. It's also a genuinely complete product, not a proof of concept: subscriptions, moderator permission scoping, audit logging, and release/asset distribution are all implemented, which is a different bar than most anti-cheat side projects clear.

The AES key material itself appears to be committed straight into the repo (bin/debug/aes_keys, bin/production/aes_keys as binary files) rather than pulled from a secrets store — for a product whose main security pitch is an encrypted protocol, baking production keys into git history undercuts that pitch. Client-side anti-cheat is fundamentally fighting an adversary who controls the machine it runs on; encrypting the transport protects the wire, not the actual attack surface (memory reads, hooking, agent patching), so the crypto work here is solving a secondary problem. There's no visible story for scaling the single Django/Channels master server past one process for many concurrent game-server WebSocket connections. And since the project has been sold and is proprietary with 2 stars and two listed maintainers, there's no path to community review of a codebase whose entire job is resisting a motivated, technical adversary.

We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
2
Forks
1
Language
Python
Last commit
1 Jul 2026

// nearby

If AtomicShieldServer isn't quite it.

All repos →