Skip to main content
The cleanup tool undoes everything the game does to your system: it removes the simulated persistence marker and, depending on your platform, removes registry entries, crontab lines, or LaunchAgent plists and kills any lingering background processes.
Always run the cleanup tool after every play session, even if the game exited cleanly. The persistence mechanisms are real and survive reboots.

​
How to run

python tools/cleanup_tool.py
The tool calls remove_persistence() from cyber_modules/persistence.py and prints one of two messages: 
[Cleanup] Removed simulated persistence marker: cyber_modules/simulated_startup/system_defender_autorun.txt
or, if nothing was found: 
[Cleanup] No persistence marker found at: cyber_modules/simulated_startup/system_defender_autorun.txt
remove_persistence() returns a Tuple[bool, Path] — the boolean indicates whether anything was actually removed, and the path is the marker location that was checked.

​
What it removes

  • Deletes the registry value VirusHunterAgent under HKCU\Software\Microsoft\Windows\CurrentVersion\Run
  • Kills any running VirusHunter.exe and pythonw.exe processes
  • Removes the marker file at cyber_modules/simulated_startup/system_defender_autorun.txt

​
How to manually verify cleanup

After running the tool, confirm that nothing was left behind:
Open Registry Editor (regedit) and navigate to:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
Confirm there is no VirusHunterAgent value. Then check Task Manager to verify no VirusHunter.exe or pythonw.exe processes are running.

​
Output messages explained

MessageMeaning
Removed simulated persistence marker: <path>The marker file existed and was deleted; platform-specific cleanup also ran.
No persistence marker found at: <path>The marker was already absent — either the game was never started, or cleanup already ran.
“No persistence marker found” does not guarantee the platform-specific entries were already clean. If you suspect a stale registry entry or crontab line from a previous session, verify manually using the steps above.

Build docs developers (and LLMs) love

Get started for freeTalk to us