Friday, April 10th 2026
Security PSA: Popular Tools CPU-Z and HWMonitor Were Briefly Compromised
Popular PC DIY enthusiast tools like CPU-Z and HWMonitor were briefly compromised during the night between April 9 and April 10. This left anyone who downloaded these tools from the CPUID website vulnerable to malware they thought was a normal software tool. What actually happened was that multiple users on Reddit noticed their downloads from CPUID for both CPU-Z and HWMonitor were flagged multiple times by Windows Defender for security concerns. During that night, users attempting to download these popular utilities found the website pointing to a different host where the modified .exe files were stored. After realizing what was happening, users started removing these compromised .exe files and waited for CPUID to issue a statement. One of the owners of CPUID published a statement on X, explaining that attackers had replaced the original download links with malware-infected file links, resulting in a widespread security vulnerability. Thankfully the website is now back up and safe to resume downloads.
Sources:
Doc TB on X, via Reddit
Hi,Community tools like CPU-Z are essential software for everyone's PC. Similarly, TechPowerUp publishes GPU-Z software, and we understand the challenges faced by the owners of CPU-Z and HWMonitor. Hopefully, the spread of the malicious files was minimal, and the CPUID team can recover from the issue without any problems. For now, users can continue installing CPUID's software without any issues.
Investigations are still ongoing, but it appears that a secondary feature (basically a side API) was compromised for approximately six hours between April 9 and April 10, causing the main website to randomly display malicious links (our signed original files were not compromised). The breach was found and has since been fixed. Sorry for the inconvenience. I did my best to fix that mess as soon as possible :-/
Sam.

26 Comments on Security PSA: Popular Tools CPU-Z and HWMonitor Were Briefly Compromised
Perhaps TPU should analyze and review it's security risks. These types of attacks seem to be on the rise. You are my one and only hope!
That wouldn't clean up the OS, but it will remove an affected file that some users might have added to the ignore list of the antivirus, thinking it's a false positive.
no checksum on the package manager
no keys
no checksum on the downloads
and binaries
what else = windows = same as always since at least windows 95
edit: Recently i saw the first time checksums for uefi updates. most *windows* software do not have checksums.
-- downloading from computerbase or similar half thrustworthy sites is better as direct downloads
-- shred / wipe the disk before reinstalling.
Like how did some outsider change the download links?
there is ZERO mentioned of this at all
www.cpuid.com/news.html
I also assume that they will now run a script that hashes the page content and checks for changes, so they can nip this in the bud, the next time something like this happens
as for how, I assume that page is auto-generated by whatever they are using, and someone got into that
CPUID should do a full disclaimer, it's not the job of other websites.
was it called ramsomware? whatever. same old stuff since windows 95.
Here's a great little picture for you!
By the way, I've never experienced such an incident myself. However, I've been a Secure Boot enthusiast from the very beginning. Yes, in my experience, ransomware only works after a restart. I could be wrong, and it was just my brain that protected me.
Regards,
Fred.
Signing of files can help, but only if you have a trustworthy way to validate the key/certificate. Most often, if the webpage can be compromised, so can all the keys and hashes too.As long as the underlying flaws remain, the problem will continue. Only with Windows will you see entire enterprise networks and backends compromised from a low-level employee opening an email.Quite often, it will only make it worse.
More attack vectors, more room for human error, and possibly some false sense of security…What we need to know is how they allowed the so-called "side API" to be compromised, how they've eliminated the risk and what measures they've put in place to detect problems in the future.