# PhishDestroy threat dossier — cr-001.github.io
================================================================

Fetched:   2026-07-28 22:55:03 UTC
Canonical: https://phishdestroy.io/domain/cr-001.github.io/

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

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

## 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-27 02:13:22 UTC (by PhishDestroy tracker)
Last verified:     2026-07-29 00:20:30 UTC
Neutralised:       2026-07-27 12:00:28 UTC
Current status:    taken down (registrar suspended or DNS dead)

## EXTERNAL CORROBORATION (third-party evidence)
----------------------------------------------------------------
URLScan.io:       https://urlscan.io/result/019fa0ef-1e57-736c-8238-8b05e754f4f6/
Wayback Machine:  https://web.archive.org/web/*/cr-001.github.io
crt.sh CT logs:   https://crt.sh/?q=%25.cr-001.github.io
Google transparency: https://transparencyreport.google.com/safe-browsing/search?url=cr-001.github.io
AlienVault OTX:   https://otx.alienvault.com/indicator/domain/cr-001.github.io
URLhaus:          https://urlhaus.abuse.ch/host/cr-001.github.io/

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

Is cr-001.github.io a Phishing Site?

Analysis indicates that the domain cr-001.github.io remains active as of the report date, July 27, 2026. DNS resolution returns the IPv4 address 185.199.108.153, which is part of the GitHub Pages hosting range operated by GitHub, Inc., the registrar listed for the domain. A nameserver lookup returned no records, yet the A‑record is functional, suggesting the domain is hosted on GitHub’s default infrastructure without custom name server configuration. The domain is listed on a single security blocklist and has been explicitly blocked by the PhishDestroy service, both of which categorize it as a phishing resource.

Google Safe Browsing also flags the site for social engineering, reinforcing the suspicion of credential‑harvesting activity. VirusTotal reports that the domain was scanned by 91 antivirus and URL‑reputation vendors; none of the vendors generated a detection at the time of scanning. While the lack of detections may indicate that the payload or page content was not yet identified by automated signatures, it does not constitute evidence of benign intent. No public page title, SSL certificate details, HTTP response codes, or additional threat‑intel identifiers such as OTX tags, brand references, or kit signatures are available from the current intelligence set.

Consequently, the precise phishing campaign vector, target brand, or credential‑collection mechanism cannot be confirmed without further content analysis. Given the confirmed blocklist entries, the PhishDestroy block, and the Google Safe Browsing social‑engineering flag, defenders should treat cr-001.github.io as a high‑risk phishing indicator. Recommended actions include adding the domain to outbound and inbound URL filtering rules, monitoring DNS queries for the associated IP address, and, where possible, employing sinkhole or redirect controls to prevent end‑user access. Continuous re‑evaluation is advised, as future scans or community reports may reveal additional malicious behavior.

## 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/cr-001.github.io/
JSON API:          https://api.destroy.tools/v1/check?domain=cr-001.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,137 domains (82,979 alive under monitoring, 124,126 confirmed takedowns/dead). Site: https://phishdestroy.io