VirusTotal
13 / 91 engine detections
レポートを開く“Suspected Malware | Cloudflare”
Cloudflareなりすまし: gvnis-zev-4y0b-0ylk7-16-09-2026-hh.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 13/91 (Criminal IP, alphaMountain.ai, BitDefender…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 91 engine detections
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This Cloudflare Pages site impersonates Cloudflare itself. It is dressed as a security interstitial titled "Suspected Malware | Cloudflare", and it targets ordinary web users who are used to seeing Cloudflare checks before a site loads. PhishDestroy first flagged it on 2026-09-17. As of 2026-10-19 the site was still alive and serving content behind protection.
Fake Cloudflare warning and verification screens rely on borrowed authority. The visitor sees what looks like a genuine Cloudflare alert about malware, and the page then tells them to take an action to "resolve" it. Depending on the variant, that means entering account credentials, downloading a supposed fix, or following instructions that hand control of the device or accounts to the attacker. Because Cloudflare does not ask visitors to clean up malware through a pop-up page, any such prompt here should be treated as the attack itself. The page title presents a Cloudflare malware warning, and we classify the site as impersonation phishing.
When VirusTotal checked the site on 2026-10-01, 13 of 91 engines flagged it. The vendors included Criminal IP, alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet and G-Data. Several major security vendors independently reached a malicious verdict, which supports the impersonation classification even though most engines had not yet caught up. Among blocklists, it currently appears only on PhishDestroy's.
The project was deployed on Cloudflare Pages on 2026-09-15, and its throwaway subdomain even carries the string "16-09-2026". PhishDestroy caught it two days after deployment. It resolves to Cloudflare, Inc. network space geolocated to Canada. Using a free pages.dev subdomain lets the operator place a page that imitates Cloudflare on a Cloudflare-owned domain, which makes the address look more credible at a glance.
If you landed on this page, close it and do not run, download or install anything it offered. If you typed a password or other login details into it, change that password wherever you use it and enable two-factor authentication. Then review recent sign-ins on the affected accounts. If you downloaded or executed something, disconnect the device and scan it with up-to-date security software before you trust it again. Defenders should block the hostname and watch for similar pages.dev subdomains with date-stamped names. Report the deployment to Cloudflare's abuse team so the project can be removed.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
39abfab2ce8bfc2a3c1df7011e7f86f858a68ab86eafec6c632a59bbb0b41d78Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→protected
http_access_restricted · Cloudflare · access_restriction
protected
http_access_restricted · Cloudflare · access_restriction
到達可能
No threat flag
View source13/91 engine detections
View sourcegvnis-zev-4y0b-0ylk7-16-09-2026-hh.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
gvnis-zev-4y0b-0ylk7-16-09-2026-hh.pages.dev
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
gvnis-zev-4y0b-0ylk7-16-09-2026-hh.pages.dev)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.