Security engines reporting a detection: 13. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
trust.kitchen was a phishing page posing as Trust Wallet. It targeted Chinese-speaking users with a fake recruitment drive for an AI beta-testing partner program. PhishDestroy first flagged it on 2026-09-02. The site has been offline since 2026-09-11, and its DNS was still inactive when we last checked on 2026-10-19.
How the scam works
The page title, "Trust Wallet AI 内测合伙人招募", translates to "Trust Wallet AI beta-test partner recruitment." It offers a bogus insider opportunity under a trusted wallet brand. Lures like this usually ask applicants to verify their wallet by entering a recovery phrase, connecting the wallet and signing a transaction, or paying a fee to join. Any of these hands control of the wallet, or the money, to the operators. Once a seed phrase is exposed, the attacker can empty the wallet from anywhere, and the theft cannot be reversed.
Evidence
Within two days of our first sighting, 13 of 90 VirusTotal engines flagged the domain. Those included ChainPatrol, alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet and G-Data. Google Safe Browsing listed it under social engineering. urlscan.io returned a malicious verdict and matched the page to the Trust Wallet brand. The domain is blocked by PhishDestroy, MetaMask and SEAL, and three AlienVault OTX threat pulses reference it, so several independent sources reached the same conclusion.
Infrastructure
The domain was registered on 2026-09-01 through GNAME.COM PTE. LTD. and was detected the very next day. That timing points to a throwaway domain built for a short campaign. It was hosted in Hong Kong on Forewin Telecom Group Limited's network. The site stayed online for only about ten days before going dark.
What to do
If you typed your Trust Wallet recovery phrase into this page, treat the wallet as compromised. Create a new wallet with a fresh phrase on a clean device and move any remaining funds there immediately. If you connected a wallet or signed anything, revoke the token approvals you granted using a reputable approval checker. If you paid a joining or activation fee, do not send more money to "unlock" anything, and report the payment to your exchange and local police. Trust Wallet does not recruit beta partners through standalone sites asking for seed phrases. Security teams should block the domain and watch for lookalike Trust Wallet domains using the same Chinese-language recruitment lure.
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 2, 2026
Submitted URLhttp://trust.kitchen/
Favicon Hash
Case ID
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-19 01:13:55 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-05 22:16:42 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-05 22:16:42 UTC → 2026-09-30 16:14:55 UTC · 593.97hmidpoint estimate ≈ 2026-09-18 07:15:48 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.
Technologies · 3 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · trust.kitchen
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.
7 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 trust.kitchen)
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.
