# PhishDestroy threat dossier — tuw-mujab.com ================================================================ Fetched: 2026-07-23 09:24:00 UTC Canonical: https://phishdestroy.io/domain/tuw-mujab.com/ ## VERDICT ---------------------------------------------------------------- CRITICAL THREAT — DO NOT VISIT Composite threat score: 100/100 (PhishDestroy scoring — see methodology below) ## DETECTION EVIDENCE ---------------------------------------------------------------- VirusTotal: 1/91 security vendors flagged this domain Flagging vendors: ChainPatrol URLQuery: 3 detections Public blocklists: listed on 3 independent blocklists ## INFRASTRUCTURE ---------------------------------------------------------------- IP address: 216.150.16.1 (US, Walnut) ASN: AS16509 Amazon.com, Inc. Hosting org: Vercel, Inc Registrar: Name.com, Inc. Nameservers: ns1.vercel-dns.com, ns2.vercel-dns.com Registered: 2026-07-12 Expires: 2027-07-12 Page title: Trust Card HTTP response: 308 ## TLS CERTIFICATE ---------------------------------------------------------------- Issuer: Let's Encrypt / YR1 Expires: 2026-10-10 Status: INVALID chain Fingerprint: 2841d5aa64b13aa08600e36765a890d4d8eebe6f073a9e8c5f8f183be44869af ## ABUSE-REPORT HISTORY (evidence of registrar non-response) ---------------------------------------------------------------- Status: pending notification queue. No abuse reports filed yet — this domain is waiting for the next cycle of our automated abuse-reporter. ## TIMELINE ---------------------------------------------------------------- Domain registered: 2026-07-12 (per WHOIS / CT — may reflect a renewal or transfer date, not first-ever registration) First detected: 2026-07-12 17:34:58 UTC (by PhishDestroy tracker) First reported: 2026-07-12 21:56:53 UTC (abuse notice filed) Last verified: 2026-07-23 08:20:25 UTC Current status: ACTIVE / observable ## EXTERNAL CORROBORATION (third-party evidence) ---------------------------------------------------------------- URLScan.io: https://urlscan.io/result/019f56f7-3fdc-75e4-85ac-3bf4f18ed7c8/ URLQuery: https://urlquery.net/report/da9dfe5a-5e68-4fa5-8c26-3f9a3dda4653 Wayback Machine: https://web.archive.org/web/*/tuw-mujab.com crt.sh CT logs: https://crt.sh/?q=%25.tuw-mujab.com Google transparency: https://transparencyreport.google.com/safe-browsing/search?url=tuw-mujab.com AlienVault OTX: https://otx.alienvault.com/indicator/domain/tuw-mujab.com URLhaus: https://urlhaus.abuse.ch/host/tuw-mujab.com/ ## ANALYST NARRATIVE ---------------------------------------------------------------- [Generated: 2026-07-12 17:50:12 UTC — narrative may predate facts above. Treat fields in TIMELINE / DETECTION EVIDENCE / INFRASTRUCTURE as authoritative if they differ from the prose below.] tuw-mujab.com — Generic Phishing Investigation The domain tuw-mujab.com was registered on July 12, 2026 through Name.com, Inc. and is currently resolving to the IPv4 address 216.150.16.1. The domain is delegated to the authoritative name servers ns1.vercel-dns.com and ns2.vercel-dns.com, which are typical of a cloud‑based hosting provider. As of the report date the domain remains active. Initial threat intelligence classifies the domain as a generic_phishing infrastructure. No publicly available samples have yet triggered detections on VirusTotal, resulting in a 0/95 detection count. The lack of detections does not imply benign intent, and the rapid creation‑to‑activation timeline is consistent with opportunistic phishing campaigns that rely on short‑lived domains. Infrastructure analysis shows a single hosting IP, 216.150.16.1, which is not currently associated with known malicious repositories. However, the use of a shared DNS service and a generic cloud host can facilitate rapid redeployment of malicious pages. The registrar information provides no indication of anonymization, suggesting the operator may be leveraging a legitimate registration to reduce immediate scrutiny. Defenders should consider adding the resolved IP address and the domain name to blocklists and monitoring egress traffic for connections to the host. Continuous DNS monitoring is recommended to detect any changes to the name server configuration or additional IP addresses that may be introduced. Further investigation of web content served from the host, including HTTP headers and page content, is advisable to confirm the phishing payload. Organizations that use brand‑specific authentication portals should educate users to verify URLs and implement multi‑factor authentication to limit credential compromise. Incident response teams should preserve any captured network artifacts and submit them to shared analysis platforms to enrich community knowledge of this emerging campaign. [Updates since narrative was generated:] - VirusTotal detections: now 1/91 (narrative was written when count was lower) ## EVIDENCE HASHES ---------------------------------------------------------------- PhishDestroy Case ID: PD-20260712-A2EE2C Favicon MD5: 4e9cc5eafe9d06f5e4548d19fb379db3 TLS cert SHA-256: 2841d5aa64b13aa08600e36765a890d4d8eebe6f073a9e8c5f8f183be44869af ## 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/tuw-mujab.com/ JSON API: https://api.destroy.tools/v1/check?domain=tuw-mujab.com 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: 188,658 domains (58,720 alive under monitoring, 128,313 confirmed takedowns/dead). Site: https://phishdestroy.io