VirusTotal
4 / 89 engine detections
レポートを開く“Blockchain Guildhall - Guild”
ブロックリスト掲載ドメイン: guildhub.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 4/89 (alphaMountain.ai, Forcepoint ThreatSeeker, VIPRE, Webroot); 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 89 engine detections
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開く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
guildhub.pages.dev is an impersonation phishing page that presented itself as "Blockchain Guildhall - Guild," borrowing the name and look of Guild, a platform crypto communities use to gate roles and channels by wallet holdings. Its targets are members of Web3 communities who expect to verify a wallet before joining. PhishDestroy first flagged it on 2026-08-31. The site has been offline since 2026-09-13, and its content is blocked by the hosting provider, which was still the case when last checked on 2026-10-19.
Guild-style verification normally asks users to connect a wallet and sign a message to prove ownership, so victims are already used to approving wallet prompts on this kind of page. A fake "guildhall" exploits that habit. The request that looks like membership verification can instead be a token approval, a permit signature or a transfer, which hands control of assets to the operator. The loss is typically whatever tokens or NFTs the signed request covers, and it can happen without the victim typing a seed phrase at all.
Four of 89 VirusTotal engines flagged the address as of 2026-09-12: alphaMountain.ai, Forcepoint ThreatSeeker, VIPRE and Webroot. That is a modest count, which is common for short-lived pages on shared developer hosting, but it is backed by the wallet-security ecosystem. MetaMask and SEAL both list the domain alongside PhishDestroy, so MetaMask users should see a warning before the page can load.
The page ran as a Cloudflare Pages project on the free pages.dev subdomain. The project dates to 2025-11-19, roughly nine months before PhishDestroy caught it, so the address existed well before the phishing activity was spotted. Traffic resolved to Cloudflare, Inc. address space geolocated to Canada. The Google Trust Services certificate is standard for Cloudflare-hosted projects, so the padlock said nothing about legitimacy.
If you connected a wallet to this page, review your token approvals and permit signatures with a revocation tool and cancel anything you do not recognize, especially approvals granted around the time of your visit. If you signed an unfamiliar request or suspect funds are at risk, move remaining assets to a fresh wallet. Never enter a seed phrase on any guild verification page. Reach Guild only by typing its address yourself or through a link in your community's official announcement channels. Defenders should block the domain, check DNS and proxy logs for visits since 2025-11-19, and warn community moderators that fake guild verification links circulate in Discord and Telegram.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
8264a2af3f3ed6d074fcdda11031a6ba162a3442cbce0e0daf6d997f76a58516Saved 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 guildhub.pages.dev · checked Sep 11, 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
guildhub.pages.dev
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
到達可能→利用不可
3→Observation retained
到達可能
No threat flag
View source4/89 engine detections
View sourceguildhub.pages.dev
View sourceListed 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 ↗
guildhub.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.