Ir al informe de seguridad
Seguridad de dominio e inteligencia sobre amenazas
longbow.cash favicon

longbow.cash

“Longbow — Credit for every asset onchain”

Registrador
Name.com
Resolved IP
216.150.1.65
Registered
11/08/2026
PhishDestroy assessment Crítico
Disponibilidad Último activo conocido Última observación de accesibilidad almacenada Observado · HTTP probe
VirusTotal detecciones: 12/92 Etiqueta automática de marca: MetaMask
OTX: 3 refs 27/09/2026 1 Report Sent CDN
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 12. Tenga extrema precaución: no ingrese credenciales o información personal.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@name.com. The latest stored availability evidence still shows the domain reachable; 23 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
23 days
Reports sent
1
Latest case ID
PD-20260927-ECC3AA
Current status
HTTP 308 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Resumen del informe

Suplantación de MetaMask: longbow.cash — Último activo conocido (HTTP 308). Resumen de las pruebas: VirusTotal 12/92 (alphaMountain.ai, Bfore.Ai PreCrime…

El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.

Source evidenceVirusTotal 12 / 92 · OTX 3 references 7 sources

VirusTotal

12 / 92 engine detections

Abrir informe

Google Safe Browsing

No threat flag

Abrir informe

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

Analysis

Crítico
VirusTotal
12 / 92
OTX
3 community refs
Page captures
3

PhishDestroy threat report

Overview

longbow.cash is an impersonation phishing page that presents itself as Longbow under the title "Longbow — Credit for every asset onchain". It is aimed at DeFi users looking to borrow against crypto holdings, the audience most likely to connect a wallet without a second thought. PhishDestroy first flagged the domain on 2026-09-27. As of 2026-10-19 the site was still alive and its content reachable through a redirect.

How the scam works

Fake lending and credit front-ends copy the branding and pitch of a real protocol, then invite the visitor to connect a wallet to deposit collateral or open a credit line. The transaction or signature requested does not open any loan. It typically hands the operator token approvals or transfer permissions, which lets them pull assets out of the wallet. Because "credit for every asset" implies the protocol needs access to many tokens, broad approval requests look normal here, which is exactly what makes the lure effective.

Evidence

On 2026-10-07, 12 of 92 VirusTotal engines classified the domain as malicious. The engines that flagged it include alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. Those engines draw on separate data sources and detection methods, which makes the verdict hard to dismiss as a single false positive. The domain also appears in 3 AlienVault OTX threat pulses. Among blocklists, only PhishDestroy currently lists it, so many browsers and wallets may not warn visitors yet.

Infrastructure

The domain was registered through Name.com, Inc. on 2026-08-11, about seven weeks before PhishDestroy detected it. That gap left time to build the clone before it began circulating. The site runs on Amazon.com, Inc. infrastructure in the US at 216.150.1.65. It carries a Let's Encrypt certificate, so the browser padlock only shows the connection is encrypted and says nothing about whether the site is the real Longbow.

What to do

If you connected a wallet to longbow.cash, open a token-approval manager right away and revoke every allowance granted to unfamiliar contracts. If you signed anything you did not fully understand, move the remaining funds to a fresh wallet. Never type a seed phrase into any site, and treat a request for one as proof of fraud. Reach Longbow only through links published on its official channels. Security teams should block the domain at DNS and proxy level, add it to wallet and browser warning lists, and report it to the registrar and hosting provider.

Extracted from stored page analysis

Observed indicators

3 wallet · 0 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

ETH
0x026df18fbd2A7639089D0a16293383ec687A5Ca1Format validated · Domain analysis
ETH
0x12f190a9f9d7d37a250758b26824b97ce941bf54Format validated · Domain analysis
ETH
0xd0601ce157db5bdc3162bbac2a2c8af5320d9eecFormat validated · Domain analysis

IoC extraction recorded 2026-09-28 04:00:12 UTC

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura guardada · 3 captures

Observed page title
Longbow — Credit for every asset onchain
Automated brand references
Across Chainlink Ethereum Morpho Uniswap
Certificado TLS
Emitido por Let's Encrypt / YR1 · stored validity ends in 19 days

Domain details

Dominio
URLScan verdict Análisis finalizado score 0 report ↗
IP Context Vercel shared edge origin IP hidden La reputación de Edge-IP no se atribuye a este dominio.
OTX tags 2026-09all-domainsblocklistcryptodominiosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador Name.com (Unknown)
Contacto de abusoabuse@name.com, abuse@vercel.com
Registro de la ICANNICANN Lookup (RDAP) →
RegistroCreado 11/08/2026 (70d · New) — Expires 11/08/2027
Estado HTTP308 Permanent Redirect
Detalles técnicosProvenance & timestamps
Primera detección27/09/2026
DOM Analysisanalyzed 09/10/2026score 98/1005 brand signals
IoC Extractionscanned 28/09/20263 wallet · 0 Telegram IoCs
Submitted URLhttp://longbow.cash/
Favicon Hash
ID del caso
ICANN OVERSIGHT

Acreditación y contexto RAA

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.

Accountability draft No se envía nada automáticamente.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
216.150.1.65
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel

La reputación de Edge-IP no se atribuye a este dominio.

Servidores de nombres 2

  • ns1.vercel-dns.com
  • ns2.vercel-dns.com

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YR1
Valid from
2026-08-11 04:05:23
Valid until
2026-11-09 04:05:22
Validity
Within stored validity dates
Collection time
2026-10-11 07:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintff8a5333c59282091de5b17e317c2a60be91d8d6f3b247fe5f56198684c6c716

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:30:55 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:30:55 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-10-19 22:35:34 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.longbow.cashDomain record

The original observation time is not recorded for these hostnames.

Tecnologías · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este dominio Envía pruebas y ayuda a proteger a los demás

Análisis de VirusTotal

12 / Los proveedores de seguridad de 92 marcaron este dominio
View on VT
Last analyzed First positive detection Previous stored snapshot: 8 detections
alphaMountain.ai
Bfore.Ai PreCrime
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos

Evidencias archivadas

Wayback Machine Snapshot
Una instantánea histórica está disponible para revisión de evidencia.
View Archive
Análisis del rendimiento del sitio

Google PageSpeed Insights — mobile performance audit of longbow.cash · checked Sep 27, 2026

71
Needs Work
Performance
FCP
4.55s
First Contentful Paint
LCP
4.8s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
47ms
Total Blocking Time
SI
4.55s
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.

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

    Desconocido→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

Earlier observations 14
  1. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  11. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  12. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  13. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  14. Availability monitor · First collection record

    Accesible

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    12/92 engine detections

    View source
  3. AlienVault OTX

    3 community references

    View source
  4. Abuse report sent

    PD-20260927-ECC3AA

    abuse@name.com
  5. Added to PhishDestroy

    longbow.cash

    View source
  6. URLScan

    Page captured

    View source

Dominios similares

79 dominios similares almacenados

Mostrar todo (67)
metasmask.io insertion Informe interno metramask.io insertion Informe interno mewtamask.io insertion Informe interno mmetamask.io homoglyph Informe interno mtamask.io omission Informe interno mwetamask.io insertion Informe interno nmetamask.io homoglyph Informe interno metamark.io bitsquatting Informe interno metamaskj.io addition Informe interno metammask.io homoglyph Informe interno metamnask.io homoglyph Informe interno emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Check for cloaking

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

longbow.cash

Datos y informes externos

Instantánea de evidencia enviada
Sent: Ledger records: 1 Case ID: PD-20260927-ECC3AA Recipient: abuse@name.com
Page title stored with report: Longbow — Credit for every asset onchain
PDF notice generated
Análisis en profundidad
Help & reporting

¿Te ha afectado esta página web?

7 evidence signal groups linked 1 stored notification records Último activo conocido
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.

Official reporting routes

¡Cuidado con los estafadores que se hacen pasar por empresas de recuperación de datos! Los delincuentes pueden volver a contactar a las víctimas haciéndose pasar por investigadores, abogados o agentes de recuperación. No pague tarifas por adelantado ni comparta credenciales. Más información sobre el fraude en las ayudas de recuperación →

Informa a las autoridades locales

Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.

directorio de 97 países

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

Borrador asistido por IA: el proveedor de IA procesa los detalles del incidente · Revíselo y envíelo usted mismo
After a phishing incident

Recomendaciones y consejos para las víctimas

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

¿Qué debo hacer ahora mismo?

Urgente

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

  • Cambiar todas las contraseñas — correo electrónico, cuentas de Exchange, cualquier cosa que utilice la misma contraseña
  • Activar la autenticación de dos factores utilizando una aplicación de autenticación (no SMS). Desactivar la recuperación mediante SMS
  • Tarjetas de congelación si has introducido tus datos bancarios en la página de phishing

¿Qué información debo recopilar para mi informe?

Directrices del 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.
  • Fechas y horas exactas — de cada transacción y del primer contacto con el estafador
  • Capturas de pantalla — páginas web fraudulentas, mensajes de chat, correos electrónicos, transacciones con monederos electrónicos, redes sociales
  • Todas las URL y dominios utilizados por el estafador (incluidos longbow.cash)
  • Comunicaciones — correos electrónicos, mensajes de texto, números de teléfono y nombres de usuario que utilizó el estafador

Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.

¿Dónde debo denunciar la estafa?

  • IC3 del FBI — Centro de Denuncias de Delitos en Internet (sistema federal de denuncia de EE. UU.)
  • Europol — Informes sobre la ciberdelincuencia en Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Policía local — deja constancia oficial, aunque no puedan actuar de inmediato

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?

  • Páginas web falsas — Clones idénticos al milímetro de sitios web legítimos, con dominios ligeramente modificados
  • Sacrificio de cerdos — Se ganaba la confianza de las víctimas a lo largo de varias semanas a través de Telegram, WhatsApp o aplicaciones de citas, y luego les robaban el dinero.
  • Estafas relacionadas con la recuperación — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Estafas basadas en la inteligencia artificial — los «deepfakes», el phishing automatizado y los sitios web generados por IA, que hacen que el fraude sea más difícil de detectar

¿Cómo puedo protegerme en el futuro?

  • Añadir a favoritos las páginas web oficiales — Nunca hagas clic en enlaces de correos electrónicos, mensajes directos o anuncios
  • Verificar dominios — comprobar si PhishDestroy antes de interactuar. Comprueba que sea HTTPS, la ortografía y la antigüedad del dominio
  • «Demasiado bueno para ser verdad» = estafa — rendimientos garantizados, recomendaciones de famosos, plazos urgentes

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

Mantente informado, mantente a salvo

Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.

Flujo de amenazas en tiempo real Reclamar este anuncio
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

Incrustar este informe

Comparte esta información sobre amenazas en tu página web o blog

embed.html
<iframe
  src="https://phishdestroy.io/es/embed/domain/longbow.cash"
  title="PhishDestroy threat report for longbow.cash"
  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>