VirusTotal
5 / 92 engine detections
レポートを開くMEXCなりすまし: lakomex.com — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 5/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 92 engine detections
レポートを開く4 community references
レポートを開くScan report
レポートを開く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
lakomex.com is an impersonation phishing site. It borrows the identity of a legitimate service to win a visitor's trust and then harvest what that trust unlocks. PhishDestroy first flagged it on 2026-10-04, barely two weeks after the domain was created. As of 2026-10-19 the domain was still live and redirecting visitors onward, so the trap remains active.
Impersonation pages copy the look, wording and flow of a real brand closely enough that a hurried user does not notice the address is wrong. Victims usually arrive through ads, search results, direct messages or posts in community chats. The page then asks for whatever the real service would ask for, such as a login, a one-time code, a recovery phrase or a payment. The redirect on lakomex.com means the domain can act as a front door that forwards visitors to the actual phishing content, which lets operators swap destinations without changing the link they spread. Anything typed into the page goes straight to the scammers, which can mean a hijacked account or an emptied wallet.
Independent detection is still thin. In a VirusTotal scan on 2026-10-15, 5 of 92 engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. It also appears in 4 AlienVault OTX threat pulses, so other researchers have linked it to malicious activity. For now PhishDestroy is the only blocklist carrying it. The low vendor count reflects how new the domain is, not proof that it is safe.
The domain was registered on 2026-09-18 through Fewmoretaps OU, which trades as Trustname.com. It was in our feed 16 days later, a short gap typical of throwaway domains built for quick campaigns. Traffic passes through Cloudflare's network, with the address geolocated to Canada. That means the server actually hosting the content stays hidden behind the proxy. The free Let's Encrypt certificate adds the browser padlock, which proves nothing about who runs the site.
If you entered a password on lakomex.com, change it immediately on the genuine service and on any site where you reused it. Then turn on app-based two-factor authentication and sign out of all active sessions. If you typed a wallet recovery phrase, treat that wallet as compromised and move your funds to a new wallet created from a fresh phrase. If you paid anything, contact your payment provider or exchange right away and keep screenshots. Security teams should block the domain and anything it redirects to at the DNS or proxy level, and report the redirect chain to Cloudflare and the registrar.
Edge-IP の評判はこのドメインに起因しません。
shane.ns.cloudflare.comLocation describes the IP network.
aac29937fab8d03c8ce80a4f1bc835ab312ad7a3d991038dda3dc695150d26edSaved 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.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
No threat flag
View source5/92 engine detections
View source4 community references
View sourcelakomex.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
lakomex.com
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 ↗
lakomex.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.