vendor binary

The CCleaner 5.33.6162 Supply Chain Attack

Updated 5 Oct 2026 · Incident date 15 Aug 2017

CCleaner 5.33.6162 and CCleaner Cloud 1.07.3191 shipped a backdoor that sent computer details to strangers and downloaded extra programs on 15 August 2017.

Avast reports that 2.27 million users ran the bad version. Piriform's own certificate signed the program, so it looked genuine.

Major incident. Avast reported that the compromised CCleaner release affected 2.27 million computers. This is not a count of second-stage infections. Impact source

What happened

Attackers placed malicious code inside CCleaner before it was built and signed.

  • Morphisec reports that the binary stayed signed by the original Piriform build machine.
  • The code changed a Visual Studio runtime function so that it ran before the real CCleaner code.
  • It loaded a DLL straight into memory.
  • The payload collected system information and contacted command servers. A domain generation algorithm seeded by the month served as a fallback.
  • It had a function to download and run more code. VulnCheck lists CVE-2017-20201.

Avast states that the compromise began around 3 July 2017 and the bad build shipped on 15 August 2017. Morphisec told Avast on 12 September. Avast took the command server down on 15 September.

Affected versions

  • CCleaner 5.33.6162, 32-bit Windows build.
  • CCleaner Cloud 1.07.3191, 32-bit Windows build. VulnCheck dates this to 24 August 2017.
  • Not affected: 5.34 and the versions before 5.33.6162. Avast also released 5.33.6163.
  • The fixed Cloud version is 1.07.3214, released on 15 September 2017 (VulnCheck).

Indicators of compromise

  • File: ccleaner.exe with the file version 5.33.6162.
  • CCleaner Cloud file version 1.07.3191.
  • A signed, genuine-looking binary whose startup code runs a custom loader before the normal entry point.
  • Outbound HTTPS to command servers, or to domains from a generation algorithm seeded by the month.

How to check

Read the version of the installed program in PowerShell. Version 5.33.6162 is the bad one.

(Get-Item "$env:ProgramFiles\CCleaner\CCleaner.exe").VersionInfo.FileVersion

For CCleaner Cloud, check the installed version in Apps.

What to do now

  1. Update CCleaner to 5.34 or later. Update CCleaner Cloud to 1.07.3214 or later.
  2. Avast states that you do not need to restore a system to a state before 15 August 2017 after the update.
  3. Look for outbound traffic to unknown servers from the program in your logs.
  4. Keep a list of installed utility software. Remove tools that you do not use.

Frequently asked questions

Who owned Piriform?

Avast bought Piriform, the maker of CCleaner, on 18 July 2017.

Did more malicious code run?

Avast states that the only malicious code on customer machines was in ccleaner.exe. The second-stage payload never activated.

Who found the backdoor?

Morphisec blocked malicious installs from 20 and 21 August 2017. Cisco reported its own findings on 14 September.

Sources

  1. blog.avast.com/update-to-the-ccleaner-5.33.6162-security-incident
  2. vulncheck.com/advisories/ccleaner-and-ccleaner-cloud-malicious-backdoor-supply-chain-compromise
  3. morphisec.com/blog/morphisec-discovers-ccleaner-backdoor/

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library