Geopolitics & Supply Chain

CPUID Breach: HWMonitor Malware Served 6 Hours

Imagine firing up HWMonitor to check your GPU temps, only to hand over your Chrome passwords to hackers. That's what hit CPUID users for six straight hours.

Hacked CPUID download page serving HWMonitor malware alert

Key Takeaways

  • CPUID site served malware for 6 hours via HWMonitor/CPU-Z downloads, stealing Chrome credentials.
  • Supply chain attacks are surging; this mirrors Stuxnet-style trusted vector exploits.
  • Check your system now—signed originals safe, but installs could've compromised users.

Six hours. That’s all it took for hackers to turn one of the most trusted names in PC hardware monitoring into a malware dispenser.

CPUID — creators of HWMonitor and CPU-Z, tools that have lit up the dashboards of millions of enthusiasts tweaking rigs for AI workloads and gaming marathons — got breached. Users clicking ‘download’ got served a trojanized installer instead, straight from a shady domain mimicking legit supp0v3-dot-com tactics from earlier campaigns.

And here’s the kicker: this wasn’t some sloppy script-kiddie job. Vx-underground, those cyber sleuths who dissect malware like surgeons, called it out on X.

“Yeah, so pretty much this https://t.co/Mwm1F8xKWT malware is a pain in the ass. I’d have to spend a good bit of time trying to bonk it with a stick and reconstruct some of it. Whoever developed this malware actually cares about evasion and made some intelligent decisions…”

Deeply trojanized, it punches into Google Chrome’s IElevation COM interface — think of it as picking the lock on your browser’s password vault. EDR? Antivirus? It dodges ‘em with clever tricks, all while blending into the crowd of legit downloads.

What Exactly Happened in the CPUID Hack?

Picture this: you’re a overclocker, or maybe an AI dev stress-testing your NVIDIA beast. You hit cpuid.com for the latest HWMonitor 1.63. Boom — instead of hwmonitor_1.63.exe, Reddit users spotted HWiNFO_Monitor_Setup.exe swapping in, laced with Russian installer vibes that screamed ‘wrong.’

The breach? A side API got owned, per CPUID’s Samuel Demeulemeester. For those six hours on April 10, 2026, the site linked to poison. Original signed files stayed safe, though — smart move by the devs, or sheer luck? Investigation’s ongoing, but the fix came quick.

Windows Defender snagged most attempts. Bypassers? That weird UI probably raised flags. Still — with CPU-Z boasting tens of millions of lifetime downloads (it’s the go-to for system specs worldwide), who knows how many slipped through.

But wait — supply chain strikes again.

These aren’t random hits. Hackers love ‘em because trust is the ultimate backdoor. JavaScript libs got RAT’d in March. Fake 7-Zip site built a botnet in January 2026. Notepad++ updater? Infected mid-June 2025. It’s like Stuxnet 2.0, but for your desktop — my unique take here: this echoes the 2010 Stuxnet worm that rode trusted Siemens software into Iran’s nukes, but now it’s democratized for every PC tinkerer. And get this — as AI hardware explodes (think custom TPUs needing real-time monitoring), tools like HWMonitor become mission-critical. One breach, and your training data’s credentials are toast.

Why Are Supply Chain Attacks Exploding Now?

Simple: efficiency. Why phish a million randos when you poison one faucet everyone drinks from?

CPUID’s crowd? Pros, gamers, data hoarders — prime targets for credential theft. This malware’s laser-focused: dump Chrome logins, ghost out. No ransomware fireworks, just quiet exfil.

Look, we’re in the AI gold rush. Everyone’s benchmarking H100s and MI300s, eyes glued to temps and clocks. HWMonitor’s your cockpit instrument. Hack that, and you’re not just stealing passwords — you’re positioning for the next wave, maybe pivoting to AI model theft or crypto wallet raids.

Samuel nailed the response:

“the investigation into this breach is ongoing, but it seems that a side API was compromised for about six hours, causing the website to link to the malicious files. However, CPUID’s signed original files were not compromised, and the breach has since been fixed.”

Classy. No spin, just facts. But corporate PR often glosses — here, it’s refreshingly raw.

Is Your System Compromised from HWMonitor Downloads?

Pause. Check your downloads folder. See HWiNFO_Monitor_Setup.exe around April 10? Nuke it.

Run a full scan — Defender, Malwarebytes, whatever. Change Chrome passwords (especially if 2FA’s weak). Monitor for odd network blips.

Worse: if installed, it might’ve phoned home already. Evasion smarts mean it could’ve burrowed deep.

Prediction time — and yeah, as your enthusiastic futurist, I’m bullish on AI but warning on this: expect 10x more of these by 2028. AI’s platform shift demands ironclad supply chains. Imagine a breached tool monitoring quantum chips — catastrophe. Devs, sign everything, audit APIs like your life’s work depends on it (it does).

This isn’t doom — it’s evolution. Hardware monitoring’s going blockchain-verified, zero-trust downloads. The future’s brighter, but only if we learn fast.

Energy’s high because breaches like this? They force innovation. CPUID’ll bounce back stronger, tools more resilient. Wonder at the pace — six hours in 2026 feels like minutes in tech time.

And sprawl here: we’ve seen npm packages own devs’ machines, Electron apps turn trojan — now core utils. Parallel? The 1988 Morris Worm clogged ARPANET via fingerd trust; today, it’s your hwmonitor.exe. Bold call: regulators’ll mandate hardware-tool certs by 2027, or AI builds grind to halt on tainted rigs.

Short punch: Stay vigilant.


🧬 Related Insights

Frequently Asked Questions

What caused the CPUID breach?

A side API on cpuid.com was compromised for six hours, redirecting HWMonitor and CPU-Z downloads to malware from supp0v3-dot-com.

Did the HWMonitor malware steal my passwords?

Yes, it targeted Chrome’s password store via IElevation COM, with strong evasion against AV and EDR.

How to check if I got hit by CPUID hack?

Scan with Defender, inspect recent downloads for HWiNFO_Monitor_Setup.exe, change browser passwords, and monitor accounts.

Priya Sundaram
Written by

Hardware and infrastructure reporter. Tracks GPU wars, chip design, and the compute economy.

Frequently asked questions

What caused the <a href="/tag/cpuid-breach/">CPUID breach</a>?
A side API on cpuid.com was compromised for six hours, redirecting HWMonitor and CPU-Z downloads to malware from supp0v3-dot-com.
Did the <a href="/tag/hwmonitor-malware/">HWMonitor malware</a> steal my passwords?
Yes, it targeted Chrome's password store via IElevation COM, with strong evasion against AV and EDR.
How to check if I got hit by CPUID hack?
Scan with Defender, inspect recent downloads for HWiNFO_Monitor_Setup.exe, change browser passwords, and monitor accounts.

Worth sharing?

Get the best Semiconductor stories of the week in your inbox — no noise, no spam.

Originally reported by Tom's Hardware

Stay in the loop

The week's most important stories from Chip Beat, delivered once a week.