Analysis of phantomcard.online indicates a high‑risk crypto‑drainer operation targeting users of the Phantom wallet. The domain was registered on March 06, 2026 through Hostinger Operations, UAB and resolves to the Amazon‑owned address 35.157.26.135 located in Germany (AS16509). Four nsone.net name servers (dns1.p04.nsone.net through dns4.p04.nsone.net) serve the domain, and no TLS certificate is presented, leaving the site exposed to plain‑HTTP interception. The page title returned from the host, “PHANTOMCARD | Secure Bank Activation”, explicitly references the Phantom brand, confirming impersonation of the legitimate wallet service.
The infrastructure is linked to the Solana Drainer kit, a known malicious script used to exfiltrate cryptocurrency from compromised wallets. VirusTotal scans show that two of ninety‑four security vendors flagged the domain, and three independent blocklists (PhishDestroy, MetaMask, SEAL) have already listed it as malicious. The domain appears on three additional security blocklists, reinforcing the consensus that it is being used for fraudulent activity. Current host status is offline, preventing live content inspection, but the combination of brand impersonation, drainer kit attribution, and multiple detections provides sufficient confidence to treat the domain as a confirmed crypto‑draining threat.
Defenders should add phantomcard.online to DNS and proxy blocklists, monitor traffic to the associated IP address for any residual connections, and enforce strict outbound controls for Solana‑related transactions. Email gateways should flag any messages containing the domain or its URL patterns, and users of the Phantom wallet should be warned not to interact with any activation links originating from this domain. Continuous observation of the IP’s activity within the Amazon network is recommended, as the hosting provider may be leveraged for future campaigns.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='phantomcard.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
DOM Analysisanalyzed 2026年7月29日score 83/1001 brand signal
Submitted URLhttp://phantomcard.online/
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:10:34 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-03-23 22:18:31 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-03-23 22:18:31 UTC → 2026-09-30 16:14:55 UTC · 4,577.94hmidpoint estimate ≈ 2026-06-27 07:16:43 UTC · precision very low · basis bounded
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.
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
您的加密货币交易所 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
加密货币诈骗通常是如何运作的？
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
恶意批准 — “连接钱包”的提示会使攻击者获得无限的代币消费权限
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
(LT)
