VirusTotal
8 / 92 engine detections
レポートを開く“Stake $BOW | Longbow”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@hostinger.com.
The latest stored availability evidence still shows the domain reachable; 16 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.
フィッシング: longbowcash.site — 未検証. 証拠の概要: VirusTotal 8/92 (Emsisoft, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, Kaspersky); URLScan malicious verdict…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
8 / 92 engine detections
レポートを開くDBL_SPAM
悪意あり
レポートを開くScan report
レポートを開く4 community references
レポートを開くScan report
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
longbowcash.site presents itself as the staking portal for Longbow, with the page title "Stake $BOW | Longbow". It targets holders of the $BOW token and anyone looking for staking yield on it. PhishDestroy first flagged the domain on 2026-10-04. As of 2026-10-19 the domain is still registered, but its DNS no longer serves the page, and it could be pointed back at live content at any time.
Fake staking pages copy the look of a real project's dashboard and offer a "Stake $BOW" button that first asks the visitor to connect a wallet. Instead of staking, the transactions or signatures the page asks for typically hand control of the victim's tokens to the operator. This is often done through unlimited token approvals or direct transfers disguised as deposits. Once signed, those assets can be moved out without any further action from the victim. The staking rewards shown on such pages never exist.
Eight of 92 VirusTotal engines flagged the domain by 2026-10-07: Emsisoft, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, Kaspersky, Netcraft, SOCRadar and Webroot. That is a modest share, but these vendors come from different ecosystems, which makes the verdict hard to dismiss. urlscan.io rated the page malicious and matched it to generic crypto branding. ScamSniffer lists it alongside PhishDestroy, and Spamhaus DBL classifies it as spam. Four AlienVault OTX threat pulses also reference the domain.
The domain was registered on 2026-09-24 through HOSTINGER operations, UAB, ten days before PhishDestroy caught it. That short gap is typical of throwaway domains built for a single campaign. It is hosted on Hostinger International Limited's network (AS47583) in Lithuania. The site uses a free Let's Encrypt certificate, so the padlock in the browser says nothing about whether the site is legitimate.
If you connected a wallet to this site, use a token-approval checker right away to find and revoke any approvals it obtained. If you signed a transaction you did not understand, move your remaining assets to a fresh wallet. Never enter a seed phrase on any staking page, and treat any site that asked for one as a full compromise. Reach Longbow only through links published on the project's official channels. Defenders should block the domain at DNS and proxy level and add it to wallet-protection and email filters while it remains registered.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x026df18fbd2A7639089D0a16293383ec687A5Ca1Format validated · Domain analysis0x23e99d72e24dc538c955b9bade710d2ce3a7fca4Format validated · Domain analysis0x451b42a15100c340ca12f7c66de06fac5ea2d751Format validated · Domain analysis0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168Format validated · Domain analysis0xeba502e1177f5fad9432c2deb273569d8381e01aFormat validated · Domain analysisIoC extraction recorded 2026-10-04 04:00:12 UTC
Last checked
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.
aster.dns-parking.comhelios.dns-parking.comLocation describes the IP network.
2a0140627d1aa6f419adc71f9aa7dfbc10d208d5e48db0b8411eeb91b5df90f5www.longbowcash.siteSaved 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.longbowcash.siteDomain recordThe original observation time is not recorded for these hostnames.
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.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
到達可能
No threat flag
View source8/92 engine detections
View source4 community references
View sourcePD-20261003-1DF020
longbowcash.site
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
longbowcash.site
PD-20261003-1DF020 Recipient: abuse@hostinger.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
longbowcash.site)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.