VirusTotal
13 / 95 engine detections
Abrir relatório“Coinbase Deposit • Bank Transfer”
Imitação de Coinbase: basepay.services — Conteúdo indisponível. Resumo das evidências: VirusTotal 13/95 (ChainPatrol, alphaMountain.ai, BitDefender, CRDF…
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
13 / 95 engine detections
Abrir relatórioThreat flag recorded
Abrir relatóriono community references
Abrir relatórioprovider verdict: clean
Abrir relatórioPage capture
Abrir relatórioResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis indicates that the domain basepay.services was registered on December 4 2025 through the HOSTINGER operations, UAB registrar. The authoritative name servers are ns1.dns-parking.com and ns2.dns-parking.com, both typical of parked or parking‑service providers. DNS resolution returns a single IPv6 address 2a02:4780:45:4282:ffbc:43a5:3cb8:fd68, which belongs to AS47583 Hostinger International Limited and geolocates to Germany. No TLS certificate is presented, meaning the site would be served over plain HTTP or an invalid HTTPS connection, a common characteristic of fraudulent landing pages. The page title retrieved from the site reads “Coinbase Deposit • Bank Transfer”, directly referencing the Coinbase brand and suggesting a crypto‑related deposit flow.
Google Safe Browsing has classified the domain as a social engineering threat, and PhishDestroy has added it to its blocklist. Additional reputation services report a Gridinsoft trust score of zero out of one hundred and the domain appears on a single security blocklist. VirusTotal analysis shows that thirteen of ninety‑five scanned scanners flagged the domain, reinforcing the malicious assessment. The observed indicators collectively point to a high‑risk crypto scam that impersonates Coinbase to lure victims into a fraudulent deposit process. The site is currently offline, which may be the result of takedown actions or the operator’s own shutdown.
Uncertainty remains regarding the exact payload delivered, the presence of any credential‑stealing forms, or whether the domain was used in a broader campaign. Defenders should continue to block the domain at perimeter filters, monitor for any residual traffic to the associated IPv6 address, and update detection rules to include the observed page title and host‑header patterns.
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.
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.
ns1.dns-parking.comns2.dns-parking.comLocation describes the IP network.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='basepay.services', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
basepay.services
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/ae552a04-7cab-40ea-932f-537b7e68ecec
Page captured
View sourceThreat flag recorded
View source13/95 engine detections
View sourcebasepay.services
View source255 domínios semelhantes armazenados
Exibindo 100 de 255
Denunciado por 1 membro da comunidade; visto pela primeira vez em 05/12/2025
Listed domains receive at least one abuse report; this entry has no retained notification history.
Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.
Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
basepay.services)Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública
Digitalize agoraEnvie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade
DenunciarRelatórios recentes de phishing e alterações de disponibilidade observadas
MonitorarMonitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo
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.