セキュリティレポートへ移動
ドメインのセキュリティと脅威インテリジェンス
longbow.cash favicon

longbow.cash

“Longbow — Credit for every asset onchain”

レジストラ
Name.com
Resolved IP
216.150.1.65
Registered
2026年8月11日
PhishDestroy assessment クリティカル
可用性 最後に確認されたアクティブな状態 最新の保存された到達可能性の観測 観測された · HTTP probe
VirusTotal 検出数: 12/92 自動ブランドラベル:MetaMask
OTX: 3 refs 2026年9月27日 1 Report Sent CDN
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 12。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
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
レポート概要

MetaMaskなりすまし: longbow.cash — 最後に確認されたアクティブな状態 (HTTP 308). 証拠の概要: VirusTotal 12/92 (alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, CRDF, Forcepoint…

元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。

Source evidenceVirusTotal 12 / 92 · OTX 3 references 7 sources

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

Analysis

クリティカル
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

保存済みキャプチャ · 3 captures

Observed page title
Longbow — Credit for every asset onchain
Automated brand references
Across Chainlink Ethereum Morpho Uniswap
TLS証明書
発行者 Let's Encrypt / YR1 · stored validity ends in 19 days

Domain details

ドメイン
URLScan verdict 分析完了 score 0 report ↗
IP Context Vercel shared edge origin IP hidden Edge-IP の評判はこのドメインに起因しません。
OTX tags 2026-09all-domainsblocklistcryptoドメインdrainerfraudlivemonthlyphishdestroyphishingscam
レジストラ Name.com (Unknown)
不正利用連絡先abuse@name.com, abuse@vercel.com
ICANNレジストリICANN Lookup (RDAP) →
登録情報作成日 2026年8月11日 (70d · New) — Expires 2027年8月11日
HTTPステータス308 Permanent Redirect
技術詳細Provenance & timestamps
初確認2026年9月27日
DOM Analysisanalyzed 2026年10月9日score 98/1005 brand signals
IoC Extractionscanned 2026年9月28日3 wallet · 0 Telegram IoCs
Submitted URLhttp://longbow.cash/
Favicon Hash
ケース ID
ICANN OVERSIGHT

認定と 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 自動送信は一切行われません。

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

Edge-IP の評判はこのドメインに起因しません。

ネームサーバー 2

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

Location describes the IP network.

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 不明
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.

使用技術 · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

12 / 92 セキュリティ ベンダーがこのドメインにフラグを立てました
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
カスペルスキー
Lionic
SOCRadar
ソフォス

アーカイブ済み証拠

Wayback Machine Snapshot
過去のスナップショットは証拠のレビューに利用可能です
View Archive
サイトパフォーマンス分析

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

    不明→redirected

    http_redirect

  2. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  3. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  4. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  5. Availability monitor · Recorded state

    不明→redirected

    http_redirect

Earlier observations 14
  1. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  2. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  3. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  4. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  5. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  6. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  7. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  8. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  9. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  10. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  11. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  12. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  13. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  14. Availability monitor · First collection record

    到達可能

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

類似ドメイン

保存された類似ドメイン:79 件

すべて表示(67)
metasmask.io insertion 内部レポート metramask.io insertion 内部レポート mewtamask.io insertion 内部レポート mmetamask.io homoglyph 内部レポート mtamask.io omission 内部レポート mwetamask.io insertion 内部レポート nmetamask.io homoglyph 内部レポート metamark.io bitsquatting 内部レポート metamaskj.io addition 内部レポート metammask.io homoglyph 内部レポート metamnask.io homoglyph 内部レポート 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

証拠および外部報告書

送信済み証拠のスナップショット
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
詳細な分析
Help & reporting

このサイトによって何か影響を受けましたか?

7 evidence signal groups linked 1 stored notification records 最後に確認されたアクティブな状態
If credentials were compromised, report immediately. Do not engage with recovery scammers.

アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。

Official reporting routes

復旧を装った詐欺に注意! 犯罪者は、捜査員、弁護士、または回収業者を装い、被害者に再び連絡を取る可能性があります。 前払い料金を支払ったり、資格情報を共有したりしないでください。 回復詐欺について詳しくはこちら →

お住まいの地域の当局へ報告してください

サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。

97か国のディレクトリ

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

AI 支援ドラフト — インシデントの詳細は AI プロバイダーによって処理されます · 自分で確認して送信する
After a phishing incident

被害者への推奨事項とアドバイス

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.

  • すべてのパスワードを変更する — メール、Exchangeアカウントなど、同じパスワードを使用しているものすべて
  • 2段階認証を有効にする 認証アプリ(SMSではない)を使用する。SMSによる復旧機能を無効にする
  • カードの凍結 フィッシングサイトに銀行口座情報を入力してしまった場合

レポート作成のために、どのような情報を収集すべきでしょうか?

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.
  • 正確な日時 — 各取引および詐欺師との最初の接触について
  • スクリーンショット — 詐欺サイト、チャットメッセージ、メール、ウォレットでの取引、ソーシャルメディア
  • すべてのURLおよびドメイン 詐欺師が使用した(以下を含む) longbow.cash)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。

この詐欺はどこに通報すればいいですか?

  • FBI IC3 — インターネット犯罪通報センター(米国連邦政府の通報窓口)
  • ユーロポール — 欧州におけるサイバー犯罪の報告(EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される

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?

  • 偽のウェブサイト — 正規サイトのドメインをわずかに変更した、ピクセル単位で完璧に再現されたクローンサイト
  • pig butchering — TelegramやWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AIを利用した詐欺 — ディープフェイク、自動化されたフィッシング、AI生成サイトにより、詐欺の発見が難しくなっている

今後、どうすれば身を守ることができるでしょうか?

  • 公式サイトをブックマークする — メール、DM、広告に含まれるリンクは絶対にクリックしないでください
  • ドメインの確認 — 確認する PhishDestroy 操作を行う前に、HTTPS、スペル、ドメインの登録期間を確認してください。
  • 「良すぎて怪しい」=詐欺 — 確実なリターン、有名人の推薦、差し迫った締め切り

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

最新情報を入手し、安全を確保しましょう

リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください

リアルタイム脅威情報フィード この掲載情報について異議を申し立てる
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

このレポートを埋め込む

この脅威情報を、ご自身のウェブサイトやブログで共有してください

embed.html
<iframe
  src="https://phishdestroy.io/ja/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>