VirusTotal
4 / 89 engine detections
Bericht öffnen“PDf Document*”
Domain auf Blocklisten: projectbotsecurefact.pages.dev — Erreichbar · Zugang eingeschränkt (HTTP 403). Zusammenfassung der Beweislage: VirusTotal 4/89…
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
4 / 89 engine detections
Bericht öffnenSchädlich
Bericht öffnenno community references
Bericht öffnenprovider verdict: clean
Bericht öffnenNo threat flag
Bericht öffnenResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
projectbotsecurefact.pages.dev is an impersonation phishing page that presented itself as a PDF document, under the page title "PDf Document*". It targets people who receive a link to a supposed shared file and expect to view or download it. PhishDestroy first saw it on 2026-09-07. The site has been offline since 2026-09-16, and as of 2026-10-19 its content remains blocked by the hosting provider.
Document lures arrive as a message saying a file has been shared with you, such as an invoice, contract or scan. The link opens a page that looks like a document preview. Before the file can be viewed, the visitor is told to sign in or verify their identity. Whatever is typed into that prompt goes to the operators, who can then take over the victim's email or cloud account and use it to send the same lure to the victim's contacts. The sloppy title "PDf Document*" is typical of these quickly assembled fake viewers.
urlscan.io rated the page malicious and recognised it as a document-themed lure. On VirusTotal, 4 of 89 engines flagged it as of 2026-09-17: alphaMountain.ai, ESET, Forcepoint ThreatSeeker and URLQuery. That is a low count, which is common for short-lived pages on shared hosting. It means most security products would not have warned a visitor. PhishDestroy lists the domain on its blocklist.
The address was created on Cloudflare Pages on 2026-09-06, and PhishDestroy caught it the next day. That one-day gap points to a page built to be used immediately in a campaign. It is served through Cloudflare's network from a Canadian address. Free subdomains on large platforms like this one inherit the platform's reputation, so filters are less likely to block them. The certificate from Google Trust Services is issued automatically, so the padlock in the browser said nothing about whether the page was safe. The page lasted about ten days before going dark.
If you entered a password on this page, change it right away. Change it too on any other account where you reused it, starting with your email. Turn on two-factor authentication and sign out of all active sessions. Check your mailbox for new forwarding rules or filters you did not create, and warn your contacts if your account sent unexpected file-sharing messages. Defenders should search mail logs for links to this domain and identify the users who clicked. Those users' credentials should be reset, and similar pages.dev document lures should be treated as high risk.
Die Edge-IP-Reputation wird dieser Domäne nicht zugeordnet.
Location describes the IP network.
bcd7449cc5b7512ef5668d11517be94951046dbab49acf9156c2e01cb73723faSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of projectbotsecurefact.pages.dev · checked Sep 15, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
projectbotsecurefact.pages.dev
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unbekannt→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unbekannt→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unbekannt→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unbekannt→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unbekannt→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unbekannt→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unbekannt→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unbekannt→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Unbekannt→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
4→4
Erreichbar→Nicht verfügbar
Erreichbar
No threat flag
View source4/89 engine detections
View sourceprojectbotsecurefact.pages.dev
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
projectbotsecurefact.pages.dev)Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenMelden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenAktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBeobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.