# PhishDestroy threat dossier — manasakonnur-bit.github.io
================================================================

Fetched:   2026-07-13 06:37:39 UTC
Canonical: https://phishdestroy.io/domain/manasakonnur-bit.github.io/

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

## DETECTION EVIDENCE
----------------------------------------------------------------
VirusTotal:      6/91 security vendors flagged this domain
  Flagging vendors: Emsisoft, 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:     AS54113 Fastly, Inc.
Registrar:       GitHub, Inc.
Nameservers:     NS_NOT_FOUND
Registered:      2026-07-06
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
----------------------------------------------------------------
Domain registered: 2026-07-06 (per WHOIS / CT — may reflect a renewal or transfer date, not first-ever registration)
First detected:    2026-07-07 02:19:55 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/019f39f0-b259-70df-be0f-fdc078598fbb/
Wayback Machine:  https://web.archive.org/web/*/manasakonnur-bit.github.io
crt.sh CT logs:   https://crt.sh/?q=%25.manasakonnur-bit.github.io
Google transparency: https://transparencyreport.google.com/safe-browsing/search?url=manasakonnur-bit.github.io
AlienVault OTX:   https://otx.alienvault.com/indicator/domain/manasakonnur-bit.github.io
URLhaus:          https://urlhaus.abuse.ch/host/manasakonnur-bit.github.io/

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

This domain, manasakonnur-bit.github.io, is currently under investigation for credential harvesting phishing, a threat type targeting user authentication data through deceptive login interfaces. Analysis indicates the domain has not yet been flagged by security engines, with a detection ratio of 0/95 on VirusTotal, suggesting it may still be in the early stages of deployment or evading detection through obfuscation techniques.  Infrastructure analysis reveals the domain resolves to the IP address 185.199.108.153, a host associated with GitHub Pages, a legitimate content delivery network often exploited for phishing due to its trusted reputation. The domain is registered through GitHub, Inc., and utilizes a Let's Encrypt SSL certificate, which provides encryption but does not validate the legitimacy of the content served. As of the latest assessment, the domain remains active, with no blocklist entries or trust score downgrades recorded in public threat intelligence feeds.  Mitigation against credential harvesting phishing requires a multi-layered approach. Users and organizations should implement strict access controls, including multi-factor authentication (MFA) for all accounts, to reduce the impact of stolen credentials. Network-level protections, such as DNS filtering or web proxy policies, should block access to the domain and its associated IP. Security teams are advised to monitor for anomalous authentication attempts, particularly those originating from the IP 185.199.108.153, and conduct retrospective analysis of logs for prior exposure. Given the domain's current undetected status, proactive hunting for related indicators of compromise (IOCs) is recommended to identify potential breaches.

[Updates since narrative was generated:]
  - Public blocklists: now listed on 1 feed
  - VirusTotal detections: now 6/91 (narrative was written when count was lower)

## 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/manasakonnur-bit.github.io/
JSON API:          https://api.destroy.tools/v1/check?domain=manasakonnur-bit.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,020 domains (49,754 alive under monitoring, 128,266 confirmed takedowns/dead). Site: https://phishdestroy.io