VirusTotal
11 / 92 engine detections
レポートを開く“Buy & Sell Bitcoin, Ethereum | Cryptocurrency Exchange | YukiTale”
Bybitなりすまし: bybitdex.network — 未検証. 証拠の概要: VirusTotal 11/92 (alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker); CF Radar malicious…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 92 engine detections
レポートを開く悪意あり
レポートを開く23 community references
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
bybitdex.network is currently active and classified as a high‑risk brand‑impersonation site targeting the cryptocurrency exchange Bybit. The page title observed for the domain reads “Buy & Sell Bitcoin, Ethereum | Cryptocurrency Exchange | YukiTale,” which does not directly reference Bybit but indicates a cryptocurrency‑focused offering. The site is listed on a single security blocklist and has been blocked by PhishDestroy, confirming that it is being actively monitored by defensive feeds. Technical investigation shows that the domain is hosted behind Cloudflare’s network. It resolves to the IP address 104.21.68.87, which belongs to AS13335, Cloudflare, Inc., and is geo‑located in the United States. The authoritative nameservers are ashton.ns.cloudflare.com and tina.ns.cloudflare.com, and the domain registration is also performed through Cloudflare, Inc. The TLS certificate is issued by Google Trust Services under the WE1 intermediate, indicating a valid‑looking HTTPS connection. The service uses Cloudflare’s HTTP/3 protocol, and the HTTP response code is 200. VirusTotal has flagged the domain on 13 of 95 scanning engines, and Gridinsoft assigns a trust score of 0 out of 100, reinforcing the malicious assessment. Defenders should treat any traffic to bybitdex.network as malicious and block it at network perimeters. Correlation with the observed page title and the Bybit brand target suggests that credential‑theft or fund‑exfiltration attempts may be attempted against Bybit users. Organizations employing web filtering or DNS sink‑hole solutions should add the domain to block lists, and incident response teams should monitor for related indicators such as the IP address 104.21.68.87 and the associated Cloudflare nameservers. Continuous monitoring of threat feeds for new detections is advised, given the active status of the infrastructure.
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.
Edge-IP の評判はこのドメインに起因しません。
ashton.ns.cloudflare.comtina.ns.cloudflare.comLocation describes the IP network.
14af5520e9163ff2ce63e99acc4bd8aba1964b99a976b760773820751c53b012Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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='bybitdex.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
bybitdex.network
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
不明→redirected
http_redirect
利用不可→到達可能
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
到達可能→利用不可
利用不可→到達可能
https://radar.cloudflare.com/scan/ff6ce08d-bfff-48f0-8837-7599fda8c0c9
到達可能→利用不可
No threat flag
View source23 community references
View source11/92 engine detections
View sourcePage captured
View sourcebybitdex.network
View source保存された類似ドメイン:112 件
112 件中 100 件を表示
コミュニティの 1 人が報告・初回確認 2025年10月3日
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
bybitdex.network)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.