metapay.facebook-secure.shop was a phishing page that impersonated Facebook's payment branding to target people selling items online. Its page title, written in Traditional Chinese and priced in Hong Kong dollars, was a fake sale confirmation aimed at sellers. PhishDestroy first detected it on 2026-09-15. It went offline on 2026-09-16, and as of 2026-10-19 its DNS was still inactive.
How the scam works
The page title reads "HK$ 380.00 | 你的商品 買家已經成功付款 請點擊確認訂單 進行收款", which means the buyer has paid for your item and you should click to confirm the order and collect the money. In this kind of scheme, a fake buyer sends the seller a link. The page, dressed up as a Facebook or Meta Pay checkout, then asks the seller to enter card numbers, bank login details or one-time codes to "receive" the payment. No money ever arrives. The details typed in are used to drain the seller's card or bank account, or to take over their Facebook account.
Evidence
On 2026-09-17, VirusTotal showed 9 of 89 engines flagging the domain, among them ESET, Fortinet, G-Data, Gridinsoft, CRDF, alphaMountain.ai, LevelBlue and SOCRadar. That is a modest count, but it comes from several independent vendors. urlscan.io rated the page malicious and recognized Facebook branding on it. Spamhaus lists the domain in its DBL as phishing, and it appears on the PhishDestroy blocklist.
Infrastructure
The domain was registered through Global Domain Group LLC on 2026-09-05, just ten days before we caught it. It was dead a day after that, a short lifespan typical of throwaway lure domains. The site was hosted in Germany on the Pusic Jurai network. Its Let's Encrypt certificate gave it a browser padlock, which shows the connection was encrypted, not that the site was genuine. The hostname is also built to look official: "metapay" and "facebook-secure" are placed in front of an unrelated .shop domain.
What to do
If you entered card or bank details on this page, call your bank now. Cancel the card and dispute any charges you don't recognize. If you shared a one-time code, tell the bank it was given to a fraudster. If you typed in Facebook credentials, change your password, turn on two-factor authentication and log out all other sessions. Remember that real marketplace buyers never need your card details to pay you, so treat any "click to collect payment" link as a scam. Defenders should block the domain, look for it in mail and messaging logs, and watch for similar hostnames that pair Meta or Facebook terms with cheap TLDs.
For the registrable domain facebook-secure.shop behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
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.
Certificate fingerprint788542e0a66591025c2a5681d5b6850b41ea553a3beb38b5045b67d1c9772cc1Certificate names · 2 SANs
sofbiserianes.cc
www.sofbiserianes.cc
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 비활성reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-19 01:14:09 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-09-15 22:18:04 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:18:04 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:29 UTC · precision low · basis bounded
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.
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 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 metapay.facebook-secure.shop)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.
