The promo-fans-mx.github.io page mimics a Facebook login portal to collect user credentials under the guise of a fan community. If you submitted your password here, change your Facebook password immediately and check your account sessions.
More about the sources
Recorded security signals
Stored VirusTotal result: 8/92 engines flagged. Malicious: 7. Suspicious: 1. Analysis time (as stored): 2026-11-21 22:10 UTC. Retrieved (as stored): 2026-11-22 15:29 UTC. Listed by external blocklists: OpenPhish. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded promo-fans-mx.github.io on 2026-11-22. Stored VirusTotal result: 8/92 engines flagged. Malicious: 7. Suspicious: 1. Analysis time (as stored): 2026-11-21 22:10 UTC. Retrieved (as stored): 2026-11-22 15:29 UTC. Listed by external blocklists: OpenPhish. Risk: critical (evidence score 75/100). Registrar: GitHub. Do not enter credentials or connect a wallet.
URLScan capture · 2026-11-22 15:26 UTC · SHA-256 52bf9a60…c6922a3
PhishDestroy analysis, reviewed version
Facebook fan community login page layout
The page hosted at promo-fans-mx.github.io opens with the Facebook logo centered above the headline "Connectez-vous à Facebook pour rejoindre la communauté de fans" and the subtitle "Fans vérifiés uniquement. 20 secondes." Below this text, the interface provides two input fields labeled "E-mail ou numéro de téléphone" and "Mot de passe". A prominent blue button labeled "Se connecter" invites the visitor to submit their credentials. Additional links for password recovery and language selection appear near the bottom of the form.
Credential harvesting and security findings
The form directly collects login credentials by asking users to input their account email or phone number alongside their password. urlscan classified the page as malicious, and 8 of 92 engines on VirusTotal flagged it on 21 Nov 2026, including vendors like Fortinet, Sophos and Netcraft. Its PhishDestroy evidence score is 60/100 (high). Because facebook.com is the genuine platform address, this Github Pages subdomain is clearly not the official site and exists solely to capture login inputs.
Recommended actions for affected users
Visitors who entered their credentials into this form should immediately navigate to the official Facebook website to secure their accounts. Change your password, enable two-factor authentication, and review all active login sessions to terminate any unauthorized access. Never use links found in unsolicited messages or unofficial fan pages to access your accounts.
Source evidenceVirusTotal 8 / 924 sources
SourceResultRecorded · UTCOpen
VirusTotal
8 / 92 engine detections
Analysis:
Open report VirusTotalOriginal source recordObserved: 14 fields
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
AI title
promo-fans-mx.github.io — Facebook verified fan login form
AI description
promo-fans-mx.github.io requests Facebook credentials for a fan community, flagged by urlscan and 8 VirusTotal engines. Avoid submitting data.
AI summary
Facebook fan community login page layout The page hosted at promo-fans-mx.github.io opens with the Facebook logo centered above the headline "Connectez-vous à Facebook pour rejoindre la communauté de fans" and the subtitle "Fans vérifiés uniquement. 20 secondes." Below this text, the interface provides two input fields labeled "E-mail ou numéro de téléphone" and "Mot de passe". A prominent blue button labeled "Se connecter" invites the visitor to submit their credentials. Additional links for password recovery and language selection appear near the bottom of the form. Credential harvesting and security findings The form directly collects login credentials by asking users to input their account email or phone number alongside their password. urlscan classified the page as malicious, and 8 of 92 engines on VirusTotal flagged it on 21 Nov 2026, including vendors like Fortinet, Sophos and Netcraft. Its PhishDestroy evidence score is 60/100 (high). Because facebook.com is the genuine platform address, this Github Pages subdomain is clearly not the official site and exists solely to capture login inputs. Recommended actions for affected users Visitors who entered their credentials into this form should immediately navigate to the official Facebook website to secure their accounts. Change your password, enable two-factor authentication, and review all active login sessions to terminate any unauthorized access. Never use links found in unsolicited messages or unofficial fan pages to access your accounts.
Headers: Server: GitHub.com; Content type: text/html; charset=utf-8; Content security policy: default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'; Via: 1.1 varnish; X cache: HIT; X cache hits: 1; X served by: cache-fra-etou8220071-FRA
Questions about promo-fans-mx.github.io
Is promo-fans-mx.github.io a legitimate Facebook page?
No, this page is not affiliated with Facebook. The official domain for Facebook is facebook.com, whereas this site runs on github.io.
What happens if I entered my password on promo-fans-mx.github.io?
urlscan classified the page as malicious, and 8 of 92 engines on VirusTotal flagged it on 21 Nov 2026 because the page captures submitted login credentials. If you typed your password, attackers likely have immediate access to your account.
What should I do if I already submitted my credentials?
Log into the real Facebook website immediately to change your password and revoke access for any unknown connected devices or sessions.
URLScan · 2026-11-22 1 / 3 Used in the analysisSource file SHA-256: 52bf9a60…c6922a3SHA-256 of the prepared copy given to the model: cbd44af8…4a0c956Stored capture 2 / 3 Cloudflare Radar 3 / 3
SourceURLScan · 2026-11-22
Recorded
StateStored capture
HTTP status200
Final URLhttps://promo-fans-mx.github.io/comunidad-fans/
Edge-IP reputation is not attributed to this domain.
Nameservers 8
dns1.p05.nsone.net
dns2.p05.nsone.net
dns3.p05.nsone.net
dns4.p05.nsone.net
ns-1339.awsdns-39.org
ns-1622.awsdns-10.co.uk
ns-393.awsdns-49.com
ns-692.awsdns-22.net
TLS certificate
Issuer
YR1
Valid from
2026-09-30 23:44:46
Valid until
2026-12-29 23:44:45
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856Certificate names · 6 SANs
*.github.com
*.github.io
*.githubusercontent.com
github.com
github.io
githubusercontent.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-22 15:28 UTC.
Loads saved data; the suspicious site is not opened.
Captured network requests
#
Network request
HTTP method · status
Type
Uncompressed size
Response body SHA-256
Stored observation history1
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Domain monitor · First collection record
Reachable
All retained availability observations0
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
No retained observations are recorded.
Threat Response Pipeline
Discovery · recorded
Analysis · recorded
Monitoring · recorded
Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including promo-fans-mx.github.io)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
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?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
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.