VirusTotal
3 / 90 engine detections
レポートを開くBitcoinなりすまし: bitcoin-hyper.space — コンテンツが利用できません. 証拠の概要: VirusTotal 3/90 (Forcepoint ThreatSeeker, Kaspersky, VIPRE); 2 external blocklist matches (MetaMask…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 90 engine detections
レポートを開くchecked — no detections recorded
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開く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
bitcoin-hyper.space was a phishing site that borrowed the Bitcoin name to look like a legitimate crypto opportunity and targeted people holding or buying cryptocurrency. PhishDestroy first flagged it on 2026-09-05, four days after the domain was registered. The site went offline on 2026-09-11, and as of 2026-10-19 its DNS no longer resolves.
Bitcoin impersonation sites like this one use the brand's credibility to make an offer feel official. Common offers include a token launch, an upgrade, or an exclusive purchase. The visitor is then pushed either to send coins to an address the operators control or to connect a wallet and approve transactions. Either way, the loss is direct and usually irreversible: transferred crypto cannot be recalled, and a signed approval can let the attacker move tokens out of the wallet. The listing on MetaMask's blocklist points to the wallet-connection risk in particular.
On 2026-09-06, three of 90 VirusTotal engines (Forcepoint ThreatSeeker, Kaspersky and VIPRE) flagged the domain. That is a modest count, so most security products would not have stopped a visitor in the site's first days. The stronger signal comes from crypto-focused blocklists. PhishDestroy, MetaMask and SEAL all list it, and four AlienVault OTX threat pulses reference it.
The domain was registered on 2026-09-01 through HOSTINGER operations, UAB and was already being detected within days. That short window fits a throwaway domain built for a brief campaign. It sat behind Cloudflare, Inc. (IP 172.67.144.31, geolocated to Canada), which hides the actual origin server. Its active life lasted roughly ten days between registration and going dark.
If you sent cryptocurrency through this site, record the transaction hashes and the receiving address, and report them to your exchange and local authorities. Do not pay anyone who offers to recover the funds for a fee. If you connected a wallet or signed anything, review and revoke token approvals with a trusted allowance checker. If you suspect the wallet itself is compromised, move the remaining assets to a fresh wallet. Never enter a seed phrase on any website. Defenders should keep the domain blocked and watch for lookalike Bitcoin-themed domains registered through similar quick-turnaround setups.
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.
Edge-IP の評判はこのドメインに起因しません。
jack.ns.cloudflare.comliberty.ns.cloudflare.comLocation describes the IP network.
Saved 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.
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
到達可能→利用不可
到達可能
No threat flag
View source4 community references
View source3/90 engine detections
View sourcePD-20260905-EB565D
bitcoin-hyper.space
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
bitcoin-hyper.space
PD-20260905-EB565D 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 ↗
bitcoin-hyper.space)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.