VirusTotal
16 / 91 engine detections
レポートを開く“MetaMask Login – Secure Access to Your Web3 Wallet”
認証情報フィッシング: metamsk-logi.created.app — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 16/91 (alphaMountain.ai, Chong Lua Dao, CRDF, CyRadar, Ermes); URLScan…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
16 / 91 engine detections
レポートを開く悪意あり
レポートを開く悪意あり
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
metamsk-logi.created.app is a credential phishing page that imitates MetaMask. Its title is "MetaMask Login – Secure Access to Your Web3 Wallet", and its hostname is a deliberate misspelling meant to pass a quick glance. It targets MetaMask users who search for a way to sign in or recover their wallet. PhishDestroy first saw it on 2026-09-19, and the page was still live and serving content when last checked on 2026-10-19.
MetaMask has no web login and never asks for your Secret Recovery Phrase on a website. Pages like this one exploit the belief that a wallet works like an online account. The fake portal asks for a password, the 12- or 24-word recovery phrase, or a private key, which it presents as an access or verification step. Whatever is typed goes straight to the operators. A recovery phrase gives them full control of every account derived from it, so they can empty the wallet from their own device without any further action from the victim.
Several independent sources back this classification. On 2026-09-29, 16 of 91 VirusTotal engines flagged the site, including ESET, Emsisoft, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, CyRadar, Ermes and Chong Lua Dao. urlscan.io returned a malicious verdict and identified MetaMask branding on the page. MetaMask's own blocklist and SEAL list the domain alongside PhishDestroy, which means the impersonated brand has confirmed the abuse.
The domain registration dates to 2023-07-12 through Name.com, Inc., more than three years before the phishing page surfaced. An old registration date is therefore no sign of legitimacy here. The site resolves to 216.150.1.129 on Amazon.com, Inc. network space in the US, and it serves a free Let's Encrypt certificate. The padlock in the browser only shows that the connection is encrypted, not that the site is genuine.
If you entered your recovery phrase or private key here, treat the wallet as compromised. Create a new wallet with a fresh phrase on a trusted device, then move any remaining assets to it immediately. Do not reuse the old phrase, and change any password you typed on the page anywhere else you use it. Ignore follow-up messages offering "recovery help", because those are often a second scam. Defenders should block metamsk-logi.created.app at DNS and proxy level, report it to the hosting provider, and remind users that MetaMask never requests a seed phrase through a website.
Last checked
For the registrable domain created.app behind this subdomain, 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.
Edge-IP の評判はこのドメインに起因しません。
ns2.vercel-dns.comLocation describes the IP network.
939dcd2ea88a9fb0cdc440fbfa55064376759753b259b34a3242d277c46010ebSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of metamsk-logi.created.app · checked Sep 19, 2026
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.
metamsk-logi.created.app
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
15→16
No threat flag
View source16/91 engine detections
View sourcemetamsk-logi.created.app
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 ↗
metamsk-logi.created.app)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.