trustwallets.store is a Trust Wallet impersonation page detected by PhishDestroy on 2026-09-17. Risk: critical (88/100). Status: Content unavailable. Hosting: Hostinger International Limited. PhishDestroy sent 1 abuse report. VirusTotal: 4/89 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 4. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
trustwallets.store was a phishing page that impersonated Trust Wallet and targeted people holding USDT and other tokens in self-custody wallets. The pluralised brand name in the domain is built to pass a quick glance in a link or search result. PhishDestroy first detected it on 2026-09-17, and the site went offline the same day. As of 2026-10-19 it is dead and its DNS no longer resolves.
How the scam works
The page carried the title 'Send USDT', which presented it as a Trust Wallet transfer screen rather than a generic login page. Fake send pages like this give victims a familiar reason to act, such as completing a payment or confirming a transfer. They then either ask for the wallet's recovery phrase or prompt the user to connect and sign a transaction. Signing can quietly grant the attacker permission to move the victim's USDT. Either way, the loss is direct and usually irreversible: once the phrase is exposed or the approval is signed, the attacker can empty the wallet without further interaction.
Evidence
Wallet-security blocklists back the classification. The domain is listed by MetaMask and SEAL in addition to PhishDestroy, which means wallet users were warned at the point of connection. On VirusTotal, only 4 of 89 engines flagged it as of 2026-09-19: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and SOCRadar. That low count reflects how quickly the site appeared and vanished, not doubt about what it was. Five AlienVault OTX threat pulses also reference the domain.
Infrastructure
The domain was registered on 2026-09-15 and was caught just two days later. This short gap is typical of throwaway phishing domains spun up for a brief campaign. The site was hosted on Hostinger International Limited in Lithuania. It used a free, automatically issued TLS certificate, so the padlock in the browser said nothing about its legitimacy.
What to do
If you entered your Trust Wallet recovery phrase on this site, treat the wallet as compromised. Create a new wallet with a fresh phrase and move any remaining funds to it immediately. If you connected a wallet or signed a transaction there, review and revoke token approvals, paying particular attention to USDT allowances. Trust Wallet will never ask for your recovery phrase on a website. Security teams should block the domain and watch for lookalike Trust Wallet domains registered on similar budget hosting.
No. PhishDestroy classifies trustwallets.store as a Trust Wallet impersonation page (risk: critical, 88/100); it was first detected on 2026-09-17. VirusTotal: 4/89 engines flag it. Treat the site as unsafe.
Is trustwallets.store safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on trustwallets.store. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used trustwallets.store?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 17, 2026
DOM Analysisanalyzed Sep 17, 2026score 88/1001 brand signal
IoC Extractionscanned Sep 19, 20262 wallet · 0 Telegram IoCs
Submitted URLhttp://trustwallets.store/
Favicon Hash
Case ID
Observed page title
Send USDT
Automated brand references
Trust Wallet
TLS Certificate
Issued by YE1· stored validity ends in 52 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
88.222.222.198
Network ASN
AS47583
Organization
Hostinger International Ltd.
Observed location
Vilnius, LT
Server header
hcdn
Nameservers 2
ns1.dns-parking.com
ns2.dns-parking.com
Location describes the IP network.
TLS certificate
Issuer
YE1
Valid from
2026-09-15 08:00:53
Valid until
2026-12-14 08:00:52
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-09-17 10:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint3adf7cad5b4b8a0839466809f8506b8c2f11b22cd0ce13743374de31d47810bfCertificate names · 2 SANs
trustwallets.store
www.trustwallets.store
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-21 01:15:43 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-17 08:19:46 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-17 08:19:46 UTC → 2026-09-30 16:14:55 UTC · 319.92hmidpoint estimate ≈ 2026-09-24 00:17:20 UTC · precision 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.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · trustwallets.store
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
6 evidence signal groups linked1 stored notification recordsContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including trustwallets.store)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
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?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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.
