VirusTotal
13 / 92 engine detections
レポートを開く“Flare: The blockchain for data”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.com.
The latest stored availability evidence still shows the domain reachable; 13 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.
Flarenetworkなりすまし: sitemuy0h6n1ra4e.cfd — 未検証. 証拠の概要: VirusTotal 13/92 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); URLQuery 3 det.…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 92 engine detections
レポートを開く3 det.
レポートを開く悪意あり
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
sitemuy0h6n1ra4e.cfd is an impersonation phishing page that copies Flare Network, the data-focused blockchain, and targets FLR holders and people active in the Flare ecosystem. PhishDestroy flagged it on 2026-10-07, the same day the domain was registered. As of 2026-10-19 the domain had stopped resolving in DNS. It is still registered and could be pointed at a server again at any time.
The page presents itself under Flare's own tagline, "Flare: The blockchain for data", so a visitor arriving from a search ad, social post or direct message sees what looks like the official project site. Fake Flare pages of this kind usually push a reward claim, airdrop or account check. The visitor is then asked to connect a wallet and sign a transaction, or to type in a recovery phrase. Either step can give the operators control over the victim's FLR and other tokens, and assets taken this way are generally gone for good.
Within four days of registration, 13 of 92 VirusTotal engines flagged the domain when it was checked on 2026-10-11. The vendors included BitDefender, ESET, Kaspersky, Fortinet, G-Data, Forcepoint ThreatSeeker, CRDF and alphaMountain.ai. urlscan.io returned a malicious verdict and identified Flare Network as the imitated brand. Wallet-focused blocklists also list the domain, including MetaMask, ScamSniffer and SEAL alongside PhishDestroy, so many wallet users will see a warning before the page loads. The domain also appears in four AlienVault OTX threat pulses.
The domain was registered through Spaceship, Inc. on 2026-10-07 and went live as a phishing page right away. The random-looking name on a cheap .cfd extension points to a throwaway domain that was never meant to build trust on its own. The page relies entirely on the copied Flare branding for that. Traffic ran through Cloudflare (AS13335, US address 188.114.97.3), which hides the real origin server. Its free Let's Encrypt certificate gives the browser padlock, which proves nothing about who runs the site.
If you connected a wallet to this page, revoke any token approvals it obtained using a reputable approval checker, and move remaining funds to a new wallet. If you entered a recovery phrase, treat that wallet as compromised and transfer everything to a wallet with a newly generated seed immediately. Only reach Flare through bookmarks you saved yourself, and ignore any "claim" or "verification" links that come through ads or messages. Defenders should block the domain, add the .cfd naming pattern to their monitoring, and watch for it resolving again.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/FlareNetworkStored page referenceIoC extraction recorded 2026-10-08 04:01:10 UTC
Last checked
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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 の評判はこのドメインに起因しません。
donald.ns.cloudflare.comromina.ns.cloudflare.comLocation describes the IP network.
135d786d9e96513353cdaa19008fa906242848b7bac8e1a4166e0e9ff564b916Saved 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
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
到達可能
No threat flag
View source13/92 engine detections
View source4 community references
View sourcePD-20261007-EF0148
sitemuy0h6n1ra4e.cfd
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
sitemuy0h6n1ra4e.cfd
PD-20261007-EF0148 Recipient: abuse@spaceship.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 ↗
sitemuy0h6n1ra4e.cfd)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.