# PhishDestroy threat dossier — tinaajmire.github.io ================================================================ Fetched: 2026-07-28 19:31:37 UTC Canonical: https://phishdestroy.io/domain/tinaajmire.github.io/ ## VERDICT ---------------------------------------------------------------- TAKEN DOWN (neutralised) Composite threat score: 55/100 (PhishDestroy scoring — see methodology below) ## DETECTION EVIDENCE ---------------------------------------------------------------- VirusTotal: 9/91 security vendors flagged this domain Flagging vendors: CyRadar, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Netcraft, Sophos, Webroot 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: Spotify - Web Player: Music for everyone 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-24 11:02:19 UTC (by PhishDestroy tracker) Last verified: 2026-07-28 16:20:28 UTC Neutralised: 2026-07-24 12:27:43 UTC Current status: taken down (registrar suspended or DNS dead) ## EXTERNAL CORROBORATION (third-party evidence) ---------------------------------------------------------------- URLScan.io: https://urlscan.io/result/019f935c-07ba-700d-af8c-89208c756ee3/ Wayback Machine: https://web.archive.org/web/*/tinaajmire.github.io crt.sh CT logs: https://crt.sh/?q=%25.tinaajmire.github.io Google transparency: https://transparencyreport.google.com/safe-browsing/search?url=tinaajmire.github.io AlienVault OTX: https://otx.alienvault.com/indicator/domain/tinaajmire.github.io URLhaus: https://urlhaus.abuse.ch/host/tinaajmire.github.io/ ## ANALYST NARRATIVE ---------------------------------------------------------------- [Generated: 2026-07-24 11:02:44 UTC — narrative may predate facts above. Treat fields in TIMELINE / DETECTION EVIDENCE / INFRASTRUCTURE as authoritative if they differ from the prose below.] tinaajmire.github.io used for credential harvesting Analysis as of July 24 2026 indicates that the GitHub Pages subdomain tinaajmire.github.io remains active and is being leveraged for phishing. The domain is registered through GitHub, Inc., which is typical for GitHub Pages hosting. DNS resolution returns the IP address 185.199.108.153, consistent with GitHub’s infrastructure. VirusTotal reports that 9 of 91 scanned security vendors have flagged the domain, providing early detection of malicious content. Independent phishing feeds have added the domain to their lists; both PhishDestroy and OpenPhish currently block it, and the domain appears on two additional security blocklists. The nameserver information could not be retrieved (NS_NOT_FOUND), limiting further DNS‑based attribution. No public SSL certificate details, HTTP response codes, or page‑title information have been disclosed, leaving the exact content of the site unverified. Reputation services assign a high risk rating to the domain, aligning with the observed high‑risk classification. The available evidence points to a credential‑harvesting operation, but the specific target brand or login portal has not been identified. Uncertainty remains regarding the exact phishing page layout, the presence of any redirect chains, and whether the site employs additional infrastructure such as content delivery networks or command‑and‑control servers. Defenders should continue to block the domain at network perimeter devices, update URL filtering lists with the known blocklist entries, and monitor DNS queries for the associated IP address. Endpoint protection solutions should be configured to treat any detections from the nine VirusTotal‑reporting vendors as malicious. Organizations using GitHub Pages should enforce strict content‑approval workflows to reduce the risk of abuse. User awareness training should emphasize that any unsolicited request for credentials originating from a github.io URL should be treated as suspicious. ## 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/tinaajmire.github.io/ JSON API: https://api.destroy.tools/v1/check?domain=tinaajmire.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,124 domains (82,720 alive under monitoring, 124,372 confirmed takedowns/dead). Site: https://phishdestroy.io