This domain, trustwalletsecurity.support, is identified as a brand impersonation threat specifically targeting Trust Wallet, a cryptocurrency wallet service. Analysis indicates the infrastructure was designed to deceive users into believing they are interacting with official Trust Wallet security protocols, likely to harvest credentials or private keys. No specific drainer kit signatures have been confirmed, but the domain aligns with known phishing patterns used in cryptocurrency theft campaigns. Infrastructure analysis reveals the following technical indicators: the domain resolves to IP address 94.154.172.39 and was registered through NETIM SAS on February 21, 2026. It is flagged by 6 out of 95 security vendors on VirusTotal, with a Gridinsoft trust score of 0/100. The domain appears on three security blocklists and is actively blocked by MetaMask, SEAL, and PhishDestroy. The SSL certificate is issued by Let’s Encrypt, a common tactic to lend false legitimacy to phishing sites. The Apache HTTP Server technology stack further suggests a low-effort but targeted deployment. As of the latest assessment, trustwalletsecurity.support has been taken offline, reducing immediate exposure risk. However, the domain remains registered and could be reactivated or repurposed. Users who interacted with this domain should assume credential compromise and take immediate action, including revoking wallet access, monitoring for unauthorized transactions, and rotating any exposed passwords. Organizations should update blocklists to include this domain and its associated IP to prevent future access attempts. The elevated risk level persists due to the domain’s registration status and historical malicious activity.
RegistrationCreated Jan 15, 2026 (279d)—Expires Jan 15, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedJan 19, 2026
DOM Analysisanalyzed Jul 28, 2026score 88/1001 brand signal
Submitted URLhttp://trustwalletsecurity.support/
Favicon Hash
ICANN OVERSIGHT
Accreditation and RAA context
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
94.154.172.39
Network ASN
AS209101
Organization
IP Vendetta Inc.
Observed location
Amsterdam, NL
Server header
Apache/2
Nameservers 1
ns3.netim.net
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / E8
Valid from
2025-10-20 21:15:31
Valid until
2026-01-18 21:15:30
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-03-15 05:48:42 UTC
Collection source
PhishDestroy collector
Certificate fingerprint181a7fa34e26513f96e54383d35eb89f5b49f51e3b0460866af2b7d298b2e865Certificate names · 1 SANs
cp4.offsh.nl
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · trustwalletsecurity.support
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.
5 evidence signal groups linked0 stored notification recordsLast known active
Listed domains receive at least one abuse report; this entry has no retained notification history.
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 trustwalletsecurity.support)
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.
(FR)
