# PhishDestroy threat dossier — idikale163-source.github.io ================================================================ Fetched: 2026-07-13 08:20:50 UTC Canonical: https://phishdestroy.io/domain/idikale163-source.github.io/ ## VERDICT ---------------------------------------------------------------- TAKEN DOWN (neutralised) Composite threat score: 100/100 (PhishDestroy scoring — see methodology below) Scam classification: Credential Phishing ## DETECTION EVIDENCE ---------------------------------------------------------------- VirusTotal: 0/91 security vendors flagged this domain Public blocklists: listed on 3 independent blocklists ## INFRASTRUCTURE ---------------------------------------------------------------- IP address: 185.199.108.153 (US, San Francisco) ASN: ASAS54113 FASTLY - Fastly, Inc., US Hosting org: AS54113 Fastly, Inc. Registrar: GitHub, Inc. Nameservers: NS_NOT_FOUND Registered: 2026-06-23 Page title: Csy-OS 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 ---------------------------------------------------------------- Domain registered: 2026-06-23 (per WHOIS / CT — may reflect a renewal or transfer date, not first-ever registration) First detected: 2026-06-25 19:10:19 UTC (by PhishDestroy tracker) Last verified: 2026-07-13 08:20:41 UTC Current status: taken down (registrar suspended or DNS dead) ## EXTERNAL CORROBORATION (third-party evidence) ---------------------------------------------------------------- URLScan.io: https://urlscan.io/result/019effc2-1b66-76be-a3b3-ec9dc83f5614/ Wayback Machine: https://web.archive.org/web/*/idikale163-source.github.io crt.sh CT logs: https://crt.sh/?q=%25.idikale163-source.github.io Google transparency: https://transparencyreport.google.com/safe-browsing/search?url=idikale163-source.github.io AlienVault OTX: https://otx.alienvault.com/indicator/domain/idikale163-source.github.io URLhaus: https://urlhaus.abuse.ch/host/idikale163-source.github.io/ ## ANALYST NARRATIVE ---------------------------------------------------------------- [Generated: 2026-06-25 19:17:49 UTC — narrative may predate facts above. Treat fields in TIMELINE / DETECTION EVIDENCE / INFRASTRUCTURE as authoritative if they differ from the prose below.] This domain, idikale163-source.github.io, is currently under investigation for hosting a credential harvesting phishing infrastructure. Analysis indicates the threat type is highly targeted, designed to mimic legitimate login portals to capture sensitive authentication credentials, including usernames, passwords, and multi-factor authentication tokens. The domain leverages GitHub Pages hosting, a tactic increasingly observed in low-detection phishing campaigns due to its perceived legitimacy and cost-free deployment. Infrastructure analysis reveals the following technical indicators: the domain has zero detections on VirusTotal (0/95 engines), suggesting evasion of traditional detection mechanisms. It is registered through GitHub, Inc., utilizing GitHub Pages infrastructure, which resolves to the IP address 185.199.109.153. The SSL certificate is issued by Let's Encrypt, providing HTTPS encryption that enhances the appearance of legitimacy. No creation date is publicly disclosed, and the domain remains unlisted on major blocklists, further complicating early detection efforts. Trust scores from automated analysis platforms are currently unavailable, reflecting its low-profile status. Mitigation against this specific threat type requires a multi-layered approach. Network-level protections should include blocking or monitoring traffic to the IP address 185.199.109.153, particularly for internal systems accessing GitHub Pages domains. Endpoint security measures should prioritize real-time behavioral analysis to detect anomalous credential submission patterns, such as repeated failed logins or submissions to untrusted domains. User awareness training must emphasize the risks of entering credentials on pages hosted under github.io subdomains, even if they appear visually identical to legitimate services. Security teams are advised to monitor for outbound connections to this domain and investigate any instances of credential reuse or unauthorized access following potential exposure. Proactive threat hunting should focus on identifying similar GitHub Pages-hosted phishing domains by analyzing DNS resolution patterns and SSL certificate issuance trends. ## EVIDENCE HASHES ---------------------------------------------------------------- Favicon MD5: 12f3b233cd266f886cd7b4c517e07743 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/idikale163-source.github.io/ JSON API: https://api.destroy.tools/v1/check?domain=idikale163-source.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: 178,033 domains (49,760 alive under monitoring, 128,273 confirmed takedowns/dead). Site: https://phishdestroy.io