Loading

AACGUARD
AACGUARD
Anti-cheat layer
cs-characters
Live protection – 441 scans completed

Client-side anti-cheat · CS:GO · CS 1.6 · CS2

Catch real cheats. Not your legit players.

AACGUARD is a lightweight client-side anti-cheat scanner for community servers, focused on loaders, injected modules, and tampering – without bloated kernel drivers or false positives from harmless apps.

By downloading AACGUARD you agree that scans may be logged and associated with your Steam account on our servers, allowing server admins to review your scan history.

Total scans
441
Players flagged
156
Last 24h
11 new detections
AACGUARD · live console
Online

[INIT] AACGUARD starting...

[OK] Players scanned: 207

[OK] Total scans: 441

[OK] Total flagged: 156

[INFO] Last 24h detections: 11

[LAST] Last scan at 2026-03-22 21:42:05

[DONE] Waiting for next client check...

Kernel drivers
None required
Detection focus
Loaders, injectors
Steam linked
Per scan session

Features

Built for real servers, not slideshows.

Plug AACGUARD into your existing stack and get a real signal on cheats instead of noise from overlays, Discord, or common background tools.

Cheat‑first detection

Targets loaders, injected modules, and suspicious behaviour instead of random background apps or harmless overlays, so legit players stay clear.

Transparent scan history

Every scan is logged with timestamps, Steam identifiers, and final verdicts inside your AACGUARD panel, giving admins a clear audit trail.

Drop‑in for communities

Designed to sit next to your existing CS:GO / CS 1.6 / CS2 stack without forcing you into a specific host, plugin system, or closed ecosystem.

Updates

Changelog

View full changelog

AACGUARD v0.0.8 (dev)

Dedicated backend API, remote scan posting and safer data path

2026-02-07

Split AACGUARD into a proper client–server architecture with a new ASP.NET Core API on your Debian host, moved all scan writes from the desktop into a central MySQL backend, and wired the Windows client to submit scans over HTTP so users never touch the database directly while you keep full control and observability on the server.

  • Upgraded scan flow – Cleaned up how scans run and finish so every session now produces a consistent status, score and detection count without changing how players use the app.
  • Richer evidence per scan – Standardized what AACGUARD records (game process, exit state, browser checks, operations JSON and detailed logs) so each scan has clearer, more useful history behind it.
  • Advanced cheat detection logic – Refined and extended existing detection code to better catch loaders, injected modules and suspicious behaviour patterns while staying focused on cheats instead of harmless background apps.
  • Secure API-backed saving – Moved all database writes behind a dedicated ASP.NET API, removing direct DB access from the client and making stored scans harder to spoof or tamper with.
  • More robust error handling – Improved how the app reacts when saves fail or the backend is unreachable, showing clearer messages instead of low-level database errors.

Flow

How AACGUARD works

  1. Player downloads AACGUARD and launches it.
  2. The client scans Steam, CS:GO / CS2 configs, running processes and environment for known cheat traces.
  3. Scan metadata, verdict, Steam ID and non‑default config data are sent securely to the AACGUARD panel.
  4. The data is analysed, used to avoid triggering VAC, then removed from our VPS once the scan is processed.
  5. Server admins review verdicts and can take action based on AACGUARD results.

Privacy

Privacy & transparency

  • We only collect Steam ID, Steam name, scan metadata, verdicts, and game‑related data like CS:GO/CS2 configs that are not default.
  • AACGUARD runs scans only when you press Start or Restart, it does not run permanently in the background.
  • Future versions may analyse kernel‑level information on our VPS to be safe with VAC, and then delete it after the scan is processed.
  • We do not store personal documents or sensitive non‑game data – only game and Steam‑related information needed for anti‑cheat.

FAQ

FAQ

When does AACGUARD run?

Only when you manually press Start or Restart in the client. It does not scan continuously in the background.

What exactly do you collect?

Steam ID, Steam name, scan metadata, the final verdict, and non‑default CS:GO/CS2 configs required to detect cheats. No unrelated personal files are retained.

How do I dispute a false positive?

If you believe you were flagged by mistake, record a video showing what AACGUARD flagged and how you play, then contact us with that proof.

Do you use kernel‑level drivers?

Current versions are user‑mode. In future versions, kernel data may be copied to our VPS to be analysed and then deleted, designed to avoid triggering VAC on your machine.