VirusTotal
6 / 89 engine detections
レポートを開く“Wallet connect”
WalletConnectなりすまし: web3connectcenter.com — コンテンツが利用できません. 証拠の概要: VirusTotal 6/89 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 89 engine detections
レポートを開くDBL_SPAM
4 community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開く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
web3connectcenter.com is a crypto wallet drainer that impersonated WalletConnect, the widely used wallet connection protocol, to deceive cryptocurrency users into authorizing malicious transactions. PhishDestroy first identified the site on 2026-09-14, the same day the domain was registered, indicating it was built for immediate deployment. The site is now dead, with DNS going inactive on 2026-09-16 and confirmed offline as of 2026-10-18.
The site presented itself under the page title "Wallet connect", mimicking the legitimate WalletConnect interface to convince visitors they were using a trusted tool to link their crypto wallets to a decentralized application. Once a user connected their wallet, the drainer silently requested broad token approvals or triggered transactions designed to transfer assets out of the victim's wallet without obvious consent. This class of drainer can empty multiple token balances in a single session, leaving the victim with little recourse after the fact.
Six of 89 engines on VirusTotal flagged web3connectcenter.com as malicious as of 2026-09-16, with detections from alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar, and desenmascara.me. The domain appears on four OTX threat-intelligence pulses, reinforcing the classification. It is listed on the PhishDestroy, MetaMask, and SEAL blocklists, and Spamhaus DBL classifies it as DBL_SPAM. The VirusTotal detection count is relatively low in absolute terms, which is common for drainer sites that are taken down within days of launch.
The domain was registered on 2026-09-14 through NICENIC INTERNATIONAL GROUP CO., LIMITED and routed through Cloudflare's network, with hosting attributed to Canada. TLS was issued by Let's Encrypt under the YE2 intermediate, a free certificate that requires no identity verification and is routinely used in short-lived fraud infrastructure.
If you visited this site and connected a wallet, immediately revoke all token approvals granted around the time of the visit using a reputable approval-checker tool, then transfer remaining assets to a fresh wallet address. Do not interact with any transaction requests that arrived after connecting. Security teams and wallet providers should ensure web3connectcenter.com is present in their blocklists and alert users who may have been redirected to it; the PhishDestroy, MetaMask, and SEAL blocklists already carry the entry.
Last checked
Edge-IP の評判はこのドメインに起因しません。
martin.ns.cloudflare.comsunny.ns.cloudflare.comLocation describes the IP network.
fb130e45e0dd9ca51824cb4980adeae84e8faab97498b4f83ea5ad373dfafde5Saved 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 web3connectcenter.com · checked Sep 14, 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.
web3connectcenter.com
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
blocked→dns_inactive
dns_nxdomain
不明→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
不明→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
不明→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
5→6
到達可能→利用不可
live_content
content_served
到達可能
4 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcePage captured
View sourceweb3connectcenter.com
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 ↗
web3connectcenter.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.