ventran.xyz
“Ventran ($VENT) · Arbitrum whitelist”
Evidence Summary
PhishDestroy first observed ventran.xyz on Sep 27, 2026. Stored content metadata identifies Arbitrum as the apparent target. The captured page title is “Ventran ($VENT) · Arbitrum whitelist”. Page analysis recorded additional brand references to Across, Dexscreener, and Telegram. Stored page analysis classifies the content as impersonation. Current evidence score: 86/100 (critical).
One source contains a positive finding: VirusTotal. VirusTotal recorded 2 detections among 91 engines: alphaMountain.ai, SOCRadar on Sep 27, 2026 at 22:32 UTC. Non-positive and contextual checks: On Sep 27, 2026 at 22:32 UTC, AlienVault OTX listed 4 community pulse references (not vendor detections); Google Safe Browsing returned no flag. The separate external-blocklist snapshot contained no matches on Sep 27, 2026 at 22:20 UTC. URLScan captured the page on Sep 27, 2026 at 15:23 UTC.
The collector marked the hostname reachable on Sep 27, 2026 at 15:23 UTC, but did not retain the HTTP response code. Registration records for the domain list NAMECHEAP INC as the registrar and Sep 19, 2026 as the creation date. Registration preceded first observation by 8 days. At collection time, the hostname resolved to 216.150.1.1 on AS16509 (Amazon.com, Inc.). The IP and ASN identify shared Vercel edge infrastructure; the origin server is not established by this address. DOM analysis on Sep 27, 2026 at 18:20 UTC returned 86/100. The evidence archive retains 3 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt / YR2 as the certificate issuer with validity through Dec 18, 2026; checked Sep 27, 2026 at 16:02 UTC.
Stored content provides classification context, but only one source contains a positive finding.
Forensic History & Detection Timeline
-
VirusTotal Detections Update Sep 27, 2026 · 20:58 UTCVirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
-
Threat First Observed Sep 27, 2026 · 17:20 UTCDomain ingestion complete. Initial state is marked as alive pointing to IP
216.150.1.1.
Threat Response Pipeline
Public Blocklist Status
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scanned
No crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
- Stored cloaking flag
- Not yet scanned
Stored Capture · 3 sources
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Technologies · 3 identified
VirusTotal Analysis
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of ventran.xyz · checked Sep 27, 2026
Lookalike domains
28 stored lookalike domains
Show all (16)
Evidence & External Reports
Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive