VirusTotal
9 / 92 engine detections
レポートを開く“Dashboard”
フィッシング: guildstack.net — コンテンツが利用できません. 証拠の概要: VirusTotal 9/92 (alphaMountain.ai, CRDF, Fortinet, G-Data, Gridinsoft); Spamhaus DBL_PHISH; 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
9 / 92 engine detections
レポートを開くDBL_PHISH
Scan report
レポートを開く4 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
guildstack.net is a crypto wallet drainer, a category of site designed to steal the entire contents of a victim's cryptocurrency wallet in a single interaction. PhishDestroy first identified it on 2026-10-09, roughly eight months after the domain was registered. No specific brand impersonation was confirmed from available data. The site is now offline; DNS went inactive on 2026-10-14 and was confirmed dead on 2026-10-17.
The page title recorded at the time of detection was "Dashboard", presenting the site as a legitimate Web3 application interface rather than an obvious phishing page. Wallet drainers of this type prompt visitors to connect their cryptocurrency wallet, then request a broad token approval or a signed transaction that silently transfers all assets to the attacker. Victims typically lose every token and NFT held in the connected wallet before realising anything is wrong, because the malicious approval is buried in a routine-looking confirmation dialog.
VirusTotal returned 9 detections from 92 scanning engines as of 2026-10-13, with flagging vendors including Sophos, Fortinet, G-Data, Gridinsoft, SOCRadar, LevelBlue, CRDF, and alphaMountain.ai. Spamhaus DBL lists the domain under the DBL_PHISH category, an independent confirmation of phishing intent. The domain appears on three blocklists — PhishDestroy, MetaMask, and SEAL — meaning wallet software actively warns users before they can connect. Four threat-intelligence pulses on OTX further corroborate the classification.
The domain was registered on 2026-02-03 through NAMECHEAP INC and was active for roughly eight months before going dark. Hosting resolved to Cloudflare, Inc. infrastructure geolocated to Canada. The TLS certificate was issued by Google Trust Services under the WE1 intermediate, a free automated certificate that provides HTTPS without implying legitimacy.
If you visited guildstack.net and connected a wallet, immediately open your wallet's token-approval manager and revoke every approval granted around the time of the visit; tools designed for this purpose are widely available for major networks. Transfer remaining assets to a fresh wallet address as a precaution, and report the incident to your wallet provider. Security teams should ensure guildstack.net and its associated IP 188.114.96.3 are present in endpoint and DNS blocklists, and share the OTX pulse data with peers to accelerate coverage.
Last checked
Edge-IP の評判はこのドメインに起因しません。
fatima.ns.cloudflare.comthaddeus.ns.cloudflare.comLocation describes the IP network.
5123bc2e82a487bbbdead5a874afe2a42707f9c1277c5d3b485a5a51750f61e4Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.guildstack.netDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of guildstack.net · checked Oct 9, 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.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
No threat flag
View source9/92 engine detections
View source4 community references
View sourcePD-20261009-2C2B68
guildstack.net
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
guildstack.net
PD-20261009-2C2B68 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
guildstack.net)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.