VirusTotal
14 / 89 engine detections
レポートを開く“Wallet Connect”
WalletConnectなりすまし: hs1db12c223ba78bf5f4bc4a5d24d86f29.nexusqalinka2.quest — コンテンツが利用できません. 証拠の概要: VirusTotal 14/89 (BitDefender, CRDF, CyRadar, Ermes, ESET)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
14 / 89 engine detections
レポートを開く悪意あり
レポートを開くchecked — no detections recorded
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain hosted a crypto wallet drainer disguised as WalletConnect, the widely used protocol for connecting crypto wallets to decentralized applications. It targets everyday wallet users who expect a legitimate connection interface. PhishDestroy first detected it on 2026-09-07, just weeks after it was stood up. The site is now offline and DNS-inactive as of 2026-09-11, confirmed dead on 2026-10-19.
The page presented itself under the title "Wallet Connect", mimicking the real WalletConnect brand to earn the victim's trust. When a user connects their wallet through the fake interface, the drainer silently requests broad token approvals or triggers malicious transaction signatures. Once granted, the attacker's contract sweeps the victim's tokens and NFTs in a single automated transaction, leaving nothing to reverse. The victim typically sees only a routine-looking connection prompt before their funds are gone.
VirusTotal returned 14 malicious detections out of 89 engines checked on 2026-09-08, with flagging vendors including BitDefender, CRDF, CyRadar, Ermes, ESET, Forcepoint ThreatSeeker, Fortinet, and G-Data. urlscan.io independently rendered the page and issued a malicious verdict, identifying WalletConnect as the impersonated brand. The domain appears on the PhishDestroy blocklist. Fourteen independent engines agreeing across multiple threat-intelligence vendors is strong corroboration of the drainer classification.
The domain was registered on 2026-08-11 through NAMECHEAP INC, giving the operators less than a month of lead time before the site went live. Hosting ran on Cloudflare, Inc. infrastructure with a Canadian-geolocated IP of 188.114.96.3. The TLS certificate was issued by Google Trust Services under the WE1 intermediate, providing the site with a padlock that would not by itself signal danger to visitors.
If you visited this site and connected a wallet, treat the connection as compromised immediately. Use a tool such as Revoke.cash or your wallet's built-in approval manager to revoke every token approval granted around the time of the visit. Transfer remaining assets to a fresh wallet address that has never interacted with this domain. If you signed any transaction you did not fully understand, assume those funds are lost and report the incident to your wallet provider. Security teams should ensure this domain and its parent zone nexusqalinka2.quest are blocked at the DNS and firewall level.
For the registrable domain nexusqalinka2.quest behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP の評判はこのドメインに起因しません。
harvey.ns.cloudflare.comsunny.ns.cloudflare.comLocation describes the IP network.
78f91f8beebbdfb011a54adac6e33ba6c9fb78fc07519ea5f91e312d4ea9c371nexusqalinka2.questSaved 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 hs1db12c223ba78bf5f4bc4a5d24d86f29.nexusqalinka2.quest · checked Sep 7, 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.
hs1db12c223ba78bf5f4bc4a5d24d86f29.nexusqalinka2.quest
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
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
到達可能→利用不可
15→14
14→15
13→14
9→13
8→9
7→8
6→7
到達可能
No threat flag
View source14/89 engine detections
View sourcePD-20260907-84C84F
hs1db12c223ba78bf5f4bc4a5d24d86f29.nexusqalinka2.quest
View sourcePage captured
View sourcePD-20260907-84C84F 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 ↗
hs1db12c223ba78bf5f4bc4a5d24d86f29.nexusqalinka2.quest)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.