mohammadhaneef110.github.io is a GitHub Pages project site that PhishDestroy classifies as impersonation phishing. It posed as a legitimate service to win the trust of visitors. We first flagged it on 2026-09-04, and it went offline the next day, 2026-09-05. It was still dead when we last checked on 2026-10-19. The root of the site now returns GitHub's "Site not found · GitHub Pages" title, which shows the project has been removed or unpublished. That title does not reflect the impersonation content we classified.
How the scam works
Impersonation pages copy the look, wording and logos of a brand people already trust, such as a wallet, an exchange or a support portal. Visitors are usually sent there through links in messages, social posts or search ads. The page then asks for something valuable: login credentials, one-time codes, personal details or a wallet recovery phrase. Whatever the victim types goes straight to the operator, who uses it to take over accounts or empty funds. Hosting on a github.io subdomain lends a borrowed sense of legitimacy and costs the operator nothing to set up or abandon.
Evidence
When VirusTotal scanned the site on 2026-09-05, 7 of 90 engines flagged it as malicious. The vendors were alphaMountain.ai, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Sophos. That is a modest count, but these are several independent vendors with their own detection pipelines, and they agreed within a day of our first sighting. Among the blocklists we track, the domain appears only on PhishDestroy's.
Infrastructure
The site sat on GitHub's shared Pages hosting at 185.199.108.153 in the United States. The parent domain is registered through GitHub, Inc., so the operator never had to buy a domain at all. Its certificate came from Let's Encrypt, which GitHub Pages issues automatically and which says nothing about who ran the page. A free throwaway account and a lifespan of about a day point to a disposable operation that can easily reappear under a new username.
What to do
If you entered a password on this page, change it right away on the real service and on any other site where you reused it. Then turn on app-based or hardware two-factor authentication. If you typed a wallet recovery phrase or private key, treat that wallet as compromised and move any remaining assets to a newly created wallet. Watch your accounts for unfamiliar logins or password-reset emails. Defenders should block the domain, hunt for other github.io pages that use the same branding, and report fresh copies to GitHub so they can be taken down quickly.
颁发者 Let's Encrypt· stored validity ends in 56 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
185.199.108.153
Observed location
US
Server header
GitHub.com
Edge-IP 声誉不属于此域。
Location describes the IP network.
TLS 证书
Issuer
Let's Encrypt
Valid from
2026-08-02 23:38:02
Valid until
2026-10-31 23:38:01
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-04 16:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84Certificate names · 3 SANs
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.
Fastly is a cloud computing services provider. Fastly's cloud platform provides a content delivery network, Internet security services, load balancing, and video & streaming services.
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（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.
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — 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)
