VirusTotal
2 / 89 engine detections
レポートを開くMetaMaskなりすまし: crypto-mll.netlify.app — コンテンツが利用できません (HTTP 404). 証拠の概要: VirusTotal 2/89 (alphaMountain.ai, Forcepoint ThreatSeeker); 2 external blocklist…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
2 / 89 engine detections
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
crypto-mll.netlify.app is an impersonation phishing page hosted as a free Netlify subdomain and dressed up as a crypto service. It was listed by MetaMask and SEAL, which points to cryptocurrency wallet users as the target. PhishDestroy first flagged it on 2026-09-03. The site went offline on 2026-09-11 and still served no content at its root when last checked on 2026-10-19.
Impersonation pages like this copy the look and wording of a legitimate crypto project or wallet so that visitors believe they are on the real service. The victim is then steered into an action that hands over control, typically typing a recovery phrase or private key into a fake form, or connecting a wallet and signing a transaction or approval. A leaked recovery phrase gives the operator full control of the wallet. A malicious signature lets them move tokens without further interaction from the victim.
Only 2 of 89 VirusTotal engines flagged the domain in the 2026-09-16 scan, alphaMountain.ai and Forcepoint ThreatSeeker. A clean result from most scanners should not be read as a sign of safety. The stronger signal comes from crypto-specific blocklists. MetaMask's phishing list and SEAL both include it alongside PhishDestroy, and both are maintained by teams that focus on wallet-targeting fraud.
The page lived on a netlify.app subdomain, which costs nothing to create and can be discarded quickly. That fits its roughly eight-day lifespan between first detection and going dark. Traffic was served from Amazon infrastructure in Germany, which is Netlify's own hosting backbone rather than anything chosen by the operator. The DigiCert certificate is the platform's standard certificate, so the padlock said nothing about who ran the page.
If you entered a recovery phrase or private key on this site, treat the wallet as compromised. Move any remaining funds to a new wallet with a freshly generated phrase, and never reuse the old phrase. If you connected a wallet and signed anything, review and revoke token approvals using a reputable approval-checking tool, and watch the address for unexpected transfers. Defenders should block the domain and keep an eye on similar netlify.app subdomains with crypto-themed names, since short-lived throwaway hosts like this one are routinely replaced.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478netlify.appSaved 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 crypto-mll.netlify.app · checked Sep 3, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
不明→inactive
http_no_content
到達可能→利用不可
1→2
0→1
到達可能
No threat flag
View source2/89 engine detections
View sourcecrypto-mll.netlify.app
View sourcePage captured
View source保存された類似ドメイン:79 件
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
crypto-mll.netlify.app
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 ↗
crypto-mll.netlify.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.