# PhishDestroy threat dossier — yahya-masood.github.io
================================================================

Fetched:   2026-07-29 02:56:45 UTC
Canonical: https://phishdestroy.io/domain/yahya-masood.github.io/

## VERDICT
----------------------------------------------------------------
TAKEN DOWN (neutralised)
Composite threat score: 78/100 (PhishDestroy scoring — see methodology below)

## DETECTION EVIDENCE
----------------------------------------------------------------
VirusTotal:      0/91 security vendors flagged this domain
Public blocklists: listed on 1 independent blocklist

## INFRASTRUCTURE
----------------------------------------------------------------
IP address:      185.199.108.153 (US, San Francisco)
ASN:             AS54113 Fastly, Inc.
Hosting org:     GitHub, Inc
Registrar:       GitHub, Inc.
Nameservers:     NS_NOT_FOUND
Page title:      Site not found · GitHub Pages
HTTP response:   404

## TLS CERTIFICATE
----------------------------------------------------------------
Issuer:     Let's Encrypt / YR2
Expires:    2026-09-02
Status:     INVALID chain
Fingerprint: 32491b26bfaf7bfb556029ef32299ac4374db34d09eecd4ffd01f21b2c5a8567
Subject Alternative Names (related infrastructure — often same operator):
  - github.com
  - github.io
  - githubusercontent.com

## ABUSE-REPORT HISTORY (evidence of registrar non-response)
----------------------------------------------------------------
Status: CLOSED — no report required.
This domain was neutralised before the abuse-report cycle could be dispatched — either
the hosting provider / registrar suspended it on their own, the DNS went dead, or the
operator abandoned the infrastructure. PhishDestroy keeps the evidence bundle on file
for audit but no formal notice was sent.

## TIMELINE
----------------------------------------------------------------
First detected:    2026-07-23 15:26:10 UTC (by PhishDestroy tracker)
Last verified:     2026-07-29 04:47:10 UTC
Neutralised:       2026-07-24 00:26:36 UTC
Current status:    taken down (registrar suspended or DNS dead)

## EXTERNAL CORROBORATION (third-party evidence)
----------------------------------------------------------------
URLScan.io:       https://urlscan.io/result/019f8f26-1903-7651-915a-943aa51c71e6/
Wayback Machine:  https://web.archive.org/web/*/yahya-masood.github.io
crt.sh CT logs:   https://crt.sh/?q=%25.yahya-masood.github.io
Google transparency: https://transparencyreport.google.com/safe-browsing/search?url=yahya-masood.github.io
AlienVault OTX:   https://otx.alienvault.com/indicator/domain/yahya-masood.github.io
URLhaus:          https://urlhaus.abuse.ch/host/yahya-masood.github.io/

## ANALYST NARRATIVE
----------------------------------------------------------------
[Generated: 2026-07-23 15:27:04 UTC — narrative may predate facts above. Treat fields in TIMELINE / DETECTION EVIDENCE / INFRASTRUCTURE as authoritative if they differ from the prose below.]

yahya-masood.github.io: GitHub Pages Hosted Phishing Endpoint

This domain, yahya-masood.github.io, is currently under investigation as a confirmed phishing endpoint hosted on GitHub Pages infrastructure. Analysis indicates the domain is actively resolving to 185.199.108.153, a known GitHub IP address range, and is registered through GitHub, Inc. The domain appears on one security blocklist (PhishDestroy) but has not been flagged by any of the 91 vendors that scanned it on VirusTotal as of the latest check. The absence of detections does not confirm safety, particularly given the domain's presence on a blocklist and the lack of nameserver records, which may indicate an attempt to obscure tracking or evade detection. Infrastructure review reveals the domain is leveraging GitHub's legitimate hosting service, a common tactic for phishing campaigns due to the free, trusted nature of the platform.

Defenders should note that GitHub Pages domains are frequently abused for credential harvesting, malware distribution, or social engineering attacks, though the specific content or target of this domain remains unconfirmed. The domain's active status and blocklist inclusion warrant immediate attention, particularly for organizations that permit GitHub Pages traffic. Recommended actions include blocking the domain at the network perimeter, monitoring for internal access attempts, and reviewing logs for connections to 185.199.108.153. If GitHub Pages is not required for business operations, consider restricting access to the entire *.github.io namespace.

Security teams should also investigate whether this domain has been used in recent phishing emails or messages, as GitHub-hosted phishing sites are often disseminated via email or social engineering. Further analysis of the page content is required to determine the exact phishing kit or brand impersonation, if any. Given the domain's active status and blocklist presence, defenders should treat it as malicious until proven otherwise.

## EVIDENCE HASHES
----------------------------------------------------------------
TLS cert SHA-256:      32491b26bfaf7bfb556029ef32299ac4374db34d09eecd4ffd01f21b2c5a8567

## SCORING METHODOLOGY
----------------------------------------------------------------
Composite score is NOT derived from VirusTotal alone. PhishDestroy aggregates:
  - VirusTotal positive ratio
  - Public blocklist consensus (MetaMask, ScamSniffer, OpenPhish, PhishTank, URLhaus,
    CryptoFirewall, SEAL, Polkadot, Enkrypt, Phishunt, DiscordPhishing, PhishingDB)
  - Cloaking detection (HTTP 666 or rendering delta between bot and real visitor)
  - DNS-filter consensus (Quad9, CleanBrowsing, NextDNS, AdGuard, Cloudflare, etc.)
  - AlienVault OTX pulses + Cloudflare Radar + Google Safe Browsing
  - URLScan / URLQuery verdicts
  - Brand-impersonation heuristics (DOM analysis of forms, logos, wording)
  - Known phishing-kit fingerprinting (favicon hash, JS obfuscation signatures)
  - Wallet-drainer family classification (Angel, MS, Rainbow, Pink, Inferno, ...)
  - Free-TLS vs paid-cert ratio (throwaway infrastructure signal)
  - Registrar/hosting abuse history (this registrar's track record)
  - Human researcher sign-off (operator takedown team)

A domain present in our database is ALREADY flagged. A low VT count by itself does
NOT mean the domain is safe — new scam domains routinely show 0/95 VT for their
first 7–30 days while actively draining wallets. Always cross-reference the composite
score and the individual indicators above, not just VT.

## CORRECTIONS / APPEALS
----------------------------------------------------------------
Full HTML report:  https://phishdestroy.io/domain/yahya-masood.github.io/
JSON API:          https://api.destroy.tools/v1/check?domain=yahya-masood.github.io
Appeal a flag:     https://phishdestroy.io/appeals/  (responded to within 48 hours, FP rate <0.01%)
Submit a report:   https://t.me/PhishDestroy_bot

About PhishDestroy: independent open-source threat-intelligence platform.
Tracked: 208,204 domains (82,853 alive under monitoring, 124,320 confirmed takedowns/dead). Site: https://phishdestroy.io