vendor binary

The CPUID CPU-Z and HWMonitor Download Compromise

Updated 5 Oct 2026 · Incident date 9 Apr 2026

CPU-Z 2.19, HWMonitor 1.63, HWMonitor Pro 1.57 and PerfMonitor 2.04 downloads from cpuid.com carried a trojanized library on 9 April 2026.

The installers held a real signed program and a malicious CRYPTBASE.dll. The final payload was STX RAT.

What happened

Attackers changed the download links on the CPUID website, so some downloads came from attacker-controlled hosts.

  • The archives held a signed program with a malicious CRYPTBASE.dll beside it.
  • Windows loads a DLL from the program folder first, so the signed program loaded the malicious file.
  • The loader ran anti-sandbox checks and then contacted a command server.
  • STX RAT can run a hidden VNC session and inject keyboard and mouse input.
  • It steals browser logins, Windows Vault data and crypto wallet data. It persists with a Run key, a scheduled task and MSBuild project files in AppData\Local.

Securelist puts the window at about 19 hours, from roughly 15:00 UTC on 9 April to about 10:00 UTC on 10 April 2026. The Scoop issue and SentinelOne describe about six hours.

Affected versions

  • CPU-Z 2.19.
  • HWMonitor 1.63.
  • HWMonitor Pro 1.57.
  • PerfMonitor 2.04.
  • Only copies downloaded from cpuid.com during the compromise window are at risk.

Indicators of compromise

  • File CRYPTBASE.dll in the same folder as a CPU-Z or HWMonitor program.
  • Hosting domains cahayailmukreatif.web[.]id, transitopalermo[.]com, vatrobran[.]hr and an r2[.]dev bucket.
  • Command server supp0v3[.]com (callback path /d/callback) and IP 147.45.178.61.
  • Process chain cpuz_x64.exe to powershell.exe to csc.exe to cvtres.exe.
  • A scheduled task that repeats every 68 minutes, a Run key and MSBuild .proj files in AppData\Local.

How to check

Search a Windows machine for a stray CRYPTBASE.dll outside the Windows folder.

Get-ChildItem -Path C:\ -Filter CRYPTBASE.dll -Recurse -ErrorAction SilentlyContinue | Where-Object { $_.FullName -notlike "C:\Windows\*" }

Review the scheduled task list for tasks you did not create.

Get-ScheduledTask | Select-Object TaskName, TaskPath

What to do now

  1. If you downloaded one of the four tools on 9 or 10 April 2026, scan the machine for CRYPTBASE.dll.
  2. Remove the DLL and the persistence items. Then run a full malware scan.
  3. Change browser, wallet and account passwords from a clean machine. Block the domains and IP above.
  4. Download the tools again only from the vendor site, after the vendor confirms the fix.

Frequently asked questions

How many victims were there?

Securelist counts more than 150 victims. Most were private persons, with some companies in retail, manufacturing and telecommunications. Most infections were in Brazil, Russia and China.

Why did older detection rules catch it?

SentinelOne notes that the attackers reused command infrastructure from a March 2026 FileZilla campaign.

Sources

  1. securelist.com/tr/cpu-z/119365/
  2. github.com/ScoopInstaller/Extras/issues/17588
  3. web.archive.org/web/20260823210854/https://www.sentinelone.com/blog/securing-the-software-supply-chain-how-sentinelones-ai-edr-autonomously-blocked-the-cpu-z-watering-hole-cyber-attack/

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