VirusTotal
17 / 89 engine detections
打开报告“CoinW”
钓鱼: coinw.diy — 内容不可用. 证据摘要: VirusTotal 17/89 (alphaMountain.ai, BitDefender, CRDF, CyRadar, Emsisoft); 2 external blocklist matches (MetaMask, SEAL); CF…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
17 / 89 engine detections
打开报告恶意
打开报告Scan report
打开报告no community references
打开报告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
coinw.diy is a phishing site that presented itself under the page title "CoinW", copying the branding of the CoinW cryptocurrency exchange to trick its customers. The odd "diy" ending is the main giveaway, because the brand name itself looks legitimate at a glance. PhishDestroy first flagged it on 2026-09-19. The site went offline on 2026-09-22, and as of 2026-10-19 its DNS no longer resolves.
Exchange impersonation pages copy the real login screen so that visitors type in their email, password and two-factor codes. Those details are relayed to the operators, who log into the real account and withdraw the balance before the victim notices. Some clones of this kind also show fake deposit addresses or demand an "unlock" or "withdrawal fee", and any money sent that way goes straight to the scammers. The result is a hijacked exchange account and crypto that cannot be recovered.
On 2026-09-21, 17 of 89 VirusTotal engines classed the domain as malicious. Those engines included BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Emsisoft, alphaMountain.ai, CRDF and CyRadar. That is broad agreement among unrelated vendors within two days of our first sighting. The domain is also listed by MetaMask and SEAL alongside PhishDestroy, so wallet users and the crypto security community already treat it as hostile.
The domain was registered on 2025-09-21 through Gname.com Pte. Ltd., almost a full year before it surfaced as an active phishing page. That gap points to a name bought ahead of time and held until it was needed. Traffic was served through Cloudflare, Inc. with a Canadian geolocation, which keeps the true origin server out of view. Its short active life, about three days after detection, is typical of throwaway exchange clones.
If you entered CoinW credentials on this site, change your CoinW password right away and reset your two-factor authentication. Review recent logins, API keys and withdrawal-address whitelists for anything you did not set up. If you sent a deposit or paid a "fee" there, contact CoinW support and report it to local authorities, and never send more money to recover funds. Use the same password anywhere else? Change it there too. Defenders should block coinw.diy and watch for lookalike CoinW domains on unusual extensions, since operators tend to reuse the same template.
Last checked
For this gTLD, 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 声誉不属于此域。
alla.ns.cloudflare.comsonny.ns.cloudflare.comLocation describes the IP network.
de601c18b7a18de43862f128ce674f3df1434b2af629ead0e940aeb4be8cfe19Saved 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 coinw.diy · checked Sep 19, 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.
coinw.diy
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
可访问→不可用
可访问
No threat flag
View source17/89 engine detections
View sourcePD-20260919-F07BCA
Page captured
View sourcecoinw.diy
View source已存储 131 个仿冒域名
显示 131 个中的 100 个
PD-20260919-F07BCA Recipient: complaint@gname.com Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
coinw.diy)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.