cpuz[.]cc

cpuz.cc entered the PhishDestroy evidence set on Jul 2, 2026. The assembled evidence scores 95/100 (critical).

Six independent sources are positive: VirusTotal, MetaMask, SEAL, Spamhaus DBL, Cloudflare Radar, and URLQuery. VirusTotal recorded 12 detections among 91 engines: ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, Forcepoint ThreatSeeker, G-Data, Gridinsoft, Lionic, SOCRadar, Sophos on Jul 2, 2026 at 13:00 UTC. MetaMask and SEAL listed the hostname in the external-blocklist snapshot on Aug 7, 2026 at 14:20 UTC. Spamhaus DBL: DBL_PHISH on Jul 2, 2026 at 14:30 UTC. Cloudflare Radar classified the hostname as malicious and placed it in the malware category; its verdict timestamp was not retained. URLQuery recorded 2 detections. The evidence is not unanimous. Google Safe Browsing returned no flag on Jul 2, 2026 at 12:56 UTC. URLScan completed without a malicious verdict (score 0) on Jul 2, 2026 at 12:52 UTC.

HTTP 502 was recorded on Aug 7, 2026 at 01:13 UTC; content was unavailable. Registration records for the domain list Spaceship, Inc. as the registrar and Mar 25, 2026 as the creation date. At collection time, the hostname resolved to 104.21.14.224 (AS13335 Cloudflare, Inc.). The recorded endpoint location is San Francisco, US. The stored server header is cloudflare. Captured page title: “CPU-Z — CPU, Board & RAM Diagnostics | Free Download & Guides”. DOM analysis completed on Jul 2, 2026 at 14:20 UTC; stored DOM score 95/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. IoC extraction completed on Jul 29, 2026 at 02:49 UTC; stored 0 format-validated wallet addresses and 0 Telegram indicators. TLS metadata lists Let's Encrypt as the certificate issuer with validity through Aug 23, 2026; checked Jul 2, 2026 at 13:00 UTC.

No target brand has been confirmed from stored page content; hostname wording alone is not treated as brand evidence. Taken together, the page content and independent findings support classifying this hostname as phishing. The stored record does not establish the post-click interaction, and it does not claim a confirmed wallet-draining transaction or credential submission.