VirusTotal
4 / 91 engine detections
Ouvrir le rapport“Trust Wallet”
Usurpation de Trust Wallet: duplicate-disabled-52034.invalid — Contenu indisponible. Résumé des preuves: VirusTotal 4/91 (alphaMountain.ai, Forcepoint…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
4 / 91 engine detections
Ouvrir le rapportchecked — no detections recorded
Ouvrir le rapportno community references
Ouvrir le rapportprovider verdict: clean
Ouvrir le rapportNo threat flag
Ouvrir le rapportNo malicious flag
Ouvrir le rapportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
On 24 July 2026 the domain www.trc20support.buzz was observed hosting a page with the title “Trust Wallet”. The page title directly references the legitimate Trust Wallet brand, and the domain is flagged as a brand‑impersonation infrastructure. The domain was registered on 21 February 2026 through OwnRegistrar, Inc., and the authoritative nameservers are ns1.dvgroup.co.in and ns2.dvgroup.co.in. DNS resolution points to the IPv4 address 194.61.31.103, which belongs to AS141995 (Contabo Asia Private Limited) and is geolocated in India. An HTTPS service is presented using a Let’s Encrypt certificate issued to “YE2”, confirming that TLS is active and the server returns HTTP status code 200 for the root request.
Reputation checks show a Gridinsoft trust score of 0 / 100 and the domain appears on one security blocklist. PhishDestroy has already listed the host as blocked. VirusTotal analysis reports that three of ninety‑five scanners flagged the site, indicating partial detection by anti‑malware engines. The observed scam type is “Crypto Scam”, consistent with the Trust Wallet impersonation claim. From the available evidence, the infrastructure is actively serving content that is likely intended to lure Trust Wallet users into disclosing credentials or performing unauthorized cryptocurrency transactions.
No additional samples of the page content, JavaScript, or credential‑capture mechanisms have been publicly released, so the exact attack flow remains uncertain. Defenders should add www.trc20support.buzz to URL filtering and endpoint allow‑list exclusions, block the associated IP address 194.61.31.103, and monitor DNS queries for the dvgroup.co.in name servers. Further analysis of the TLS certificate and any network traffic to the host is recommended to capture potential payloads. Organizations using Trust Wallet should issue user awareness advisories warning against visiting URLs that contain “trust” or “wallet” without confirming the official domain.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0xA249B9926CBF6A84d5c1549775636488E697a5edFormat validated · Domain analysisIoC extraction recorded 2026-07-29 02:38:24 UTC
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.
ns1.dvgroup.co.inns2.dvgroup.co.inLocation describes the IP network.
3fa1b9ed89926957a871315878d31e9385fc8586fe23234871b891b52e8c6422trc20support.buzzSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-52034.invalid', port=80): Max retries exceeded with url: / (Caused by N
duplicate-disabled-52034.invalid
4/91 engine detections
View sourceNo threat flag
View sourceduplicate-disabled-52034.invalid
View sourcePage captured
View source104 domaines ressemblants enregistrés
100 affichés sur 104
Listed domains receive at least one abuse report; this entry has no retained notification history.
Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
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 ↗
duplicate-disabled-52034.invalid)Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.
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
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
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.