VirusTotal
5 / 92 engine detections
レポートを開く“WhatsApp”
WhatsAppなりすまし: z1me4.shop — 未検証. 証拠の概要: VirusTotal 5/92 (alphaMountain.ai, CRDF, Gridinsoft, OpenPhish, SOCRadar); URLScan malicious verdict; Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 92 engine detections
レポートを開くDBL_PHISH
悪意あり
レポートを開く5 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
z1me4.shop is an impersonation phishing page dressed up as WhatsApp, with the browser tab simply reading "WhatsApp". It targets ordinary WhatsApp users, and through them their contacts. PhishDestroy first flagged it on 2026-10-11. As of 2026-10-19 the domain no longer resolves in DNS, so the page is offline for now. The domain itself can still be pointed at a server again.
Fake WhatsApp pages usually copy the look of the official web login or verification screens. They ask the visitor for a phone number and the SMS verification code, or to scan a QR code that quietly links the attacker's device to the victim's account. Once inside, the operator can read chats and impersonate the victim. A common follow-up is messaging friends and family with urgent requests for money or crypto. The victim loses control of the account, and their contacts become the next targets.
Five of 92 VirusTotal engines flagged the domain on 2026-10-12: alphaMountain.ai, CRDF, Gridinsoft, OpenPhish and SOCRadar. That count is modest, but it includes a dedicated phishing feed. urlscan.io rated the page malicious and recognised the WhatsApp branding on its own. Spamhaus lists the domain in its DBL as phishing, and it appears in five AlienVault OTX threat pulses alongside the PhishDestroy blocklist.
The domain was registered on 2026-08-24 through GNAME.COM PTE. LTD. It went live as a phishing page roughly seven weeks before we caught it. That gap suggests the domain was bought ahead of time and held until the campaign was ready. Hosting sat on Tencent's network in Hong Kong at 43.129.237.150. The random-looking name on a cheap .shop extension fits disposable domains that are burned and replaced quickly.
If you entered a verification code or scanned a QR code on this page, open WhatsApp, go to Linked Devices and log out any session you don't recognise. Then re-verify your number on your own phone and turn on two-step verification with a PIN. Warn your contacts that messages asking for money may not be from you. If you already sent money because of such a message, contact your bank or payment provider. Defenders should block z1me4.shop and the hosting IP. They should also check DNS and proxy logs for visits since 2026-10-11 and remind staff that WhatsApp never asks for codes through a website.
For this gTLD, 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.
b3.share-dns.netLocation describes the IP network.
Saved 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.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
5 community references
View sourceNo threat flag
View source5/92 engine detections
View sourcez1me4.shop
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
z1me4.shop
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 ↗
z1me4.shop)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.