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.
Primary outcome비활성reason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: StaleRegistration: Unknown
Latest HTTP observation비활성Http No Content70%2026-10-19 01:11:37 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-09-04 14:36:01 UTCcurrent episode first observed: 2026-10-09 01:21:02 UTCobserved RIP window: 2026-09-04 14:36:01 UTC → 2026-10-01 01:32:04 UTC · 634.93hmidpoint estimate ≈ 2026-09-17 20:04:02 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
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.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
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.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 mohammadhaneef110.github.io)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
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)
