VirusTotal
13 / 89 engine detections
打开报告“TrustCard - The Future of Credit Cards”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@globaldomaingroup.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
冒充 Trust Wallet: walletcard.digital — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 13/89 (alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, CRDF, Ermes); URLQuery 3…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
13 / 89 engine detections
打开报告3 threat-system alerts
打开报告恶意
打开报告4 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
walletcard.digital is an impersonation phishing page that borrows the Trust Wallet name to pitch a product called TrustCard, billed as "The Future of Credit Cards." It targets Trust Wallet users and crypto holders drawn to the idea of a card linked to their wallet balance. PhishDestroy first detected it on 2026-09-04. As of 2026-10-19 the site was still online, with its content served behind a protection layer.
The page dresses up as an official Trust Wallet card launch, which gives visitors a plausible reason to link their wallet or hand over details to sign up. Fake wallet-branded card offers usually ask the victim to connect a wallet, approve a transaction, enter a recovery phrase to verify the account, or pay an issuance or activation fee. Each route ends with the attacker taking the funds. A seed phrase gives full control of the wallet, a malicious approval lets the attacker move tokens, and any fee paid is gone. Trust Wallet does not ask users to type their recovery phrase into a website.
On 2026-09-14, 13 of 89 VirusTotal engines flagged the domain. They include alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, CRDF, Ermes, ESET, Fortinet and G-Data, a mix of mainstream antivirus vendors and predictive threat-intelligence services. urlscan.io returned a malicious verdict and identified Trust Wallet as the imitated brand, which independently confirms the impersonation. ScamSniffer, a crypto-focused blocklist, lists the domain alongside PhishDestroy, and it appears in four AlienVault OTX threat pulses.
The domain was registered through Global Domain Group LLC on 2026-08-27, eight days before PhishDestroy flagged it. That short gap is typical of throwaway domains bought for a single campaign. The site is hosted on 185.174.175.2 in Ukraine. Its free Let's Encrypt certificate means the padlock in the browser says nothing about whether the site is legitimate.
Do not connect a wallet or submit anything on this site. If you entered your recovery phrase, treat that wallet as compromised: create a new wallet on a clean device and move any remaining assets there immediately. If you connected a wallet or signed a transaction, check your token approvals with a revocation tool and revoke anything you don't recognise. If you paid a card fee, report the payment to your exchange or bank right away. Security teams should block the domain and its IP, add it to wallet and browser blocklists, and warn users that Trust Wallet card offers arriving through ads or messages should be checked against official channels.
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.
dns1.hyperhost.uadns2.hyperhost.uamail.walletcard.digitalpriority 10mail.walletcard.digitalpriority 20Location describes the IP network.
1f53657c50a36fd2fc4f5df855a26331a77a454afb5dbc3adb3a5cabde0497bfwww.walletcard.digitalSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.walletcard.digitalDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of walletcard.digital · checked Sep 4, 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.
alive_content: raw=content_403; http=403; via=https_proxy; server=nginx/1.20.1
walletcard.digital
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
未知→protected
http_access_restricted · access_restriction
可访问
4 community references
View sourceNo threat flag
View source13/89 engine detections
View sourcePD-20260904-7BDFE5
walletcard.digital
View sourcePage captured
View source已存储 104 个仿冒域名
显示 104 个中的 100 个
PD-20260904-7BDFE5 Recipient: abuse@globaldomaingroup.com 如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
walletcard.digital)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.