Avast Unknowingly Bundled Malware With CCleaner For Almost A Month

Cisco’s Talos Intelligence security research group found that CCleaner, a popular piece of software that allows users to do routine maintenance on their Windows PCs, has been distributing malware along with its installation file for almost a month. Piriform was the previous owner of CCleaner, but the company has recently been acquired by antivirus maker Avast, which makes the whole situation quite ironic.

Latest Videos FromTom's Hardware
Contributor

Lucian Armasu is a Contributing Writer for Tom's Hardware US. He covers software news and the issues surrounding privacy and security.

  • Dark Lord of Tech
    I won't touch CCLEANER AGAIN. Uninstalled.
    Reply
  • TadashiTG
    Bye CCleaner, bye Avast.
    Reply
  • alchap1
    FYI, just ran Malwarebytes on my 64-bit machine with CCleaner v5.34.6207 already installed.

    Malwarebytes detected Trojan.Nyetya for download of ccsetup533.exe and \Program Files (86)\iolo\System Checkup
    Reply
  • 3ogdy
    On September 13, Talos was conducting some beta testing for its new exploit detection technology when it noticed that CCleaner 5.33 (the latest version at the time) was being flagged by the new software.


    The Talos team further analyzed the CCleaner file, and although the file was correctly signed by the vendor, CCleaner was not the only application being downloaded on users’ systems. The 32-bit binary of CCleaner 5.33 also included a malicious payload with a connection to a hardcoded command and control server.

    The affected version of CCleaner (v5.33) was released on August 15, which gave the malware almost a month to infect CCleaner users. Version 5.34 came out on September 12, the same day the CCleaner devs found the malware themselves, and it didn’t have the malware bundled with it.
    OK, this makes no sense at all. Talos says 5.33 was the latest version at the time, which is September 13th, yet 5.34 had come out a day before?
    Reply
  • ddpruitt
    20186759 said:
    OK, this makes no sense at all. Talos says 5.33 was the latest version at the time, which is September 13th, yet 5.34 had come out a day before?

    Talos never said that. Tom's once again editorializing without admitting it. The actual writeup states just that they were doing testing on 5.33, not why they were using it. My guess is that since it was beta testing it didn't really matter and they just went with what they had lying around.
    Reply
  • ddpruitt
    My respect and trust in a company depends on how they handle an incident like this. It's clear that this malware was intended to allow another large scale botnet and that there were several breakdowns in the software development process that allowed this to happen.

    Talos makes it pretty clear that there was a serious problem on Piriform's end (how do you build and send something out when the source obviously doesn't match what is in your release branch???). They spell out what happened and what they know and don't know and try to avoid assigning blame.

    On the other hand Piriform's statement makes it seem like they figured it out and eliminated the problem and released an update. It's pretty obvious they just got damn lucky the new version doesn't have the malware, probably because it got built on different machine from the affected release. They aren't taking any responsibility for what's a pretty massive breach on there end.

    With that type of response I won't ever support the use of Avast or Piriform software in the foreseeable future.
    Reply
  • skitszo
    i still have an older copy. 4.12.xxxx lol

    I been using wisecare365 lately anywayz.
    Reply
  • derekullo
    Avast maties.

    It be time to find a new ship.
    Reply
  • lperreault21
    well, i have some uninstalling to do...
    Reply
  • coolitic
    Oh the irony of an antivirus company bundling malware...
    Reply