VirusTotal
7 / 89 engine detections
打开报告“USDC Approval Manager - Signature-based Token Approvals”
冒充 Ethereum: trustsending.live — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 7/89 (alphaMountain.ai, Chong Lua Dao, CRDF, CyRadar, Forcepoint ThreatSeeker)…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
7 / 89 engine detections
打开报告1 threat-system alert
打开报告DBL_PHISH
恶意
打开报告4 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | trustsending.live |
malicious | Sinkholed |
PhishDestroy threat report
trustsending.live is an impersonation phishing site that borrows Trust Wallet's identity and presents itself as a "USDC Approval Manager" for signature-based token approvals. It targets Trust Wallet users and stablecoin holders who might believe they are managing or securing their USDC permissions. PhishDestroy first saw it on 2026-09-11. On 2026-10-19 the site was still online and its content was reachable through a redirect.
The page title promises a tool for signature-based token approvals, which is the core of the trick. Instead of asking for a transaction, this kind of page asks the victim to sign an off-chain message such as a permit. That signature can quietly grant a third party the right to move the victim's USDC or other tokens. Because no gas is paid and nothing seems to leave the wallet at signing time, victims often notice only when their balance is drained. The Trust Wallet look exists to make that signature request feel routine and official.
Several independent sources agree. urlscan.io rated the site malicious and recognized Trust Wallet branding on it. On 2026-09-11, 7 of 89 VirusTotal engines flagged it: alphaMountain.ai, Chong Lua Dao, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet and Kaspersky. Spamhaus lists the domain in its DBL as phishing, and it is blocked by the MetaMask and SEAL blocklists as well as PhishDestroy's. It also appears in 4 AlienVault OTX threat pulses, so other analysts have tracked it independently.
The domain was registered through Name.com, Inc. on 2026-08-07, about five weeks before PhishDestroy detected it. That gap suggests it was prepared in advance rather than spun up on the spot. It is hosted on Google LLC infrastructure in the United States and serves a free Let's Encrypt certificate. The padlock icon this produces says nothing about whether the site is legitimate.
If you signed anything on this site, treat the wallet as compromised. Review and revoke token approvals and permits for USDC and any other assets with a reputable approval-checking tool. Then move the remaining funds to a fresh wallet whose seed phrase has never been entered or exposed anywhere. If you typed in a recovery phrase, abandon that wallet entirely. Remember that Trust Wallet does not run approval managers on outside domains. Defenders should block trustsending.live at DNS and proxy level, add it to wallet and browser blocklists, and alert users that "approval manager" pages requesting signatures are a common drainer lure.
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.
ns1cny.name.comns2ckr.name.comns3jkl.name.comns4hny.name.comLocation describes the IP network.
a0955f5477de20f7e5beb41480da4ddc82d18eac4c89f56b4bef489a9a5658ebSaved 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 trustsending.live · checked Sep 11, 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.
trustsending.live
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
可访问→不可用
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
不可用→可访问
可访问→不可用
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→inactive
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
不可用→可访问
可访问→不可用
可访问
4 community references
View sourceNo threat flag
View source7/89 engine detections
View sourcePD-20260911-E28CF9
trustsending.live
View sourcePage captured
View source已存储 52 个仿冒域名
PD-20260911-E28CF9 Recipient: abuse@name.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 ↗
trustsending.live)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.