VirusTotal
13 / 89
“Veminex: Elon Musk’s Official Crypto Casino Powered by Blockchain”
veminex.com — Последний известный активный (HTTP 200). Сводка доказательств: VirusTotal 13/89 (alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet); URLScan malicious verdict; Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. Регистратор: Fewmoretaps OU d/b/a T….
Подробный анализ PhishDestroy AI ниже оставлен на английском, чтобы сохранить исходную криминалистическую запись.
Stored evidence for veminex.com: VirusTotal recorded 3 detections among 90 scanners on 2026-09-06. 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 veminex.com. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 3 detections among 90 scanners in the stored snapshot dated 2026-09-06. 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-06 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.
MetaMask and SEAL are recorded as named external blocklist observations for veminex.com in the snapshot dated 2026-09-06. 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 veminex.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.
The record first observed veminex.com on 2026-09-05. The MetaMask and SEAL blocklist snapshot is dated 2026-09-06 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-05-10. A URLScan reference was stored on 2026-09-05 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.
The source stores 188.114.97.3 as the observed address in this record. The registration date for veminex.com is recorded as 2026-05-10. The SSL issuer is recorded as Let's Encrypt / YE2 in the snapshot dated 2026-09-05. The stored ASN observation records 13335 and Cloudflare, Inc. in this record. The observed server header is recorded as cloudflare 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.
The veminex.com record states that VirusTotal recorded 3 detections among 90 scanners on 2026-09-06. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-06. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 188.114.97.3. The supported conclusion is bounded to the exact stored observations for veminex.com. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to veminex.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain veminex.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 veminex.com. The stored record does not justify extending that rule to 188.114.97.3 or to other infrastructure records.
Сохраненные данные сравнения данных сканера и браузера для данного хоста, а также проверка отпечатков в режиме реального времени для систем распределения трафика типа «Кейтаро».
cloudflareПримечание к сканированию: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
Репутация Edge-IP не связана с этим доменом.
jamie.ns.cloudflare.comlynn.ns.cloudflare.comLocation describes the IP network.
d484407496fd4c6faba361730024948e86d72dd360e82925dbfcd36a1695d5f0Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
188.114.97.3. 13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Если вы ввели учетные данные, личную или платежную информацию или загрузили файл с этого домена, примите немедленные меры. Ниже приведены ресурсы, которые помогут вам сообщить об инциденте и защитить себя.
Выберите свою страну, чтобы получить официальные контакты по киберпреступности или создать проект жалобы →.
Template-based draft · optional AI wording assistance requires separate consent
Анализ угроз с использованием сохраненного черного списка, WHOIS, DNS и общедоступных доказательств сканирования.
Сканировать сейчасДобавляйте подозрительные домены в нашу базу данных угроз — защищайте сообщество
СообщитьНедавние сообщения о фишинге и наблюдаемые изменения доступности
ОтслеживатьОтслеживайте актуальные угрозы или оспорьте эту запись, если считаете, что это ложное срабатывание