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.
How the scam works
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.
Evidence
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.
Infrastructure
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.
What to do
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-19 01:55:25 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-19 01:55:25 UTClast content: 2026-10-19 01:55:25 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
기술 · 3 identified
R
React
JavaScript frameworks
React is an open-source JavaScript library for building user interfaces or UI components.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
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.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
FBI 지침
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 submitcase-92841074.com)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
지역 경찰 — 비록 당장 조치를 취할 수는 없더라도 공식 기록을 남깁니다
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
About this reportSources, observation dates and corrections
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.
(US)
