mtoken[.]baby

PhishDestroy first observed mtoken.baby on Sep 5, 2026. Current evidence score: 78/100 (critical).

Positive findings are stored from 3 sources: VirusTotal, Cloudflare Radar, and URLQuery. VirusTotal stored 8 positive engine results: alphaMountain.ai, CRDF, Ermes, Emsisoft, Fortinet, Netcraft, OpenPhish, Webroot; the total engine count is unavailable or inconsistent, and no check timestamp is available. Cloudflare Radar classified the hostname as malicious and placed it in the phishing category; its verdict timestamp was not retained. URLQuery recorded 3 threat-system alerts on Sep 5, 2026 at 01:13 UTC. Non-positive and contextual checks: AlienVault OTX listed 4 community pulse references (not vendor detections) on Sep 5, 2026 at 01:47 UTC. The separate external-blocklist snapshot contained no matches on Sep 4, 2026 at 22:20 UTC. Google Safe Browsing returned no flag on Sep 5, 2026 at 01:45 UTC. URLScan captured the page on Sep 5, 2026 at 01:09 UTC.

The collector marked the hostname reachable on Sep 5, 2026 at 01:09 UTC, but did not retain the HTTP response code. Registration records for the domain list Dynadot Inc as the registrar and Sep 3, 2026 as the creation date. Registration preceded first observation by 1 day. At collection time, the hostname resolved to 23.145.152.44. The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and URLQuery; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt as the certificate issuer.

The record contains 3 positive source findings supporting the current phishing classification. The stored fields do not identify an impersonated brand or victim interaction.