Aller au rapport de sécurité
Tableau de bord analytique
Domain security report
walletconnectgate.com favicon

walletconnectgate.com

“Wallet connect”

Verdict de menace
CritiqueRecours en matière de nom de domaine
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Disponibilité Non vérifié Aucune réponse actuelle concluante n'est stockée Observé · HTTP probe
Signaux de risque
Détections VirusTotal : 9/89 Spamhaus DBL: DBL_PHISH Correspondances de la liste de blocage stockée : 2 Automated brand label: WalletConnect
OTX: 4 refs 11/09/2026 WalletConnect CDN
API
Bureau d’enregistrement
NiceNIC
Resolved IP
172.67.190.27
Registered
10/09/2026
3 sources
The capture source is temporarily unavailable.
1 / 3
Source
Primary capture
Collected · UTC
Open capture
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 9. Listes de blocage publiques signalant une correspondance : 2. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
Résumé du rapport

walletconnectgate.com — Non vérifié. Usurpation de l'identité de la marque : WalletConnect; Type d'arnaque : Crypto Drainer; Drainer: Wallet Connect Abuse. Résumé des preuves: VirusTotal 9/89 (ChainPatrol, alphaMountain.ai, Chong Lua Dao, CRDF, Forcepoint ThreatSeeker); Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. Bureau d’enregistrement: NiceNIC.

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Additional indicators at a glance
Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
9 det.
OTX references
4 community refs
URLScan
URLScan
Signaler ↗
ScamAdviser
Scamadviser
15/100Very Likely Unsafe
Certificat TLS
Expiré ou non vérifié
Âge
1 mo New
PhishDestroy
DestroyList
Répertorié

Source evidence

9 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

9 / 89

Signaler
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Scamadviser

15/100

Observation time not recorded
Signaler
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

2 external matches

Détails
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

4 community references

Signaler
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Signaler
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

rapport stocké

View stored capture ↗
Signaler
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analyse terminée

Signaler
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Signaler
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Renseignements sur la sécurité réseau Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Résumé des preuves

Critique
VirusTotal
9/89
OTX
4 community refs
URLScan
Stored capture

Stored narrative · generated . Provider checks below retain their own observation dates.

Assessment

Stored evidence for walletconnectgate.com: VirusTotal recorded 5 detections among 89 scanners on 2026-09-11. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for walletconnectgate.com. Each item in this report remains at the scope supplied by its dated source record.

Read the full analysis6

Detection Evidence

VirusTotal records 5 detections among 89 scanners in the stored snapshot dated 2026-09-11. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-11 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.

Source Context

MetaMask and SEAL are recorded as named external blocklist observations for walletconnectgate.com in the snapshot dated 2026-09-11. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains walletconnectgate.com as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.

Reachability and Timeline

The record first observed walletconnectgate.com on 2026-09-11. The MetaMask and SEAL blocklist snapshot is dated 2026-09-11 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-10. A URLScan reference was stored on 2026-09-11 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.

Registration and Infrastructure

For walletconnectgate.com, the registrar field records NICENIC INTERNATIONAL GROUP CO., LIMITED; this is kept as an exact source value. The source stores 172.67.190.27 as the observed address in this record. The registration date for walletconnectgate.com is recorded as 2026-09-10. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.

Conclusion

The walletconnectgate.com record states that VirusTotal recorded 5 detections among 89 scanners on 2026-09-11. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-11. PhishDestroy remains a separate publisher catalogue entry in the stored record. For walletconnectgate.com, the registrar field records NICENIC INTERNATIONAL GROUP CO., LIMITED; this remains separate from the other source fields. The observed address field in this record contains 172.67.190.27. The supported conclusion is bounded to the exact stored observations for walletconnectgate.com. Any statement beyond those source values would require additional dated material.

Recommended Actions

Avoid submitting sensitive information to walletconnectgate.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain walletconnectgate.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to walletconnectgate.com. The stored record does not justify extending that rule to 172.67.190.27 or to other infrastructure records.

Data coverage & collection19 · datasets with records / 12 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
9 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
2 · external matches
Cloudflare Radar
sainCollection time not recorded
Scamadviser
15/100 · provider trust scoreCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
NICENIC INTERNATIONAL GROUP CO., LIMITEDCollection time not recorded
Network & DNS
172.67.190.27 · 2 · nameserversCollection time not recorded
Certificat TLS
Let's Encrypt / YE2
Page captures
3 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
100/100 · mobile performance
Availability history
48 · stored state changes
Source observation history
2 · stored source events
IP reputation
Network-level observations
Not recorded in this report 12

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Signalements communautaires
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.
Blocklist records2 · external source matches

Statut de la liste de blocage publique

