view-e-start-ledgor-io[.]pages[.]dev

PhishDestroy identifies view-e-start-ledgor-io.pages.dev as an active generic phishing domain hosting a fake document delivery portal designed to trick users into downloading malicious PDF files that distribute malware payloads. The campaign abuses Cloudflare’s Pages service to host a convincing replica of a legitimate document-sharing interface, luring victims with urgency-based lures such as "urgent invoice" or "contract pending review." All evidence indicates this is a malicious infrastructure designed for credential harvesting or malware delivery, posing a direct threat to user endpoints and corporate networks.

This domain was flagged under seed bbdc82 with a risk level of under_investigation. VirusTotal currently shows 1 out of 95 engines detecting the domain. It is registered through Cloudflare, Inc., resolving to IP address 188.114.96.3. The SSL certificate is issued by Google Trust Services, which may increase perceived legitimacy. The domain operates under Cloudflare Pages, a legitimate service often abused for phishing due to its fast provisioning and SSL support. No current blocklist entries were observed, but the absence of detections does not indicate safety. The domain’s structure—using subdomain prefixes like "view-e-start-ledgor"—suggests a randomized or algorithmic naming pattern to evade detection filters. The infrastructure is modern, leveraging trusted providers to bypass initial scrutiny while delivering malicious content.

Users should immediately block traffic to and from 188.114.96.3 and view-e-start-ledgor-io.pages.dev at the network perimeter and DNS level. Do not open any files downloaded from this domain, especially PDFs, as they are likely weaponized with embedded exploits or social engineering prompts for password submission. Verify unexpected document links through direct communication with the sender using a known, trusted channel. Organizations should deploy endpoint protection to monitor for connections to this IP and inspect outbound SSL/TLS traffic for anomalies. Security teams should add the domain and IP to blocklists and correlate logs for signs of lateral movement if the site was accessed internally. Prompt isolation of affected systems is recommended.