VirusTotal
10 / 89 engine detections
Ouvrir le rapport“Service Status”
Usurpation de MetaMask: morpjho.org — Accessible · accès restreint (HTTP 403). Résumé des preuves: VirusTotal 10/89 (ChainPatrol, alphaMountain.ai, CRDF…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
10 / 89 engine detections
Ouvrir le rapportDBL_PHISH
Malveillant
Ouvrir le rapport3 community references
Ouvrir le rapportprovider verdict: clean
Ouvrir le rapportNo threat flag
Ouvrir le rapportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
morpjho.org is an impersonation phishing page that presented itself under the title "Service Status". urlscan.io matched its layout to a generic Cloudflare page. Crypto-focused blocklists from MetaMask and SEAL picked it up, which points to wallet users as the intended audience. PhishDestroy first saw it on 2026-08-21. The site has been offline since 2026-09-16, with its content blocked by the provider, and it was still dead at the last check on 2026-10-19.
Pages like this borrow the look of a familiar infrastructure screen, such as a status notice or a Cloudflare check. The goal is to make a visitor believe they are going through a routine step. The "Service Status" title fits that pattern. The visitor is then pushed toward an action that hands over control, such as entering credentials or a recovery phrase, or connecting and signing with a wallet. Whatever gets entered or approved goes to the operator, not to any real service.
Ten of 89 VirusTotal engines flagged the domain as of 2026-09-13. The flagging vendors include ChainPatrol, alphaMountain.ai, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and LevelBlue. That is a modest count, but several of those vendors specialize in crypto threats, which matters more here than raw volume. urlscan.io returned a malicious verdict, Spamhaus lists the domain in its DBL as phishing, and it appears in three AlienVault OTX threat pulses. On top of the PhishDestroy listing, both MetaMask and SEAL blocklist it.
The domain was registered through Gname.com Pte. Ltd. It resolved to 188.114.97.9 on Cloudflare's network, geolocated to Canada. That means the origin server sat behind Cloudflare's proxy rather than being exposed directly. Its certificate came from Google Trust Services (WE1), the issuer Cloudflare routinely provisions, so the padlock says nothing about who ran the page. The operator chose a meaningless, typo-like name rather than a brand lookalike, which suits a page that relies on a generic status screen for credibility.
If you typed a password or recovery phrase into this page, treat that account or wallet as compromised. Change the password and reset 2FA, or move any funds to a newly created wallet. If you connected a wallet or signed anything, revoke token approvals granted around your visit using a reputable approval checker. Never re-import a seed phrase you entered here. Defenders should block morpjho.org at DNS and proxy level and search logs for visits after 2026-08-21. Be wary of other look-alike "status" or verification screens that ask for wallet connections.
Last checked
La réputation Edge-IP n’est pas attribuée à ce domaine.
ram.ns.cloudflare.comLocation describes the IP network.
ce93b085d873c59c3295a3f372e2e4272f4308d492fba29430db66306eb7e66eSaved 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
morpjho.org
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Accessible→Indisponible
Accessible
3 community references
View sourceNo threat flag
View source10/89 engine detections
View sourcemorpjho.org
View source79 domaines ressemblants enregistrés
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 ↗
morpjho.org)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.