VirusTotal
17 / 91 engine detections
レポートを開く“Meta Verified: Get the verified badge on Facebook”
Facebookなりすまし: submitcase-92841074.com — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 17/91 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, ESET)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
17 / 91 engine detections
レポートを開く悪意あり
レポートを開くDBL_PHISH
4 community references
レポートを開く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
submitcase-92841074.com is an impersonation phishing page that poses as Facebook, using the title "Meta Verified: Get the verified badge on Facebook" to lure creators, businesses and page owners who want the blue badge. PhishDestroy first saw it on 2026-09-16. On 2026-10-19 the site was still alive and serving its phishing content, so it remains an active threat.
The domain name pairs "submitcase" with a long number, which reads like an official case or ticket ID. That suits a lure built around account reviews and verification. Schemes like this usually reach victims through messages or ads that promise a verified badge or warn of a pending case. The victim is then asked to confirm their identity with a Facebook password, a two-factor code and sometimes personal or payment details. Anyone who complies can lose control of their account and any pages or ad accounts tied to it, which are then resold or reused to spread the same lure.
When VirusTotal checked the domain on 2026-09-29, 17 of 91 engines flagged it. Among them were BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, Chong Lua Dao, CRDF and Gridinsoft. That spread across mainstream antivirus vendors and specialist phishing feeds means the verdict does not rest on a single source. Spamhaus lists the domain in its DBL as a phishing domain (DBL_PHISH). It also appears in four AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered through Name.com, Inc. on 2026-05-25, nearly four months before PhishDestroy detected it. That gap suggests it was registered ahead of time and held until the campaign launched. It is hosted on Amazon.com, Inc. cloud infrastructure in Germany (63.176.8.218). The Let's Encrypt certificate gives the page a padlock, but that shows only that the connection is encrypted, not that the site is legitimate.
If you entered your Facebook password here, change it at once from the official app or site. Then review active sessions and log out any devices you don't recognize. Reset two-factor authentication, check that your recovery email and phone number haven't been changed, and audit page and Business Manager admin roles for unfamiliar people. Change the password on any other account that used the same one, and if you entered card details, contact your bank. Defenders should block the domain at DNS and proxy level. They should also search mail and chat logs for links to it and warn social media staff that Meta does not sell or grant verification through outside "case" sites.
Edge-IP の評判はこのドメインに起因しません。
dns4.p02.nsone.netLocation describes the IP network.
cd4cc55c91118a03ec3fab2352b73902e1c087ef531c26bb0218140da3515f03Saved 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.
submitcase-92841074.com
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
protected→live_content
content_served
live_content→protected
http_access_restricted · access_restriction
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
live_content→protected
http_access_restricted · access_restriction
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
17→18
4 community references
View sourceNo threat flag
View source17/91 engine detections
View sourcesubmitcase-92841074.com
View sourceListed 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 ↗
submitcase-92841074.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.