Last night I ran Malwarebytes on my portable device. It detected a Trojan. The Trojan was distributed in a release of Crap Cleaner.
If you updated Crap Cleaner recently, there is a chance your PC may have the infected version.

https://www.piriform.com/news/blog/2017 ... dows-users

When I found it 8 antivirus programs reported it on Vyak. Now:
https://www.virustotal.com/en/file/6f78 ... 505771070/
Note that Microsft Windows Defender (and many others) will still not report the infection.

Don't rely on your AV program. Either follow instruction on Piriform's website or run Malwarebytes (after updating).

EDIT: Just discovered that Piriform was sold to Avast (one of the big antivirus company) a couple of months ago.

Thanks. I run MB pretty frequently at home but hadn't run into this as I'm on the road. Good thing I haven't used CCleaner in months, good to know though.

Interesting. I've used CCleaner pretty much since it was first released. Never had any issues.

Was running 5.33 - ran virus scan (MalwareBytes, Kapersky, AVG) - nothing detected.

I usually only run Windows Defender as my anti-virus protection - I just installed (and have no uninstalled) the others mentioned above, to scan for this suppose malware in CCleaner.

Now running CCleaner v5.34.

Mike.

<EDIT> Ah, it seems it was only an issue with the 32-bit version of CCLeaner 5.33. Another good reason to update to 64-bit guys!

If Malwarebytes says you are clean, you may be OK
The 32bit version I used was cleared by VirusTotal a few days ago so whether your version (and my 64 bit machine's version) does not contain another Trojan written by an even smarter virus writer.

I was tempted to get rid of Windows Defender and install Kaspersky but this is not my 64bit desktop but an underpowered pile of excrement with not much more than 1 bit of RAM! Defender seems to have lesser system overheads.

On the 64bit machine, I run Avast. This incident should keep them all on their toes for a while so I may stick with it, despite being tempted to install Kaspersky instead.

I was going to edit and mention the 64 bit but didn't get around to it. I'm easily distracted

According to Avast threat analysis, we're all safe (provided we uninstalled the affected version):

https://blog.avast.com/additional-infor ... y-incident