Domain, network & archiveNICENIC INTERNATIONAL GROUP CO., LIMITED · 172.67.190.27 · DNS, TLS and retained responses

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainesdrainerfraudlivemonthlyphishdestroyphishingscam
Bureau d’enregistrement NiceNIC RU(RU) PhishDestroy Investigation
Contact anti-abusabuse@nicenic.net
Registre de l'ICANNICANN Lookup (RDAP) →
Recherche WHOISICANN RDAP pour walletconnectgate.com →
EnregistrementCréé 10/09/2026 (35d · New) — Expires 10/09/2027
Elapsed Since First Report 2 days
Ce que nous comptons Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Non vérifié.
Ce que contient chaque rapport Les enregistrements de rapports sortants stockés peuvent faire référence à des preuves disponibles à ce moment-là, telles que les verdicts des fournisseurs, les données d'enregistrement, les détails d'hébergement, les classifications ou les captures d'écran. Cette page ne déduit pas la charge utile exacte livrée, la réception, l'accusé de réception ou l'action d'un destinataire.
Détails techniquesProvenance & timestamps
Première détection11/09/2026
DOM Analysisanalyzed 11/09/2026score 100/1001 brand signal
Submitted URLhttp://walletconnectgate.com/
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.190.27
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 2

  • martin.ns.cloudflare.com
  • sunny.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt / YE2
Valid from
2026-09-10 09:19:40
Valid until
2026-12-09 09:19:39
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-09-11 10:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint76e27eb1d05bac40e13f277b09596b4b175975c88a5f1370e69d52ccd31cdd0c

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 172.67.190.27rapiddns.io

Latest Classified Outcome 2026-10-15 20:22:19 UTC

Primary outcome DNS inactif reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Inconnu Probe Inconclusive 20% 2026-10-15 10:48:38 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-09-12 23:03:10 UTC last content: 2026-09-12 23:03:10 UTC current episode first observed: 2026-09-13 06:07:31 UTC observed RIP window: 2026-09-12 23:03:10 UTC → 2026-09-13 06:07:31 UTC · 7.07h midpoint estimate ≈ 2026-09-13 02:35:20 UTC · precision medium · 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
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

9 / Les fournisseurs de sécurité 89 ont signalé ce domaine
View on VT
Last analyzed Previous stored snapshot: 5 detections
ChainPatrol
alphaMountain.ai
Chong Lua Dao
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
VIPRE
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of walletconnectgate.com · checked Sep 11, 2026

100
Good
Performance
FCP
0.84s
First Contentful Paint
LCP
0.84s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.18s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
7.07
Estimate basis
Bounded by observations
Estimate precision
Moyen

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checksStored browser and crawler observations
Analyse de la détection et de l'évasion

Vérification du cloaking et de la répartition du trafic

Pas encore numérisé Aucune différence entre les robots d'indexation et les navigateurs n'a encore été constatée

Enregistrement des observations « crawler contre navigateur » pour cet hôte, ainsi qu'une vérification en temps réel des empreintes numériques pour les systèmes de répartition du trafic de type Keitaro.

Indicateur de camouflage enregistré
Pas encore numérisé
Dernier scan de camouflage

