Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
murex.exchange favicon

murex.exchange

“Murex.exchange - Надежный онлайн обменник”

Bureau d’enregistrement
NameCheap
Resolved IP
91.108.190.226
Registered
17/05/2024
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 4/89 Type d'arnaque : Impersonation
OTX: 3 refs 27/07/2026
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 4. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Résumé du rapport

Domaine sur listes de blocage: murex.exchange — Dernier actif connu (HTTP 200). Résumé des preuves: VirusTotal 4/89 (alphaMountain.ai, Forcepoint…

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

Source evidenceVirusTotal 4 / 89 · OTX 3 references 5 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critique
VirusTotal
4 / 89
OTX
3 community refs
Page captures
2

PhishDestroy threat report

Overview

murex.exchange presents itself as a Russian-language currency exchange service. Its page title reads "Murex.exchange - Надежный онлайн обменник", meaning "reliable online exchanger." It targets Russian-speaking users who want to swap cryptocurrency or move money between assets. PhishDestroy classified it as an impersonation phishing page and first flagged it on 2026-07-27. As of 2026-10-19 the site was still online and serving live content.

How the scam works

Sites like this copy the look and language of a legitimate exchanger. The pitch is reliability, good rates and fast swaps. The victim picks a currency pair, receives a deposit address or payment details, and sends funds expecting the converted amount in return. In this kind of scheme the payout either never arrives or is held back behind invented "verification" or "withdrawal fees" that cost the victim even more. Anything sent to the operator's addresses is effectively lost, and the details entered along the way can be reused against the victim.

Evidence

Independent detection is thin so far. On 2026-09-14, 4 of 89 VirusTotal engines flagged the domain: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. Most security tools still treat it as clean, so a browser warning should not be expected. The domain appears in 3 AlienVault OTX threat pulses, which shows other researchers have tied it to malicious activity. Among the blocklists tracked here, it is listed by PhishDestroy.

Infrastructure

The domain was registered through NameCheap, Inc. on 2024-05-17, more than two years before PhishDestroy flagged it. An older domain can look established and slip past filters that focus on newly registered names. The site is hosted on the NetWarm LTD network in the United Kingdom. Its certificate comes from Let's Encrypt, so the browser padlock only means the connection is encrypted and says nothing about whether the operator is honest.

What to do

Do not send funds to murex.exchange, and do not pay any "fee" it requests to release a pending exchange. Paying only increases the loss. If you already sent money, stop all contact and save the deposit addresses, transaction IDs and any chat logs. Report the theft to your bank or the exchange you sent from, and to the police. If you created an account, change that password wherever you reused it and watch for follow-up "recovery" offers, which are a common second scam. Defenders should block the domain and its hosting IP at DNS and proxy level, and flag it in mail and chat filters aimed at Russian-speaking users.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Capture enregistrée · 2 captures

Observed page title
Murex.exchange - Надежный онлайн обменник
Automated brand references
Ethereum Solana Telegram Tron
Certificat TLS
Émis par Let's Encrypt · stored validity ends in 31 days

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
Réputation de l’IP abuse score 0/100 0 reports checked 11/10/2026
OTX tags 2026-07activeall-domainsblocklistcontentcryptodomainesdrainerfraudmonthlyphishdestroyphishingscam
Bureau d’enregistrement NameCheap US(US)
Contact anti-abus["abuse@namecheap.com"]
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 17/05/2024 — Expires 17/05/2028
Statut HTTP200
Détails techniquesProvenance & timestamps
Première détection27/07/2026
DOM Analysisanalyzed 18/09/2026score 81/1004 brand signals
Favicon Hash
ICANN OVERSIGHT

Contexte de l’accréditation et du RAA

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 Rien n’est envoyé automatiquement.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
91.108.190.226
Network ASN
AS201664
Organization
NetWarm LTD
Observed location
London, GB
Server header
nginx

Serveurs de noms 1

  • meilani.ns.cloudflare.com

Mail routing 1 MX record

  • mx.yandex.netpriority 10

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt
Valid from
2026-06-16 23:30:42
Valid until
2026-09-14 23:30:41
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-08-12 10:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprintd7e209aeb1ef7b74ce19a51bc2d7a81b42bacf258a4e69f28ae8a59da9f0e8ef
Certificate names · 1 SANs
  • www.murex.exchange

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

Latest Classified Outcome 2026-10-19 22:31:26 UTC

Primary outcome Contenu actif reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Contenu actif Ordinary HTTP content served 90% 2026-10-19 22:31:26 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-19 22:35:35 UTC last content: 2026-10-19 22:31:26 UTC
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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.murex.exchangeDomain record

The original observation time is not recorded for these hostnames.

Technologies · 9 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

4 / Les fournisseurs de sécurité 89 ont signalé ce domaine
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of murex.exchange · checked Aug 12, 2026

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

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Stored observation history20

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→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

Earlier observations 15
  1. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  6. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  7. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  8. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  9. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  10. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  11. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  12. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  13. VirusTotal · Detection count

    2→4

  14. VirusTotal · Detection count

    0→2

  15. Availability monitor · First collection record

    Accessible

Recorded activity

5 entries
  1. AlienVault OTX

    3 community references

    View source
  2. URLScan

    Page captured

    View source
  3. VirusTotal

    4/89 engine detections

    View source
  4. Google Safe Browsing

    No threat flag

    View source
  5. Added to PhishDestroy

    murex.exchange

    View source

Renseignement communautaire

1 signalement communautaire

CatégorieIMPERSONATION

This is a coordinated "frozen order" exchange scam operated through a Telegram account named "Flowisland Support." The group poses as a cryptocurrency exchange service. Method of operation: After a victim sends crypto for a swap (SOL to TRX), the operators claim the order is "fr

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

murex.exchange

Données factuelles et rapports externes

Community Scam Report — ChainAbuse
1 report filed for murex.exchange (1 written by a person) · category: Impersonation · source checked
“This is a coordinated "frozen order" exchange scam operated through a Telegram account named "Flowisland Support." The group poses as a cryptocurrency exchange service. Method of operation: After a victim sends crypto for a swap (SOL to TRX), the operators claim the order is "frozen" due to a fabricated network error — e.g. a "7th validator error" on Solana, or a claimed amount mismatch (5.55 vs 5.56 SOL). No such error exists; this is a pretext. They then demand the victim make a second ident”
— reported by Anonymous on Jul 17, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

4 evidence signal groups linked 0 stored notification records Dernier actif connu

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.

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.

Official reporting routes

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. 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
After a phishing incident

Recommandations et conseils à l'intention des victimes

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Que dois-je faire tout de suite ?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • 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

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.
  • 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 murex.exchange)
  • 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)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 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.

How do phishing scams typically work?

  • 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
  • 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
  • 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 ?

  • 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
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

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
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.

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/murex.exchange"
  title="PhishDestroy threat report for murex.exchange"
  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>