Cloudflare Radar
悪意あり
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: blockdags-ef6.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 0/89; URLScan malicious verdict; 3 external blocklist matches…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
悪意あり
レポートを開く悪意あり
レポートを開く0 / 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
blockdags-ef6.pages.dev is a phishing page hosted on a Cloudflare Pages subdomain. We classify it as an impersonation of Cloudflare, and its crypto-themed content and wallet-security blocklistings point to cryptocurrency wallet holders as the targets. PhishDestroy first saw it on 2026-09-06. The site has been offline since 2026-09-16, and on 2026-10-19 it was still dead, with its content blocked by the hosting provider.
Pages like this borrow the name and look of a trusted brand. Cloudflare's familiar interface and its free pages.dev hosting make a lure seem routine, so the visitor goes along with a prompt to connect a wallet, sign a request or enter recovery details. urlscan.io identified generic crypto branding on the page, which fits a wallet-connection lure. Victims of this kind of page typically lose wallet access or the funds an approval lets the attacker move. The current page title, "Suspected Phishing | Cloudflare", is Cloudflare's own warning screen shown after the provider blocked the content, not the original lure.
urlscan.io returned a malicious verdict. The domain sits on four blocklists: PhishDestroy, MetaMask, ScamSniffer and SEAL. Three of those are maintained specifically to protect crypto wallet users. VirusTotal showed 0 detections out of 89 engines on 2026-09-17, but that scan ran a day after the site went offline. A clean result there says little about what the page served while it was live.
The Cloudflare Pages project was created on 2026-07-20, about seven weeks before we detected it. It then went down ten days after detection. Traffic resolved to Cloudflare, Inc. infrastructure geolocated in Canada, behind a certificate from Google Trust Services. Disposable pages.dev subdomains with randomized suffixes like "-ef6" are cheap to spin up and easy to replace, so expect lookalike projects under new names.
If you connected a wallet or signed anything on this page, use a token-approval checker to revoke permissions you do not recognize. Move remaining assets to a fresh wallet if you approved unfamiliar transactions. If you typed a seed phrase, treat that wallet as compromised and empty it into a new one generated on a clean device. Defenders should block the domain and watch for other pages.dev subdomains reusing the "blockdags" naming. Report new variants to Cloudflare's abuse team and to wallet-security blocklists.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0xa69fF6cdb130F4324777724b915D6Cd88C247a70Format validated · Domain analysisIoC extraction recorded 2026-09-21 04:01:18 UTC
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
5d1af2174d81363bc8302aa0a44a8bcabf33fa9ed226d48f466c85e65c8e9835Saved 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 blockdags-ef6.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
到達可能→利用不可
到達可能
No threat flag
View source0/89 engine detections
View sourceblockdags-ef6.pages.dev
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
コミュニティ報告:2 件
カテゴリPHISHING
@aaaaaaaaaaaaaa01
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
blockdags-ef6.pages.dev
“@aaaaaaaaaaaaaa01”
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 ↗
blockdags-ef6.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.