Stored evidence for v2-exodus.com: VirusTotal recorded 15 detections among 89 scanners on 2026-09-15. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for v2-exodus.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 15 detections among 89 scanners in the stored snapshot dated 2026-09-15. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-15 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for v2-exodus.com in the snapshot dated 2026-09-19. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains v2-exodus.com as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed v2-exodus.com on 2026-09-13. The MetaMask and SEAL blocklist snapshot is dated 2026-09-19 and remains a separate event in the stored timeline. A stored HTTP status 502 was observed for v2-exodus.com on 2026-09-19. The HTTP status 502 dated 2026-09-19 records a single response for later comparison. The registration date is separately recorded as 2026-09-11. A URLScan reference was stored on 2026-09-14 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
For v2-exodus.com, the registrar field records Dominet (HK) Limited; this is kept as an exact source value. The source stores 94.154.35.225 as the observed address in this record. The registration date for v2-exodus.com is recorded as 2026-09-11. The SSL issuer is recorded as Let's Encrypt / YE1 in the snapshot dated 2026-09-13. The stored ASN observation records 202412 and Omegatech LTD in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The v2-exodus.com record states that VirusTotal recorded 15 detections among 89 scanners on 2026-09-15. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-19. PhishDestroy remains a separate publisher catalogue entry in the stored record. For v2-exodus.com, the registrar field records Dominet (HK) Limited; this remains separate from the other source fields. The observed address field in this record contains 94.154.35.225. The supported conclusion is bounded to the exact stored observations for v2-exodus.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to v2-exodus.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain v2-exodus.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to v2-exodus.com. The stored record does not justify extending that rule to 94.154.35.225 or to other infrastructure records.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='v2-exodus.com', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutError(
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 10:41:47 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:18:15 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Last analyzed Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Netcraft
SOCRadar
Sophos
VIPRE
Webroot
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-09-13 09:47:46 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 94.154.35.225.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
(HK)
