Majorgeeks News.

I often read the news - Off Base & Way Off Base - on MajorGeeks. It's informative, funny or sometimes both.

For those who don't, and are using CCleaner, do read this.
http://www.majorgeeks.com/news/story/ccleaner_hacked_malware_spread_to_2_2_million_users.html
http://www.majorgeeks.com/news/stor...e_infected_by_the_ccleaner_malware_issue.html
Thanks to Timothy Tibbetts & Jon Ben-Mayor.

Users of CCleaner 5.33 32-bit must install the latest version 5.35.
Standard.
http://www.majorgeeks.com/files/details/ccleaner_standard.html
Slim.
http://www.majorgeeks.com/files/details/ccleaner_slim.html
Portable.
http://www.majorgeeks.com/files/details/ccleaner_portable.html

 

I check it every day Way Off Base is a favourite and often gives me a laugh
The news on software updates or changes is also handy and I usually scan over the article names to see if anything is applicable to me then when I find something relevant I read it
Tim and Jon are unsung heroes who do a great job keeping us up to date

 

It seems the CCleaner malware is more serious than Piriform has acknowledge.
https://www.ghacks.net/2017/09/21/ccleaner-malware-second-payload-discovered/

 

I read on another technical forum that the Malware could only activate on 32-bit systems. All mine are 64-bit. Certainly MalwareBytes only flagged the downloaded 5.33 on my desktop, (I had not installed it luckily), and it did NOT show/flag any of the bad registry entries expected (I checked manually as well). I DO run MBAR (MalwareBytes anti-ransomware BETA), and MBAE (MalwareBytes Anti-Exploit) along with Norton Security, so I feel quite safe.

 

My Win 10 x64 Defender picked up the V 5.33 malware, so it might not work on the 64 bit OS but it was there.

 

The setup file includes both the 32-bit & 64-bit executables.
According to Piriform only 32-bit Windows will be effected by the malware.

 

Well good thing i keep older versions of programs.

I have 5.32 CCcleaner.

I have multi scanned it and 5.32 must be clean just down grade it.Till it's fixed.

 

It has been fixed.
The links are in post #1.