Cheat-first detection
Targets loaders, injected modules, and suspicious behaviour instead of random background apps or harmless overlays, so legit players stay clear.
Live · 12,461 scans completed
Catch real cheats.
Catch real cheats.
Not your legit players.
AACGUARD is a lightweight client-side anti-cheat scanner for CS2, CS:GO and CS 1.6 community servers. It finds loaders, injected modules and tampering without kernel drivers, and without flagging 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.
12,461
Total scans
4,096
Players flagged
30
Detections, last 24h
[INIT] AACGUARD starting...
[OK] Players scanned: 4,263
[OK] Total scans: 12,461
[OK] Total flagged: 4,096
[INFO] Last 24h detections: 30
[LAST] Last scan at 2026-10-06 21:15:04
[DONE] Waiting for next client check_
Kernel driversNone required
Detection focusLoaders, injectors
Steam linkedPer scan session
Player lookup
Search a player’s AACGUARD history
Enter a username, SteamID64, SteamID, or Steam profile link.
Search for a player
The player info will appear here without leaving this page.
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.
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
AACGUARD v0.0.11.b11 (current release version)
External cheat detection, deep Windows forensics, ban-evasion fingerprint and fairer verdicts
Version 0.0.11 is the biggest update so far: AACGUARD now catches external cheats that never show up by name, reads many more Windows records with reliable timestamps, recognises players returning on new accounts, and explains every verdict with a local scan report, all in a redesigned app.
- External cheat detection – While a game is running, AACGUARD finds programs reading or writing the game's memory and invisible ESP overlay windows, so external cheats are caught whatever they are called.
- CS 1.6 proxy DLL & ASI check – Game folders are checked for fake opengl32.dll, d3d9.dll, dinput8.dll and similar files and for .asi plugins, the classic way CS 1.6 hacks get loaded.
- Cheat version labels – Every Counter-Strike finding now shows whether it is a CS 1.6, CS:GO or CS2 cheat.
- Hardware fingerprint & spoofer detection – One-way hashes of key hardware are sent with each report so ban evasion on new accounts can be recognised (raw serials never leave the PC), and HWID spoofer traces are flagged.
- Tamper checks – Flags cleared event logs, Prefetch switched off, clock changes, aacguard.com blocked and Windows booted in test-signing or kernel-debug mode.
- Much deeper Windows forensics – Windows Defender history, deleted files, the Windows 11 launch log, DNS cache, services, drivers and scheduled tasks, ShellBags, Recent files and Jump Lists are now checked.
- USB traces – Every USB storage device the PC has seen is listed, and programs or files used from removed drives are linked back to it.
- AmCache works & reliable timestamps – AmCache is read even when Windows locks it, Prefetch, BAM, ShimCache and MUICache were rebuilt, and every finding now has an evidence timeline, including browser visit times.
- Fairer verdicts – Old traces count less, cheats for another game are shown but not counted, only real HvH / cheat cfgs are flagged, and the whitelist can no longer be abused.
- Local scan report – A report opens after every scan, showing each finding, why it was flagged and how many points it counted.
- Redesigned desktop app – New dark blue design that works at any window size, with a readable raw log and a Detected Players window for today's scans.
- Bug fixes – Scans no longer report CLEAN when the rules cannot be downloaded, crashes and restart mix-ups are fixed, and USB, AmCache, BAM and browser timestamp issues are resolved.
Flow
How AACGUARD works
- Player downloads AACGUARD and launches the client.
- The client scans Steam, CS:GO / CS2 configs, relevant running processes, and the game environment for known cheat traces and suspicious changes.
- Scan metadata, verdict details, Steam ID, and non-default config data are sent securely to the AACGUARD panel.
- The data is analysed in a way designed to avoid unsafe VAC interactions, then temporary scan data is removed from our VPS once processing is complete.
- Server admins review verdicts and can take action based on AACGUARD results.
Privacy
Privacy & transparency
- We only collect what is needed for anti-cheat: Steam ID, Steam name, scan metadata, verdicts, and game-related data like non-default CS:GO / CS2 configs.
- 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 in a controlled way to stay safe with VAC, and then delete that temporary data after the scan is processed.
- We do not store personal documents or sensitive non-game data – only Steam and game-related information required for anti-cheat checks.
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 config data 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 so we can review the case.
Do you use kernel-level drivers?
Current versions are user-mode only. In future versions, kernel-level data may be copied to our VPS for analysis and then deleted, specifically to avoid running invasive kernel-level drivers on your machine.