accounts-google-login.github.io is a credential phishing page hosted on GitHub Pages that impersonated Google's account sign-in. It was built to catch Google users who expected a real login screen. PhishDestroy first saw it on 2026-09-08. It went offline on 2026-09-11, and on 2026-10-19 it was still dead with no content at its root.
How the scam works
The subdomain strings together "accounts", "google" and "login" so that a quick glance at the address bar suggests Google's own sign-in service. A victim who arrives from a lure such as a security alert, a shared document or a storage warning sees a copied Google login form and types in an email and password. Those details go straight to the operator, who can then take over Gmail, Drive, YouTube and any service that uses Google sign-in. Some kits also prompt for the one-time 2FA code and replay it immediately. The page title now reads "Site not found · GitHub Pages", which is GitHub's default for a removed site, while our classification is credential phishing.
Evidence
Sixteen of 89 VirusTotal engines flagged the address on 2026-09-15, including Google Safe Browsing, BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Emsisoft and alphaMountain.ai. Google Safe Browsing lists it under SOCIAL_ENGINEERING, which means Chrome and other browsers using that service warn visitors away. urlscan.io returned a malicious verdict and detected Google branding on the page. The domain is also on the PhishDestroy blocklist.
Infrastructure
The operator did not register a domain. They published the page on a free GitHub Pages subdomain, which runs on GitHub's Fastly-fronted network in the US. This setup costs nothing and inherits GitHub's trusted HTTPS, so a padlock and a reputable parent domain told victims nothing about whether the page was safe. The site lasted about three days after PhishDestroy first saw it, which is typical for throwaway pages on free hosting.
What to do
If you entered your Google password on this page, change it right away from the real Google account settings. Then review Security > Your devices and Recent security activity and sign out of any session you do not recognize. Turn on 2-Step Verification, preferably with a passkey or security key, and check Gmail forwarding rules and recovery email and phone settings for changes. Change the password on any other site where you used the same one. Defenders should block the subdomain, search mail and proxy logs for visits on and around 2026-09-08, and report any new look-alike GitHub Pages sites to GitHub for removal.
颁发者 Let's Encrypt· stored validity ends in 53 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
185.199.108.153
Network ASN
AS54113
Organization
Fastly, Inc.
Observed location
San Francisco, 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-08 10: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)
