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
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.