This was a phishing page posing as Facebook and aimed at Facebook users. Its browser tab showed Facebook's own web address as the page title, so it would pass a quick glance. PhishDestroy first saw it on 2026-09-07. The site went offline on 2026-09-16 and was still dead and unreachable when last checked on 2026-10-19.
How the scam works
Pages like this copy Facebook's look and title closely, then ask the visitor to log in, confirm their identity or fix a supposed account problem. Anything typed into the form goes to the operator, not to Facebook. The "ad" in the subdomain fits a common lure aimed at people who run Facebook pages or ad accounts, often framed as a policy warning or a review notice. A victim can lose control of the account, along with linked pages, ad budgets and the contacts the attacker can then target.
Evidence
When VirusTotal scanned the domain on 2026-09-17, 15 of 89 engines flagged it. The vendors included alphaMountain.ai, BitDefender, CyRadar, ESET, Emsisoft, Fortinet, G-Data and Kaspersky. That is a broad spread of independent security vendors agreeing the page was malicious, not one outlier verdict. PhishDestroy lists the domain on its own blocklist.
Infrastructure
The operator did not register a domain. The page ran on a free Cloudflare Pages subdomain, which can be set up in minutes. It resolved to 172.66.47.159 on Cloudflare's network, which geolocates to Canada. Cloudflare serves sites from many edge locations, so that country does not show where the operator is. About nine days passed between our first sighting and the site going offline, a short life typical of disposable phishing pages on free hosting.
What to do
If you entered your Facebook password on this page, change it right away from the official Facebook app. Use a new password on any other service where you used the same one. Turn on two-factor authentication, review active sessions and log out devices you don't recognize. Check your ad account, payment methods and page admin roles for changes you did not make. Security teams should block the domain, search mail and proxy logs for visits since 2026-09-07, and reset credentials for any user who reached it.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
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.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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)
