If it becomes a real problem, then I will probably be forced into installing Chrome on my machine so I can duplicate and track down the bug. Don’t get me wrong, I am happy that you let us know about it. Since Chrome is probably the most popular browser right now, I would think the comments would be churning with complaints and yours is only the second time I’ve heard of this. I don’t see how it could be a DCT coding problem. The reason I am suspicious of the browser is that DCT uses WordPress as its CMS along with millions of other sites around the world. In all fairness to Avast, I guess it is possible they didn’t know about it, but they are in the security business, after all, so what does that tell you…ĭid this happen with previous versions of Chrome, or is this something new? (All one has to do is consider the Equifax debacle to know what I’m talking about.) In this case, it took Avast, the new owner of Piriform, nearly a month to get this fixed. There seems to be a fast-growing trend for companies to hold off when it comes to notifying its customers about a security breach. A more drastic approach would be to permanently delete the software. Apparently, the malware is limited to a CCleaner Dynamic Link Library (DLL) file which is replaced when updating the software. Opting to update CCleaner is, in my opinion, the best and only viable route to take. According to Microsoft, Defender is able to detect and remove this virus The second way is to run Windows Defender.First and foremost, uninstall the old version and download CCleaner version 5.34 (or later).The good news is that it is relatively easy to fix the problem and there are a couple of ways to do it: If you have installed CCleaner after September 12, then you should have the latest version. It is also possible that an insider with access to either the development or build environments within the organization intentionally included the malicious code or could have had an account (or similar) compromised which allowed an attacker to include the code. Given the presence of this compilation artifact as well as the fact that the binary was digitally signed using a valid certificate issued to the software developer, it is likely that an external attacker compromised a portion of their development or build environment and leveraged that access to insert malware into the CCleaner build that was released and hosted by the organization. This is important, as you will learn later in this post. If you are running version 5.33, uninstall it and get the latest clean version (5.34 as of this writing). To know which version you are currently running, simply fire up CCleaner and the version number is prominently displayed in the upper-left corner of the main window. If you installed the free 32-bit version 5.33 of CCleaner, then, “Yep!”, you are– along with an estimated 2.27 million other unlucky folks. This version was released on August 15 and was still being used for its download link on the official CCleaner page on September 11. According to Talos, a division of Cisco, version 5.33 was hiding malware in the installer for CCleaner. By “normal”, I mean those of us who are not geeky, power freaks who are able to strip an operating system down to its nuts and bolts and put it back together again.īut recently, the CCleaner installer got corrupted by a Botnet virus (-6336251-0). I have always recommended CCleaner as a good utility for the normal Windows user to help keep their Windows systems free of clutter, and I still do.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |