VirusTotal
12 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: void-sigil.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 12/89 (alphaMountain.ai, BitDefender, CyRadar, ESET, Emsisoft); URLScan…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
12 / 89 engine detections
レポートを開く悪意あり
レポートを開く悪意あり
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
void-sigil.pages.dev is an impersonation phishing page that borrowed Cloudflare's branding and was aimed at cryptocurrency users. PhishDestroy first flagged it on 2026-09-05, three days after the subdomain was created. The site has been offline since 2026-09-15, its content blocked by the hosting provider, and it was still dead when last checked on 2026-10-19.
Pages dressed up as Cloudflare exploit the trust people place in its familiar security checks and verification screens. A visitor sees what looks like a routine Cloudflare step and is then pushed toward a crypto-themed action, typically entering account credentials or connecting a wallet and approving a request. urlscan.io identified generic cryptocurrency branding on the page, so the likely losses are crypto account logins or funds drained through wallet permissions. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning page shown after the takedown, while PhishDestroy classified the original content as impersonation phishing.
On 2026-09-17, 12 of 89 VirusTotal engines flagged the domain as malicious, including ESET, Kaspersky, BitDefender, Fortinet, G-Data, Emsisoft, CyRadar and alphaMountain.ai. That is a modest detection rate, but the vendors come from independent engines rather than one shared feed. urlscan.io returned a malicious verdict and matched the page to crypto branding. The domain is listed on the PhishDestroy blocklist.
The site ran as a free Cloudflare Pages project and resolved to Cloudflare, Inc. infrastructure in Canada. It was spun up on 2026-09-02 and caught by 2026-09-05, which fits a throwaway project created for a short phishing campaign. Hosting on the brand's own platform gave the lure a real Cloudflare-served address that can look credible at a glance. Cloudflare cut off the content within about two weeks of its creation.
If you entered a password or email on this page, change that password everywhere you reuse it and turn on app-based two-factor authentication for your exchange and email accounts. If you connected a wallet or signed anything, check the wallet with a token approval checker, revoke unfamiliar approvals, and move remaining funds to a fresh wallet if you approved a transaction you did not understand. Be suspicious of any "Cloudflare check" that asks for a wallet connection or login, because genuine Cloudflare challenges never do. Defenders should block the domain, search proxy and DNS logs for visits between 2026-09-02 and 2026-09-15, and contact any users who reached it.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x742d35Cc6634C0532925a3b844Bc454e4438f44eFormat validated · Domain analysisIoC extraction recorded 2026-09-22 04:00:18 UTC
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
983a7fdf1e75c826712c83181d0d9a805cbb5e4059124b4f940c1cc8d830ec50Saved 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 void-sigil.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.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
11→12
到達可能→利用不可
到達可能
No threat flag
View source12/89 engine detections
View sourcevoid-sigil.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
void-sigil.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 ↗
void-sigil.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.