Note relative à la numérisation: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='walletconnectgate.com', port=80): Max retries exceeded with url: / (Caused by NewConnectio

Vérification en direct des empreintes digitales d'TDS
Sept empreintes Keitaro ainsi qu’une comparaison entre robot d’indexation et navigateur, générées par le scanner PhishDestroy lorsque ce panneau est ouvert.
En attente
Timeline & responseCollection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-09-13 10:03:34 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. Threat First Observed 2026-09-11 09:54:30 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.190.27.
Stored observation history50

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  3. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  5. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

Earlier observations 45
  1. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  2. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  4. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  6. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  8. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  10. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  11. Availability monitor · Recorded state

    dns_inactive→Inconnu

    origin_unreachable · http_5xx

  12. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  13. Availability monitor · Recorded state

    dns_inactive→Inconnu

    origin_unreachable · http_5xx

  14. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  15. Availability monitor · Recorded state

    dns_inactive→Inconnu

    origin_unreachable · http_5xx

  16. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  17. Availability monitor · Recorded state

    dns_inactive→Inconnu

    origin_unreachable · http_5xx

  18. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  19. Availability monitor · Recorded state

    dns_inactive→Inconnu

    origin_unreachable · http_5xx

  20. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  21. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  22. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  23. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  24. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  25. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  26. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  27. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  28. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  29. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  30. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  31. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  32. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  33. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  34. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  35. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  36. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  37. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  38. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  39. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  40. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  41. Availability monitor · Recorded state

    dns_inactive→Inconnu

    probe_inconclusive

  42. Availability monitor · Recorded state

    Inconnu→dns_inactive

    dns_nxdomain

  43. Availability monitor · Recorded state

    Inconnu

    probe_inconclusive

  44. Availability monitor · Recorded state

    Accessible→Indisponible

  45. Availability monitor · First collection record

    Accessible

Processus de réponse aux menaces Pipeline

Découverte
Analysis
Monitoring

13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Menace détectée
walletconnectgate.com détectés et mis en file d'attente en vue d'une analyse complète
11/09/2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
11/10/2026
URLScan.io Capture
Enregistré URLScan report with capture artifacts
11/09/2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
9/89 recorded on VirusTotal
13/09/2026
Détection des listes noires
Trouvé dans 2 blocklists: MetaMask, SEAL
16/10/2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
11/10/2026
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Drainer Identified
Utilisation abusive de Wallet Connect wallet drainer — impersonating WalletConnect
11/09/2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
11/09/2026
Technical Analysis Recorded
Le rapport contient des résultats de technologie ou d’analyse médico-légale stockés.
16/10/2026
Content Observed Unavailable
La surveillance a enregistré une réponse indisponible ; la cause n’a pas été établie de manière indépendante.
13/09/2026
DestroyList publié
Listed in the public PhishDestroy/DestroyList repository
11/09/2026
How we investigate & report

Public scans, evidence and abuse channels

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecÉvaluation du site AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Statut de la liste de blocage publique

Related infrastructureShared hosting, registrar records and related domains
Evidence & investigation toolsOriginal reports, independent checks and evidence links

Données factuelles et rapports externes

Analyse de sécurité
URLScan Analyzed VirusTotal 9 det. ChainPatrol URLQuery Scamadviser 15 trust SSL Laboratoires Hostname coverage not recorded CF Radar Ouvrir le rapport OTX 4 refs WOT Vérificateur de liste noire URL nulle Sucuri SiteCheck Observatoire MDN
OSINT et renseignement
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certificats WHOIS Wayback
DNS et réseau
nslookup.io DNS bgp.tools ASN /Itinéraire
Référencement naturel et nom de domaine
SpyFu Moz DA/PA Ahrefs Liens entrants
Analyse approfondie
Analyse approfondie
Signaler
ChainAbuse
Help & reportingRecovery steps, reporting contacts and complaint drafts

Ce site vous a-t-il affecté ?

5 evidence signal groups linked 0 reports recorded Non vérifié
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si vous avez interagi avec ce domaine, saisi des informations personnelles ou connecté un portefeuille de crypto-monnaie, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Europol
Trouvez le canal de signalement officiel pour votre pays de l'UE
National police directory
Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL -ISAC
Security Alliance crypto threat intelligence
PhishDestroy listing review Pas un rapport des forces de l'ordre
Recours en matière de nom de domaine
Demandez un examen si vous possédez ce domaine et pensez que la liste est incorrecte
Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. Aucun service légitime ne peut garantir la récupération des cryptomonnaies volées. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

Template-based draft · optional AI wording assistance requires separate consent

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même

Vérifier n'importe quel domaine

Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique

Scanner maintenant

Signaler une tentative d'hameçonnage

Signalez les domaines suspects à notre base de données des menaces — protégez la communauté

Signaler

Flux d'alertes en temps réel

Rapports de phishing récents et changements de disponibilité observés

Surveiller

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce

Recommandations et conseils à l'intention des victimes

On estime que $51 billion ont été transférés vers des portefeuilles de cryptomonnaies illicites en 2024 (source). Si vous avez interagi avec walletconnectgate.com — Agissez dès maintenant.

Que dois-je faire tout de suite ?
Urgent
  • Révoquer les autorisations de jetons — use revoke.cash pour supprimer l'accès accordé à des contrats intelligents malveillants
  • Transférer les fonds restants vers un tout nouveau portefeuille. Le portefeuille compromis n'est plus sûr
  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage
Quelles informations dois-je rassembler pour mon rapport ?
Directives du FBI

Selon le FBI, les éléments les plus importants sont les données relatives aux transactions :

  • Adresses de cryptomonnaie — le portefeuille de l'escroc (par exemple, 0x5856...35985)
  • Montant et type de cryptomonnaie — montant exact (par exemple, 1,02345 ETH, 0,5 BTC, 500 USDT)
  • Identifiant de transaction (hachage) — l'identifiant unique de la transaction sur la blockchain
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment walletconnectgate.com)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

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.

À qui dois-je signaler cette arnaque ?
  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Chainabuse — signaler les portefeuilles frauduleux sur les différentes bourses et plateformes
  • Votre plateforme d'échange de cryptomonnaies — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

Comment fonctionnent généralement les escroqueries liées aux cryptomonnaies ?
  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Approbations malveillantes — Des invites « connect wallet » qui permettent aux pirates de dépenser un nombre illimité de jetons
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Fausses publicités et airdrops — Les publicités sur Google et les réseaux sociaux, ainsi que les offres de « jetons gratuits », qui mènent à des applications qui vident le portefeuille
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter
Comment puis-je me protéger à l'avenir ?
  • Utilisez un portefeuille matériel (Ledger, Trezor). Ne conservez jamais de grosses sommes dans des portefeuilles de navigateur
  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Lire chaque autorisation — Vérifier les autorisations avant la signature. Refuser les validations illimitées
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html 
<iframe
  src="https://phishdestroy.io/fr/embed/domain/walletconnectgate.com"
  title="PhishDestroy threat report for walletconnectgate.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>