Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
db.ashoo.ventures favicon

db.ashoo.ventures

“Ashoo - официальный сайт и актуальный доступ к платформе”

Bureau d’enregistrement
NameCheap
Resolved IP
188.114.96.3
Registered
16/11/2025
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 6/89 Type d'arnaque : Impersonation
31/08/2026 CDN
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 6. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Résumé du rapport

Hameçonnage: db.ashoo.ventures — Dernier actif connu (HTTP 301). Résumé des preuves: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker…

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Source evidenceVirusTotal 6 / 89 5 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critique
VirusTotal
6 / 89
Page captures
2

PhishDestroy threat report

Overview

db.ashoo.ventures is an impersonation phishing page that presents itself as the official home of Ashoo. Its Russian-language title translates to "Ashoo - official site and current access to the platform," so it is aimed at Russian-speaking users looking for a working way into that service. PhishDestroy first flagged it on 2026-08-31. As of 2026-10-19 the site is still online and redirects visitors onward.

How the scam works

The page bets on one habit: people who can't reach a service search for an "official" or "current access" link and trust whatever ranks or gets shared. Once a visitor lands on the lookalike, they are steered into signing in, registering or funding an account on infrastructure the real Ashoo does not control. Anything typed there, including logins, passwords, one-time codes, personal details or deposits, goes to the operators. The redirect keeps the page useful to them, because they can send visitors to whatever destination currently serves the scheme.

Evidence

On 2026-09-11, 6 of 89 VirusTotal engines classed the domain as malicious: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That count is modest, but these are six independent vendors, including web-filtering and threat-intel feeds, reaching the same verdict. PhishDestroy lists the domain on its blocklist. A low score mostly means many products will not yet block it, so users cannot count on a browser warning.

Infrastructure

The parent domain ashoo.ventures was registered through NameCheap, Inc. on 2025-11-16, about nine and a half months before PhishDestroy detected it. That long gap suggests the domain was held or used quietly before this page surfaced. Using a subdomain like "db." also lets operators rotate pages under one registration. Traffic goes through Cloudflare, Inc., with the address geolocated to Canada, so the real origin server is hidden behind the proxy.

What to do

If you signed in on this page, change your Ashoo password right away, along with any other account that uses the same one. Turn on or reset two-factor authentication and end any active sessions you don't recognize. If you sent money or made a deposit there, contact your bank or payment provider immediately. Do not pay any "verification" or "unlock" fee these sites may later ask for. Reach Ashoo only through an address you have confirmed independently, not through search results or shared "mirror" links. Defenders should block the domain and the wider ashoo.ventures zone, and alert Russian-speaking user groups to lookalike "official access" pages.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Capture enregistrée · 2 captures

Observed page title
Ashoo - официальный сайт и актуальный доступ к платформе
Certificat TLS
Émis par Google Trust Services · stored validity ends in 47 days

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La réputation Edge-IP n’est pas attribuée à ce domaine.
Registrar (base domain) NameCheap US(US)
Contact anti-abus["abuse@namecheap.com"]
Registre de l'ICANNICANN Lookup (RDAP) →
Registration (base domain)ashoo.ventures · Créé 16/11/2025 (338d) — Expires 16/11/2028
Statut HTTP301 Moved Permanently
Détails techniquesProvenance & timestamps
Première détection31/08/2026
DOM Analysisanalyzed 09/10/2026score 78/100
Submitted URLhttp://db.ashoo.ventures/
Favicon Hash
ICANN OVERSIGHT Registration: ashoo.ventures

Contexte de l’accréditation et du RAA

Registrar accreditation and DNS abuse obligations

For the registrable domain ashoo.ventures behind this subdomain, 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.

Accountability draft Rien n’est envoyé automatiquement.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

La réputation Edge-IP n’est pas attribuée à ce domaine.

Serveurs de noms 1

  • donovan.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
Google Trust Services
Valid from
2026-09-19 04:14:50
Valid until
2026-12-18 05:13:16
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:16 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte8294123db3d8b472ec95b9b1d549d894707e98bc56a0ffe23a1de8554288d94

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 22:28:45 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-19 22:28:45 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-19 22:35:31 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.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

6 / Les fournisseurs de sécurité 89 ont signalé ce domaine
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
VIPRE
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of db.ashoo.ventures · checked Aug 31, 2026

83
Needs Work
Performance
FCP
3.37s
First Contentful Paint
LCP
3.37s
Largest Contentful Paint
CLS
0.049
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.25s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

db.ashoo.ventures
Résultat enregistré
Keitaro TDS
Stored observation history19

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

Earlier observations 14
  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  11. VirusTotal · Detection count

    4→5

  12. VirusTotal · Detection count

    3→4

  13. VirusTotal · Detection count

    0→3

  14. Availability monitor · First collection record

    Accessible

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    6/89 engine detections

    View source
  3. Added to PhishDestroy

    db.ashoo.ventures

    View source
  4. URLScan

    Page captured

    View source

Données factuelles et rapports externes

Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

3 evidence signal groups linked 0 stored notification records Dernier actif connu

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Official reporting routes

Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

Template-based draft · optional AI wording assistance requires separate consent

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
After a phishing incident

Recommandations et conseils à l'intention des victimes

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Que dois-je faire tout de suite ?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment db.ashoo.ventures)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html
<iframe
  src="https://phishdestroy.io/fr/embed/domain/db.ashoo.ventures"
  title="PhishDestroy threat report for db.ashoo.ventures"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>