VirusTotal
1 / 91
engines flag the domain · 2 suspicious
“chainabuse”
1 / 91
engines flag the domain · 2 suspicious
No threat flag
Not on Google threat lists at check time
0
threat pulses mention the domain
Online · HTTP 200
Vercel · 216.198.79.1 · TLS: Let's Encrypt
malicioussuspicious
Each check shows its own collection time. Zero detections do not guarantee safety.
MetaMask 사칭: chainabuse.cc — 콘텐츠를 사용할 수 없음. 증거 요약: VirusTotal 3/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft); URLQuery 3 det.; 2 external…
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
3 / 91 engine detections
보고서 열기3 det.
보고서 열기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
chainabuse.cc is a phishing page that borrowed the name of Chainabuse, a platform where people report crypto scams, and displayed a plain "chainabuse" page title. It targets people who have already lost funds or suspect fraud and are looking for somewhere to report it. PhishDestroy first detected it on 2026-09-29. The site went offline on 2026-09-30, and as of 2026-10-19 its DNS no longer resolves.
Impersonating a scam-reporting service is a re-victimisation tactic. People arrive stressed and hopeful that their money can be traced or recovered. Pages like this typically ask the visitor to connect a wallet "to verify ownership", enter a recovery phrase, or pay a fee to open a case or speed up recovery. Any of these hands the operator either control of the remaining funds or a direct payment. Real reporting platforms never need your seed phrase or a payment to log a report.
MetaMask and SEAL both list the domain on their blocklists alongside PhishDestroy. This matters because both focus on threats to wallet users. VirusTotal coverage was thin: 3 of 91 engines flagged it on 2026-09-29, namely alphaMountain.ai, Forcepoint ThreatSeeker and Gridinsoft. That low count reflects how quickly the site appeared and disappeared, not a clean bill of health.
The domain was registered through NAMECHEAP INC on 2026-08-24, about five weeks before it was detected. It was served from an Amazon.com, Inc. network address in the US. The .cc extension paired with an exact brand name is a common way to pass as an official site at a glance. The site went dark the day after detection, a lifespan typical of disposable phishing domains.
If you connected a wallet to this site, revoke any token approvals it may have obtained and move your assets to a fresh wallet. If you typed in a recovery phrase, treat that wallet as compromised and move everything out immediately. If you paid a "case" or "recovery" fee, report the transaction to your exchange and to the real Chainabuse service, and ignore anyone who later contacts you promising to get the money back. Defenders should block the domain, watch for lookalike Chainabuse domains on other extensions, and warn support teams that scam victims are being actively targeted a second time.
Last checked
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
dns1.registrar-servers.comdns2.registrar-servers.comeforward3.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward1.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
20218185233b8ed1094e68a54d2da9292bf835dc5960d1c3341bb4dfb6180183Saved 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 chainabuse.cc · checked Sep 29, 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
알 수 없음→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
접속 가능→이용 불가
접속 가능
PD-20260929-EA4D3E
No threat flag
View source3/91 engine detections
View sourcechainabuse.cc
View sourcePage captured
View source저장된 유사 도메인 79개
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
chainabuse.cc
PD-20260929-EA4D3E 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 ↗
chainabuse.cc)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.