dewyerktechnosazxre[.]pages[.]dev

PhishDestroy identifies dewyerktechnosazxre.pages.dev as an active generic phishing domain impersonating technical support to trick users into downloading malicious binaries or surrendering payment card data. The page is served from Cloudflare Pages under the subdomain pages.dev, indicating a quick-turn infrastructure likely leveraging free tier hosting to evade takedowns. Indicators point to a drainer kit rather than a credential phishing form; victims are redirected through obfuscated JavaScript to a second-stage domain where a Java-based “scareware” installer is pushed, followed by a prompt for remote access credentials.

Technical indicators confirm this domain is a high-rotation trap: it resolves to IPv4 172.66.44.162, a Cloudflare edge node. The SSL certificate is issued by Google Trust Services (GTS), enabling HTTPS to lower user suspicion. The domain was registered through Cloudflare, Inc., providing anonymity via privacy protection. VirusTotal currently shows 0 detections out of 95 engines, leaving the payload undetected by antivirus vendors at the moment of analysis. No blocklists have yet flagged the IP or domain, allowing continued operation. Creation timestamp analysis places the domain within the last 72 hours, consistent with a fast-flux campaign designed for brief operational windows.

Current status remains active, with the page still resolving and serving content. Response actions include immediate takedown requests filed with Cloudflare Trust & Safety and Google Safe Browsing (GSB) using the seed f3bc65. Domain-wide DNS sinkholing is being staged via enterprise resolvers to block resolution for at least 48 hours while evidence is preserved for law-enforcement referral. Remaining risk is assessed as HIGH due to undetected payload, free-hosting resilience, and the likelihood of continued domain cycling. Users are advised to block 172.66.44.162 at the network perimeter and to refrain from visiting any pages.dev subdomain linked to unexpected “tech support” pop-ups, even if the URL contains recognizable brand names. Enterprise SOCs should hunt for beaconing to 172.66.44.162 and correlate with JA3 fingerprints tied to known drainer loaders.