mvmnext-app[.]com

PhishDestroy first observed mvmnext-app.com on Aug 19, 2026. The hostname explicitly references Mvmnext; stored content metadata identifies the same apparent target. Stored page analysis classifies the content as impersonation. Current evidence score: 100/100 (critical).

Positive findings are stored from 6 sources: VirusTotal, MetaMask, SEAL, Spamhaus DBL, Cloudflare Radar, and URLScan. VirusTotal recorded 10 detections among 91 engines: BitDefender, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, LevelBlue, Netcraft, SOCRadar, Sophos, Webroot on Aug 20, 2026 at 02:06 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Aug 20, 2026 at 02:20 UTC. Spamhaus DBL: DBL_PHISH on Aug 20, 2026 at 02:30 UTC. Cloudflare Radar classified the hostname as malicious and placed it in the phishing category; its verdict timestamp was not retained. URLScan returned a malicious verdict with score 100; scan metadata linked the capture to Mvmnext and assigned phishing as its category on Aug 19, 2026 at 23:08 UTC. Non-positive and contextual checks: URLQuery recorded no positive detection; no observation timestamp was retained. Google Safe Browsing returned no flag on Aug 19, 2026 at 23:28 UTC.

The collector marked the hostname reachable on Aug 19, 2026 at 22:54 UTC, but did not retain the HTTP response code. Registration records for the domain list Name.com, Inc. as the registrar and Aug 18, 2026 as the creation date. Registration preceded first observation by 1 day. At collection time, the hostname resolved to 158.94.208.174. The recorded endpoint location is Frankfurt am Main, DE. The stored server header is nginx. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt as the certificate issuer.

The content indicators and 6 positive source findings support the current Mvmnext-themed impersonation classification.