Stored VirusTotal result: 20/92 engines flagged. Analysis time (as stored): 2026-10-24 21:39 UTC. Retrieved (as stored): 2026-10-27 05:16 UTC. Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
PhishDestroy first recorded trust-wallet-customer-support-number.github.io on 2026-07-26. Stored VirusTotal result: 20/92 engines flagged. Analysis time (as stored): 2026-10-24 21:39 UTC. Retrieved (as stored): 2026-10-27 05:16 UTC. Listed by external blocklists: MetaMask, SEAL.
“Trust Wallet Customer Support Number™ : ( Official )”
Availability HTTP 404 · Content unavailableThe saved response applies to the checked URL. It does not establish that every path on the domain is unavailable.Observed HTTP probe
PhishDestroy first recorded trust-wallet-customer-support-number.github.io on 2026-07-26. Stored VirusTotal result: 20/92 engines flagged. Analysis time (as stored): 2026-10-24 21:39 UTC. Retrieved (as stored): 2026-10-27 05:16 UTC. Listed by external blocklists: MetaMask, SEAL. Risk: critical (100/100). Registrar: GitHub. Status: HTTP 404 · Content unavailable. Hosting: FASTLY - Fastly, Inc., US. Do not enter credentials or connect a wallet.
Analysis of the domain trust-wallet-customer-support-number.github.io, registered through GitHub, Inc., indicates active infrastructure linked to a crypto drainer threat as of July 26, 2026. The domain resolves to IP address 185.199.111.153, a GitHub Pages hosting endpoint, and currently returns an HTTP status consistent with an active deployment. Infrastructure checks reveal the domain lacks configured nameservers (NS_NOT_FOUND), a common indicator of ephemeral or hastily deployed phishing pages.
Detection data shows the domain is flagged by 18 of 91 security vendors on VirusTotal, and it appears on three independent security blocklists, including PhishDestroy, MetaMask, and SEAL, all of which classify it as malicious. The threat classification as a crypto drainer is supported by the blocklist entries, which specialize in cryptocurrency-related fraud detection. No specific brand impersonation or page content analysis is available in the current intelligence, though the domain name suggests targeting users of Trust Wallet or similar crypto services.
Defenders should treat this domain as high-risk and prioritize blocking at the network and endpoint levels. Given its GitHub Pages origin, monitoring for rapid domain changes or subdomain variations is recommended, as threat actors frequently rotate infrastructure to evade detection. The domain remains active, and further investigation into associated wallet addresses or transaction patterns may yield additional indicators of compromise.
Source evidenceVirusTotal 20 / 9211 sources
SourceResultRecorded · UTCOpen
VirusTotal
20 / 92 engine detections
Analysis:
Open report VirusTotalOriginal source recordObserved: 13 fields
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Open report Separate monitor score · 0 / 100 · 2026-07-26T14:20:14Z
This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Heuristic score
0
Analyzed at
2026-07-26T14:20:14Z
Source timestamp
2026-07-26 16:20:14
PhishDestroy narrative
Narrative generation metadata
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Ai summary
Analysis of the domain trust-wallet-customer-support-number.github.io, registered through GitHub, Inc., indicates active infrastructure linked to a crypto drainer threat as of July 26, 2026. The domain resolves to IP address 185.199.111.153, a GitHub Pages hosting endpoint, and currently returns an HTTP status consistent with an active deployment. Infrastructure checks reveal the domain lacks configured nameservers (NS_NOT_FOUND), a common indicator of ephemeral or hastily deployed phishing pages. Detection data shows the domain is flagged by 18 of 91 security vendors on VirusTotal, and it appears on three independent security blocklists, including PhishDestroy, MetaMask, and SEAL, all of which classify it as malicious. The threat classification as a crypto drainer is supported by the blocklist entries, which specialize in cryptocurrency-related fraud detection. No specific brand impersonation or page content analysis is available in the current intelligence, though the domain name suggests targeting users of Trust Wallet or similar crypto services. Defenders should treat this domain as high-risk and prioritize blocking at the network and endpoint levels. Given its GitHub Pages origin, monitoring for rapid domain changes or subdomain variations is recommended, as threat actors frequently rotate infrastructure to evade detection. The domain remains active, and further investigation into associated wallet addresses or transaction patterns may yield additional indicators of compromise.
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Collected source details
Stored page, network and scanner observations, grouped by source and observation time.
Every stored field, with its source and date
Network Security Intelligence
Cloudflare Radar VerdictMalicious
Phishing
Questions about trust-wallet-customer-support-number.github.io
Is trust-wallet-customer-support-number.github.io legit?
PhishDestroy rates trust-wallet-customer-support-number.github.io as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-07-26. Stored VirusTotal result: 20/92 engines flagged. Analysis time (as stored): 2026-10-24 21:39 UTC. Retrieved (as stored): 2026-10-27 05:16 UTC. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is trust-wallet-customer-support-number.github.io safe to connect a wallet?
This report does not record which wallet requests trust-wallet-customer-support-number.github.io makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.
What should I do if I used trust-wallet-customer-support-number.github.io?
It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.
Trust Wallet Customer Support Number™ : ( Official )
Automated brand references
Trust Wallet
TLS Certificate
Issued by Let's Encrypt· stored validity ends in 38 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
185.199.111.153
Network ASN
AS54113
AS name
FASTLY - Fastly, Inc., US
Organization
Fastly, Inc.
Observed location
San Francisco, US
Server header
GitHub.com
Edge-IP reputation is not attributed to this domain.
Nameservers 5
ns-692.awsdns-22.net
ns-1622.awsdns-10.co.uk
dns1.p05.nsone.net
dns2.p05.nsone.net
dns3.p05.nsone.net
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-06-04 23:26:07
Valid until
2026-09-02 23:26:06
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-07-26 13:02:54 UTC
Collection source
PhishDestroy collector
Certificate fingerprint32491b26bfaf7bfb556029ef32299ac4374db34d09eecd4ffd01f21b2c5a8567Certificate names · 3 SANs
github.com
github.io
githubusercontent.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 03:29 UTC.
Recorded events: 12. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Pre-emptive Discovery & IngestionThreat Ingested1/1Recorded: 1 of 1
Threat Ingested
trust-wallet-customer-support-number.github.io detected and queued for full analysis
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.
t.rustwallet.comSplit into subdomainVariant of trustwallet.comNS ns1.namebrightdns.comtrastwallet.comVowel swapVariant of trustwallet.comA 104.21.74.187NS major.ns.cloudflare.comtrostwallet.comVowel swapVariant of trustwallet.comNS 1-you.njalla.notrsutwallet.comSwapped charactersVariant of trustwallet.comMX mx.zoho.comNS dave.ns.cloudflare.comtrusfwallet.comReplaced characterVariant of trustwallet.comA 91.204.209.6MX trusfwallet.comNS ns1.hostns.iotrusrwallet.comReplaced characterVariant of trustwallet.comA 139.162.174.209trusstwallet.comPlural formVariant of trustwallet.comA 13.248.169.48NS ns1.dan.comtrusttwallet.comRepeated characterVariant of trustwallet.comA 208.98.40.203trustw.allet.comSplit into subdomainVariant of trustwallet.comA 139.162.174.209trustwa.llet.comSplit into subdomainVariant of trustwallet.comA 13.248.169.48NS ns1.namefind.comtrustwaklet.comReplaced characterVariant of trustwallet.comA 47.243.69.130NS a.share-dns.comtrustwalelt.comSwapped charactersVariant of trustwallet.comA 188.114.96.3NS nico.ns.cloudflare.comtrustwalket.comReplaced characterVariant of trustwallet.comA 47.243.69.130NS a.share-dns.comtrustwall3t.comReplaced characterVariant of trustwallet.comA 34.120.137.41MX mx1.hostinger.comNS ns1.dns-parking.comtrustwalleet.comRepeated characterVariant of trustwallet.comA 43.157.105.4MX mail.trustwalleet.comNS ns1.dyna-ns.nettrustwallef.comReplaced characterVariant of trustwallet.comA 104.21.35.38NS byron.ns.cloudflare.comtrustwaller.comReplaced characterVariant of trustwallet.comA 13.223.25.84NS nsg1.namebrightdns.comtrustwallit.comVowel swapVariant of trustwallet.comA 213.111.149.204MX trustwallit.comNS dns1.icedns.istrustwalllet.comRepeated characterVariant of trustwallet.comA 13.248.169.48NS ns5.afternic.comtrustwallot.comVowel swapVariant of trustwallet.comA 213.111.149.204MX trustwallot.comNS dns1.icedns.istrustwallte.comSwapped charactersVariant of trustwallet.comMX mx.zoho.comNS cesar.ns.cloudflare.comtrustwlalet.comSwapped charactersVariant of trustwallet.comA 188.114.96.3NS nico.ns.cloudflare.comtrustwollet.comVowel swapVariant of trustwallet.comA 43.198.87.21NS ns1.dyna-ns.nettrustwullet.comVowel swapVariant of trustwallet.comA 194.156.117.152NS brodie.ns.cloudflare.comtrustwwllet.comReplaced characterVariant of trustwallet.comA 3.167.227.113NS grannbo.ns.cloudflare.comtrustwzllet.comReplaced characterVariant of trustwallet.comA 47.243.69.130NS a.share-dns.comtrutswallet.comSwapped charactersVariant of trustwallet.comA 172.233.219.123MX mx156.hostedmxserver.comNS ns1.parklogic.comtruustwallet.comRepeated characterVariant of trustwallet.comA 188.114.96.3NS nico.ns.cloudflare.comtrystwallet.comReplaced characterVariant of trustwallet.comA 13.223.25.84NS nsg1.namebrightdns.comturstwallet.comSwapped charactersVariant of trustwallet.comA 45.91.226.134NS ns1.julydns.comrustwallet.comMissing characterVariant of trustwallet.comNS ns1.namebrightdns.comtrestwallet.comBit flipVariant of trustwallet.comA 147.161.37.75NS aldo.ns.cloudflare.comtrrustwallet.comInserted characterVariant of trustwallet.comA 13.223.25.84NS nsg1.namebrightdns.comtructwallet.comBit flipVariant of trustwallet.comA 66.78.41.20MX mail.tructwallet.comNS ns1.server1.webhostmost.comtruestwallet.comInserted characterVariant of trustwallet.comA 13.223.25.84NS nsg1.namebrightdns.comtruhstwallet.comInserted characterVariant of trustwallet.comA 179.43.144.214MX mail.h-email.netNS ns1.panamans.comtruistwallet.comInserted characterVariant of trustwallet.comA 15.197.148.33NS ns05.domaincontrol.comtrusdtwallet.comInserted characterVariant of trustwallet.comA 91.195.240.94NS ns1cnb.name.comtrusdwallet.comBit flipVariant of trustwallet.comA 91.195.240.94NS ns1cnb.name.comtrust-wallet.comAdded hyphenVariant of trustwallet.comA 44.232.173.249NS launch1.spaceship.nettrust2wallet.comInserted characterVariant of trustwallet.comA 13.248.243.5NS ns45.domaincontrol.comtrustewallet.comInserted characterVariant of trustwallet.comA 13.223.25.84NS nsg1.namebrightdns.comtrustqwallet.comInserted characterVariant of trustwallet.comA 13.223.25.84NS nsg1.namebrightdns.comtrustrwallet.comInserted characterVariant of trustwallet.comA 13.223.25.84NS nsg1.namebrightdns.comtrustswallet.comInserted characterVariant of trustwallet.comA 86.105.245.69NS ns1.eftydns.comtrustuallet.comBit flipVariant of trustwallet.comA 188.114.96.3NS ariella.ns.cloudflare.comtrustvallet.comBit flipVariant of trustwallet.comA 13.248.169.48NS ns1.afternic.comtrustwa11et.comLookalike lettersVariant of trustwallet.comA 216.120.147.200NS ns100.webnic.cctrustwa1let.comLookalike lettersVariant of trustwallet.comA 196.251.84.147MX mx.zoho.euNS ns2.1domainregistry.comtrustwaallet.comInserted characterVariant of trustwallet.comA 156.235.6.179NS ns1.myhostadmin.nettrustwaiiet.comLookalike lettersVariant of trustwallet.comA 13.223.25.84NS nsg1.namebrightdns.comtrustwailet.comLookalike lettersVariant of trustwallet.comA 91.195.240.94NS ns1cnb.name.comtrustwal1et.comLookalike lettersVariant of trustwallet.comA 156.251.149.9NS ns4.myhostadmin.nettrustwalet.comMissing characterVariant of trustwallet.comA 78.41.207.39NS ns1.torresdns.comtrustwaliet.comLookalike lettersVariant of trustwallet.comA 13.223.25.84NS nsg1.namebrightdns.comtrustwallat.comBit flipVariant of trustwallet.comA 188.114.96.3NS aldo.ns.cloudflare.comtrustwalldt.comBit flipVariant of trustwallet.comA 156.238.250.237NS a.share-dns.comtrustwalle.comMissing characterVariant of trustwallet.comA 13.223.25.84NS nsg1.namebrightdns.comtrustwallet0.comAdded characterVariant of trustwallet.comNS a.share-dns.comtrustwallet4.comAdded characterVariant of trustwallet.comA 156.238.250.124NS a.share-dns.comtrustwallet5.comAdded characterVariant of trustwallet.comNS a.share-dns.comtrustwallet6.comAdded characterVariant of trustwallet.comNS carla.ns.cloudflare.comtrustwalleta.comAdded characterVariant of trustwallet.comA 172.65.185.109NS sp1.gname-dns.comtrustwalleth.comAdded characterVariant of trustwallet.comNS a.share-dns.comtrustwalletj.comAdded characterVariant of trustwallet.comNS a.share-dns.comtrustwalletk.comAdded characterVariant of trustwallet.comA 156.251.149.28NS ns4.myhostadmin.nettrustwalletr.comAdded characterVariant of trustwallet.comA 156.235.6.119NS ns1.myhostadmin.nettrustwallets.comAdded characterVariant of trustwallet.comA 34.42.100.71NS ns-cloud-c1.googledomains.comtrustwallett.comAdded characterVariant of trustwallet.comA 13.248.169.48NS ns1.afternic.comtrustwalletx.comAdded characterVariant of trustwallet.comA 2.57.91.91NS ns1.dns-parking.comtrustwallgt.comBit flipVariant of trustwallet.comA 156.238.250.36NS a.share-dns.comtrustwallmt.comBit flipVariant of trustwallet.comA 45.205.7.25NS a.share-dns.comtrustwallt.comMissing characterVariant of trustwallet.comMX mx.zoho.comNS cesar.ns.cloudflare.comtrustwaqllet.comInserted characterVariant of trustwallet.comA 156.235.6.164NS ns1.myhostadmin.nettrustwawllet.comInserted characterVariant of trustwallet.comA 156.235.6.163NS ns1.myhostadmin.nettrustwellet.comBit flipVariant of trustwallet.comA 199.191.50.130MX ~NS ns111430.ztomy.comtrustwwallet.comInserted characterVariant of trustwallet.comA 208.98.40.204trustwzallet.comInserted characterVariant of trustwallet.comA 156.235.6.170NS ns1.myhostadmin.nettrustywallet.comInserted characterVariant of trustwallet.comA 75.101.163.116MX alt1.aspmx.l.google.comNS ns1039.ui-dns.detruswallet.comMissing characterVariant of trustwallet.comA 91.195.240.94NS ns1cnb.name.comtrvstwallet.comLookalike lettersVariant of trustwallet.comA 13.248.169.48NS ns1.afternic.comttrustwallet.comInserted characterVariant of trustwallet.comA 188.114.96.3NS abdullah.ns.cloudflare.comxn--trstwallet-beb.comLookalike lettersVariant of trustwallet.comA 185.53.179.136NS ina1.registrar.euxn--trstwallt-i4a6r.comLookalike lettersVariant of trustwallet.comA 103.224.212.107MX park-mx.above.comNS ns1.abovedomains.comxn--trustwalet-6yb.comLookalike lettersVariant of trustwallet.comA 103.224.212.109MX park-mx.above.comNS ns1.abovedomains.comxn--trustwalet-toe.comLookalike lettersVariant of trustwallet.comA 185.53.179.128NS ns1.dyna-ns.netxn--trustwalle-5cc.comLookalike lettersVariant of trustwallet.comA 185.53.179.128NS ns1.dyna-ns.netxn--trustwallt-j7a.comLookalike lettersVariant of trustwallet.comA 185.53.179.128NS ns1.dyna-ns.net
Showing 100 of 104
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches6
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
5 evidence signal groups linkedHTTP 404 · Content unavailable
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.
Scammers are criminals. Filing a report creates a legal record and helps protect others.
97-country directory
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.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
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 trust-wallet-customer-support-number.github.io)
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
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 →
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.