https://forum.piriform.com/index.php?s=6c73721068b999a12954e2e6ba4e5877&;showtopic=48869&page=11#entry286985

Didn't run ccleaner v5.33.0.6162 at any point = not infected
Installed but didn't run ccleaner v5.33.0.6162 before September 16th = not infected (this assumes the installed doesn't run the main exe files at all after installing)
Installed and ran ccleaner v5.33.0.6162 before September 16th, but firewall rules denied CCleaner.exe all network access = not infected
Installed and ran ccleaner v5.33.0.6162 after September 15th = not infected (malware server disabled)

64-bit users:
Installed and ran ccleaner v5.33.0.6162 before September 16th, but did not use the skip User Account Control (UAC) feature and did not run the 32-bit main exe = not infected
Installed and ran ccleaner v5.33.0.6162 before September 16th, and did use the skip User Account Control (UAC) feature OR ran the 32-bit main exe = status unclear (see note A1)

Note A1: If the tampered 32-bit main exe file (CCleaner.exe) exits after running the untampered 64-bit main exe = not infected

Note A1: If the tampered 32-bit main exe file (CCleaner.exe) persists while waiting for the 10 minute delay after passing control to the untampered 64-bit main exe = Stage 2 possible


32-bit users:
Installed and ran ccleaner v5.33.0.6162 before September 16th = Stage 2 possible