jpmorganchaseadmin.github.io is a credential phishing page that impersonated Chase. It sat on a free GitHub Pages subdomain under a name built to look like an official JPMorgan Chase admin portal. It targeted Chase banking customers. PhishDestroy first saw it on 2026-09-07, and it went offline on 2026-09-11, four days later. It was still dead at the last check on 2026-10-19.
How the scam works
Victims usually arrive through an email or text message claiming a problem with their Chase account. The message links to a page dressed in Chase branding that asks for a username and password, and often for one-time codes or personal details. Whatever is typed goes to the operators, who can then log into the real account, move money or reset recovery settings. The page now returns the title "Site not found · GitHub Pages", which reflects the removed content and differs from the phishing classification it earned while live.
Evidence
When VirusTotal was checked on 2026-09-16, 17 of 89 security engines flagged the site. They included BitDefender, ESET, Fortinet, Emsisoft, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai and Google Safe Browsing. Google Safe Browsing classed it as social engineering, which triggers browser warnings in Chrome, Firefox and Safari. urlscan.io returned a malicious verdict and detected Chase as the imitated brand. The domain is on the PhishDestroy blocklist.
Infrastructure
The page was hosted as a project on GitHub Pages and was served through Fastly's content delivery network in the US. Free developer hosting lets phishers launch a site in minutes under a trusted parent domain, with HTTPS already in place. That also explains the short lifespan: once the subdomain was reported, the content was pulled within days.
What to do
If you entered Chase credentials on this page, change your Chase password immediately from the official app or by typing the address yourself. Also change it on any other site where you reused it. Review your account for unfamiliar transfers, payees, linked devices and changed contact details. Call the number on the back of your card to report the incident and request fraud monitoring. Enable two-factor authentication through the Chase app rather than SMS where possible, and treat any follow-up calls or texts asking for codes as part of the same attack. Defenders should block the subdomain and look in mail logs for messages that linked to it.
颁发者 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-07 01:02:05 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)
