Malware identified in CCleaner 5.33
blog.talosintelligence.com
Malware identified in CCleaner 5.33
1–10 of 229 posts
Re: Malware identified in CCleaner 5.33
#2"CCleanup" appears to be a wordplay on "cleaning up CCleaner", but it's confusing and unnecessary. Even though the original article is named that way, I propose changing the thread title to the proper, well-known application name, CCleaner.
Re: Malware identified in CCleaner 5.33
#3Just Wow. I am happy now that I haven't updated my installation of ccleaner for over a year and so I am safe.
Re: Malware identified in CCleaner 5.33
#4What can be done on machines that have a new install of CCleaner - Is there a patch available ?
Also does this effect the Mac OSX version of CCleaner or just the windows version ?
Re: Malware identified in CCleaner 5.33
#5"CCleanup" appears to be a wordplay on "cleaning up CCleaner", but it's confusing and unnecessary. Even though the original article is named that way, I propose changing the thread title to the proper, well-known application name, CCleaner.
Also "A vast" - a play on Avast.
Re: Malware identified in CCleaner 5.33
#6Uninstalling CCleaner and formatting now.
Re: Malware identified in CCleaner 5.33
#7"CCleanup" appears to be a wordplay on "cleaning up CCleaner", but it's confusing and unnecessary. Even though the original article is named that way, I propose changing the thread title to the proper, well-known application name, CCleaner.
Installer neither on your system. They do more harm than good.
Re: Malware identified in CCleaner 5.33
#8What can be done on machines that have a new install of CCleaner - Is there a patch available ? Also does this effect the Mac OSX version of CCleaner or just the windows version ?
Edit: Updating with their release blogpost instead, as it's clearer:
Release Post: http://www.piriform.com/news/release-announcements/2017/9/18...
Affected Versions:
>This compromise only affected customers with the 32-bit version of the v5.33.6162 of CCleaner and the v1.07.3191 of CCleaner Cloud. No other Piriform or CCleaner products were affected. We encourage all users of the 32-bit version of CCleaner v5.33.6162 to download v5.34 here: download. We apologize and are taking extra measures to ensure this does not happen again.
macOS seems fine, it looks like it was their 32bit Windows/Cloud offerings:
http://www.piriform.com/news/blog/2017/9/18/security-notific...
>Before delving into the technical details, let me say that the threat has now been resolved in the sense that the rogue server is down, other potential servers are out of the control of the attacker, and we’re moving all existing CCleaner v5.33.6162 users to the latest version. Users of CCleaner Cloud version 1.07.3191 have received an automatic update. In other words, to the best of our knowledge, we were able to disarm the threat before it was able to do any harm.
So if you have a Windows copy, look for a patch I guess. Seems like it's not just fixed, but the rogue server taken down.
Re: Malware identified in CCleaner 5.33
#9Just Wow. I am happy now that I haven't updated my installation of ccleaner for over a year and so I am safe.
Me too, good that their update isn't convenient.. for once. Still at 5.31.
Gotta check other computers though, and smartphones.
Re: Malware identified in CCleaner 5.33
#10There has been a number of cases of installers from trusted developers being infected lately. (For example Transmission being infected twice...)
On our side (developers) we need to be careful with this idea that "we will know" when something is wrong and be more careful when deploying software. It would also be nice if some form of tool could be used to test a binary to make sure it only contains what it should contain (sort of a whitelist of symbol names compared to the source files, idk...) I'm sure something along these lines probably exists for some different purpose.