VirusTotal
10 / 89 engine detections
レポートを開く“Service Status”
MetaMaskなりすまし: morpjho.org — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 10/89 (ChainPatrol, alphaMountain.ai, CRDF, CyRadar, Forcepoint ThreatSeeker)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
10 / 89 engine detections
レポートを開くDBL_PHISH
悪意あり
レポートを開く3 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults 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
Edge-IP の評判はこのドメインに起因しません。
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.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
到達可能
3 community references
View sourceNo threat flag
View source10/89 engine detections
View sourcemorpjho.org
View source保存された類似ドメイン:79 件
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.