VirusTotal
12 / 92 engine detections
Ouvrir le rapport“Longbow — Credit for every asset onchain”
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.
Usurpation de MetaMask: longbow.cash — Dernier actif connu (HTTP 308). Résumé des preuves: VirusTotal 12/92 (alphaMountain.ai, Bfore.Ai PreCrime, BitDefender…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
12 / 92 engine detections
Ouvrir le rapport3 det.
Ouvrir le rapport3 community references
Ouvrir le rapportprovider verdict: clean
Ouvrir le rapport80/100
Ouvrir le rapportNo threat flag
Ouvrir le rapportNo malicious flag
Ouvrir le rapportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
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.
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.
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.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x026df18fbd2A7639089D0a16293383ec687A5Ca1Format validated · Domain analysis0x12f190a9f9d7d37a250758b26824b97ce941bf54Format validated · Domain analysis0xd0601ce157db5bdc3162bbac2a2c8af5320d9eecFormat validated · Domain analysisIoC extraction recorded 2026-09-28 04:00:12 UTC
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.
La réputation Edge-IP n’est pas attribuée à ce domaine.
ns1.vercel-dns.comns2.vercel-dns.comLocation describes the IP network.
ff8a5333c59282091de5b17e317c2a60be91d8d6f3b247fe5f56198684c6c716Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.longbow.cashDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of longbow.cash · checked Sep 27, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Inconnu→redirected
http_redirect
Accessible
No threat flag
View source12/92 engine detections
View source3 community references
View sourcePD-20260927-ECC3AA
longbow.cash
View sourcePage captured
View source79 domaines ressemblants enregistrés
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
longbow.cash
PD-20260927-ECC3AA Recipient: abuse@name.com 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.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
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 ↗
longbow.cash)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.
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
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
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.