teleymmob[.]com

PhishDestroy first observed teleymmob.com on Jun 28, 2026. The captured page title is “Messenger”. Current evidence score: 95/100 (critical).

Positive findings are stored from 5 sources: VirusTotal, Spamhaus DBL, DNS security resolvers, Cloudflare Radar, and URLQuery. VirusTotal recorded 15 detections among 91 engines: ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, SOCRadar, Sophos, VIPRE on Jul 8, 2026 at 16:20 UTC. Spamhaus DBL: DBL_SPAM on Jun 28, 2026 at 22:30 UTC. DNS security checks returned 3 blocking results across 14 tested policies: Control D Adblock, Control D Family, Control D Malware; no observation timestamp was retained. Cloudflare Radar classified the hostname as malicious and placed it in the dga domains category; its verdict timestamp was not retained. URLQuery recorded 2 detections; no observation timestamp was retained. Non-positive and contextual checks: The external blocklist snapshot contained no matches on Aug 7, 2026 at 22:20 UTC. Google Safe Browsing returned no flag on Jun 28, 2026 at 14:45 UTC. URLScan completed without a malicious verdict (score 0) on Jul 29, 2026 at 03:01 UTC.

HTTP 502 was recorded on Aug 7, 2026 at 01:37 UTC; content was unavailable. Latest classified outcome: registration hold observed; cause registrar client hold; mechanism client hold; observed actor NICENIC INTERNATIONAL GROUP CO., LIMITED on Aug 7, 2026 at 02:23 UTC. Registration records for the domain list NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar and May 23, 2026 as the creation date. At collection time, the hostname resolved to 27.124.47.186 on AS152194 (CTG Server Limited). The recorded endpoint location is Sheung Wan, HK. The stored server header is nginx/1.18.0 (Ubuntu). DOM analysis on Jun 28, 2026 at 18:20 UTC returned 88/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Telegram as the certificate issuer with validity through Sep 14, 2028; checked Jun 28, 2026 at 16:00 UTC.

The content indicators and 5 positive source findings support the current phishing classification. The stored fields do not identify an impersonated brand or victim interaction.