The domain bitcoinhyper.digital is a brand impersonation threat specifically targeting the Ethereum cryptocurrency ecosystem. The site presents itself as the Bitcoin Hyper Official Website, promoting a fraudulent BTC Hyper Layer 2 Presale, likely designed to deceive users into connecting wallets or sending funds. This infrastructure mimics legitimate presale announcements to harvest credentials or drain cryptocurrency assets.
Technical indicators confirm the malicious nature of this domain. VirusTotal reports a detection rate of 3/95 security vendors flagging this domain. The domain was registered on February 21, 2026, through Web Commerce Communications Limited, and resolves to IP address 104.21.34.93. The domain appears on 3 security blocklists, and Gridinsoft assigns a trust score of 0/100, indicating no legitimate reputation.
Current status shows the domain has been taken offline. Response actions include blocking by MetaMask, SEAL, and PhishDestroy security tools. While offline, the remaining risk involves potential reactivation under a different domain or IP. Users who previously interacted with this site should revoke any wallet permissions and monitor for unauthorized transactions. Entities should add this seed ce1ac3 to blocklists and educate users about verifying presale announcements through official channels only.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 2026年4月23日score 30/1004 brand signals
IoC Extractionscanned 2026年8月2日0 wallet · 1 Telegram IoC
Submitted URLhttps://bitcoinhyper.digital/
ケース 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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:08:06 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-17 22:12:48 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 22:12:48 UTC → 2026-09-30 16:14:55 UTC · 2,514.04hmidpoint estimate ≈ 2026-08-09 07:13:51 UTC · precision very low · basis bounded
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.
Last analyzed Previous stored snapshot: 2 detections
alphaMountain.ai
Fortinet
Gridinsoft
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
2514.04
Estimate basis
Bounded by observations
Estimate precision
very_low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bitcoinhyper.digital', port=80): Max retries exceeded with url: / (Caused by NewConnection
bitcoinhyper.digital
Stored observation history12
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
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.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(MY)
