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 carried a signed backdoor that reported computer details to an outside server from 15 August 2017.

Piriform released version 5.33 on 15 August 2017 with a valid digital signature. Avast owned Piriform and says 2.27 million users were affected.

Major incident. Avast reported that the compromised CCleaner release affected 2.27 million computers. This entry covers the same incident as the other CCleaner record. Impact source

What happened

Attackers added code to the CCleaner binary before it was signed.

  • The malware waited 601 seconds before it ran.
  • It needed administrator rights.
  • It stored settings under the registry key HKLM\SOFTWARE\Piriform\Agomo with values MUID, TCID and NID.
  • It sent host information over HTTPS to 216.126.225.148, with the host header speccy.piriform.com.
  • It used a domain generation algorithm as a fallback if the main server was down.

The compromise probably began on 3 July 2017 and the bad release shipped on 15 August. Talos found the threat on 13 September 2017.

Affected versions

  • CCleaner 5.33.6162 and CCleaner Cloud 1.07.3191, 32-bit Windows versions only.
  • 5.32: the clean baseline before the attack.
  • 5.33.6163: fixed build with the backdoor removed, according to Avast.
  • 5.34: released 12 September 2017 and clean.
  • The free version has no auto-update. Users had to update by hand.

Indicators of compromise

  • SHA-256: 6f7840c77f99049d788155c1351e1560b62b8ad18ad0e9adda8218b9f432f0a9.
  • SHA-256: 1a4a5123d7b2c534cb3e3168f7032cf9ebf38b9a2a97226d0fdb7933cf6030ff.
  • SHA-256: 36b36ee9515e0a60629d2c722b006b33e543dce1c8c2611053e0651a0bfdb2e9.
  • Command server: 216.126.225.148.
  • Registry key HKLM\SOFTWARE\Piriform\Agomo with values MUID, TCID and NID.
  • Generated domains such as ab6d54340c1a.com and aba9a949bc1d.com. Talos lists 11 examples and says the algorithm makes new domains each month.

How to check

Check the registry key. If it exists, the machine ran the backdoored build.

reg query HKLM\SOFTWARE\Piriform\Agomo

Hash your CCleaner file and compare it with the values above.

Get-FileHash "C:\Program Files\CCleaner\CCleaner.exe" -Algorithm SHA256

What to do now

  1. Update to CCleaner 5.34 or later.
  2. Talos advises you to restore the machine to a state from before 15 August 2017, or reinstall it.
  3. Delete the Agomo registry key after you collect evidence. Search network logs for the command server address and the generated domains.
  4. Change the passwords that were used on the affected machine.

Frequently asked questions

Did the second-stage payload run?

Avast says the second-stage payload never activated. The only malicious code on customer machines was in the CCleaner binary.

Who found the backdoor?

Morphisec told Avast on 12 September 2017 and Talos told Avast after it found the threat. The command server was taken down on 15 September.

Sources

  1. blog.talosintelligence.com/avast-distributes-malware/
  2. blog.avast.com/update-to-the-ccleaner-5.33.6162-security-incident

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