reclaimwise.finance is an active crypto‑drainer site observed since its registration on 24 May 2026. The domain resolves to 185.158.133.1, a server located in Frankfurt, Germany, and serves content over HTTPS using a Google Trust Services/WE1 certificate. DNS is delegated to four name servers (ns3fqs.name.com, ns1hwy.name.com, ns2fln.name.com, ns4jnz.name.com) registered through Name.com, Inc. HTTP requests return status 200 and the page title “The 95% Project — Reclaim what fraud took from you”. The site is listed on three security blocklists and is actively blocked by PhishDestroy, MetaMask, and SEAL. VirusTotal analysis shows a single detection out of 91 scanners, and Gridinsoft assigns a trust score of 0 / 100, reinforcing the malicious assessment. Infrastructure indicators, including the German IP address and recent domain age, are consistent with fast‑flux or short‑lived abuse campaigns targeting cryptocurrency users. No additional technical artifacts such as malware hashes or C2 endpoints have been published, so the exact draining mechanism remains unknown. Defenders should add reclaimwise.finance to deny‑list rules, monitor outbound connections to 185.158.133.1, and consider sinkholing the IP range. Continuous telemetry collection is advised to capture any evolving payloads or command‑and‑control activity associated with this crypto‑drainer operation.
DOM Analysisanalyzed 2026年9月19日score 100/1003 brand signals
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-19 22:32:12 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-19 22:35:36 UTClast content: 2026-10-19 22:32:12 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(US)
