store[.]workshopratemod[.]com

store.workshopratemod.com is a subdomain of workshopratemod.com. PhishDestroy first recorded this hostname on Dec 31, 2025. The captured page title is “Website workshopratemod.com is ready. The content is to be added”. The evidence score is 100/100 (critical).

Two evidence sources are positive: VirusTotal and Cloudflare Radar. VirusTotal recorded 13 detections among 91 engines: ADMINUSLabs, BitDefender, Chong Lua Dao, CyRadar, ESET, Fortinet, G-Data, Gridinsoft, Lionic, SOCRadar, Sophos, VIPRE, Webroot on Jul 27, 2026 at 02:29 UTC. Cloudflare Radar classified the hostname as malicious and assigned the categories security threats and phishing; its verdict timestamp was not retained. Other stored checks provide context: The external blocklist snapshot contained no matches on Aug 7, 2026 at 18:20 UTC. URLQuery recorded no positive detection. Google Safe Browsing returned no flag on Mar 3, 2026 at 04:14 UTC. URLScan completed without a malicious verdict (score 0) on Feb 24, 2026 at 01:17 UTC.

HTTP 301 was recorded on Aug 7, 2026 at 10:29 UTC. Registration records for the registrable domain workshopratemod.com list Global Domain Group LLC as the registrar and Dec 28, 2025 as the creation date. Registration preceded first observation by 2 days. At collection time, the hostname resolved to 172.67.139.173 on AS13335 (CLOUDFLARENET, US). The associated network metadata labels the endpoint as AS13335 Cloudflare, Inc. in San Francisco, US. The stored server header is cloudflare. DOM analysis completed on Apr 23, 2026 at 07:22 UTC; stored DOM score 88/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. IoC extraction completed on Jul 29, 2026 at 02:39 UTC; stored 0 format-validated wallet addresses and 0 Telegram indicators. TLS metadata lists Google Trust Services / WE1 as the certificate issuer with validity through May 28, 2026; checked Mar 12, 2026 at 01:33 UTC.

Taken together, the content indicators and positive source findings support classifying this hostname as phishing. The intended brand and exact victim interaction are not resolved by the stored content fields.