If you've never installed a cheat before, the process is simpler than most guides make it seem. Here's every step.
Before You Download
- Check status — always go to the live status page first. An outdated cheat is more likely to be detected and won't have the latest features.
- Note the anti-cheat — CS2 uses VAC, Valorant uses Vanguard, Apex uses EAC. Different games need different safety settings.
Step 1: Download the Archive
Click the download button on the game's cheat page. You'll get a .zip file — no account, no payment required.
Step 2: Extract the Archive
- Right-click the
.zip→ "Extract All" (Windows) or use 7-Zip / WinRAR. - When asked for a password, enter:
2026 - Extract to a simple path like
C:\cheats\— avoid paths with spaces or special characters.
Step 3: Disable Antivirus Temporarily
Windows Defender and most AV products flag cheat loaders as malware (false positive — they use memory APIs that AV doesn't like). You need to add an exclusion:
- Windows Defender: Settings → Virus & Threat Protection → Exclusions → Add folder → select your extract folder.
- Or disable real-time protection temporarily before running.
Step 4: Run the Launcher
- Right-click
aLauncher.exe→ "Run as Administrator" — required for memory access. - The loader window opens. Don't launch the game yet.
- Configure your settings (FOV, smoothing, which features to enable).
- Launch your game normally from Steam/Battle.net.
- Wait until you're in the game's main menu, then click "Inject" in the loader.
Step 5: In-Game
The overlay appears (usually toggle key: Insert or F1). Adjust settings to your preference. Close the loader when done gaming — don't leave it running in the background.
Browse available game cheats: Cosmo Cheatz →
Checking That Injection Actually Worked
A load can report success and still deliver nothing usable, so verify rather than assume. The clearest signal is the overlay itself: press the toggle key and watch for the menu drawing over the game within two or three seconds. A blank or frozen menu usually means the loader attached before the game finished initialising its renderer, which is common when injecting from the main menu on titles like Escape from Tarkov or Rust, where the first match loads additional assets. Trying again after loading into an offline raid or the firing range is the reliable fix. Check that your chosen features respond in a controlled way, such as an FOV slider visibly widening the field, before joining live matches. Look at the loader log; most write a timestamped line confirming the process handle and module base address. If no log entry appears, the injection failed silently, often because the target ran elevated and the loader did not.
Antivirus Handling Without Disabling Protection
Leaving Defender's real-time protection off for a whole session is an unnecessary risk, and most detections come from the loader's use of WriteProcessMemory and handle-opening calls rather than from the game itself. A folder exclusion on the extracted directory is enough in most cases, but Defender sometimes still quarantines individual DLLs at first run, so confirm the file count matches the archive after a fresh extraction. Third-party suites behave differently: Bitdefender's Advanced Threat Defence will block injection even with a folder exclusion until you add a process exclusion for the game executable, and Kaspersky's System Watcher can roll back a loader as a suspicious application. If the loader closes instantly with no window, that is almost always antivirus interference rather than a bad build. Re-enable real-time protection once the game session ends, and delete the extracted folder rather than leaving dormant executables on disk.
The Most Common Installation Mistakes
Extracting into the game's own installation folder breaks updates and, on Steam, causes the next patch to delete your files without warning, so keep the loader somewhere entirely separate. Running the game before configuring the loader is the second frequent error: settings saved after injection often fail to apply because some menus are only read at attach time, so change FOV and smoothing values first. Launching the loader without administrator rights produces a handle error that many users misread as a detection. Steam overlay conflicts are underrated; disable the overlay for the specific game if the menu flickers or input is captured twice. On Vanguard-protected titles such as Valorant, the kernel driver rejects handles from unsigned loaders regardless of exclusions, so failures there are expected rather than fixable. Finally, leaving the loader open after closing the game keeps a session alive and increases exposure.