delvaie[.]com

PhishDestroy first observed delvaie.com on Jun 29, 2026. Stored content metadata identifies Wetransfer as the apparent target. The captured page title is “Log in | WeTransfer:”. Current evidence score: 95/100 (critical).

Positive findings are stored from 5 sources: VirusTotal, Spamhaus DBL, DNS security resolvers, Cloudflare Radar, and URLScan. VirusTotal recorded 17 detections among 91 engines: ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, Fortinet, G-Data, Kaspersky, LevelBlue, Lionic, SOCRadar, Sophos on Jun 29, 2026 at 13:30 UTC. Spamhaus DBL: DBL_ABUSED_PHISH on Jun 29, 2026 at 18: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 phishing category; its verdict timestamp was not retained. URLScan returned a malicious verdict with score 100; scan metadata linked the capture to Wetransfer and assigned phishing as its category on Jul 29, 2026 at 03:01 UTC. Non-positive and contextual checks: The external blocklist snapshot contained no matches on Aug 7, 2026 at 22:20 UTC. URLQuery recorded no positive detection; no observation timestamp was retained. Google Safe Browsing returned no flag on Jun 29, 2026 at 13:25 UTC.

HTTP 502 was recorded on Aug 7, 2026 at 01:13 UTC; content was unavailable. Registration records for the domain list OwnRegistrar, Inc. as the registrar and Apr 28, 2025 as the creation date. At collection time, the hostname resolved to 159.195.47.52 on AS197540 (netcup GmbH). The recorded endpoint location is Nuremberg, DE. The stored server header is nginx/1.28.2. DOM analysis on Jun 29, 2026 at 14:20 UTC returned 88/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt as the certificate issuer with validity through Sep 22, 2026; checked Jun 29, 2026 at 16:00 UTC.

The content indicators and 5 positive source findings support the current Wetransfer impersonation and phishing classification. The target field identifies Wetransfer, but the record does not establish whether the page requested credentials, a seed phrase, or a wallet connection.