VirusTotal
10 / 92 engine detections
レポートを開く“Firelight – The Protection Layer for Digital Assets”
暗号資産投資詐欺: treasurypool-firelight.foundation — コンテンツが利用できません. 証拠の概要: VirusTotal 10/92 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); URLScan…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
10 / 92 engine detections
レポートを開くSuspicious
レポートを開く悪意あり
レポートを開くchecked — no detections recorded
レポートを開くchecked — no match recorded
no community references
レポートを開く14 確認済み — ブロックなし
No threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain, treasurypool-firelight.foundation, operates as a brand impersonation scheme designed to deceive users of the legitimate hardware wallet service. The site mimics the appearance and functionality of the authentic platform, presenting itself as 'Firelight – The Protection Layer for Digital Assets.' Its primary objective is to harvest sensitive credentials, such as recovery seeds or private keys, under the guise of enhanced security features. Users who interact with this domain risk unauthorized access to their digital assets, financial theft, or complete account compromise. The threat is particularly insidious due to its polished presentation and targeted exploitation of trust in established security brands. Analysis indicates this domain is a confirmed malicious entity with substantial evidence supporting its fraudulent nature. It was registered on May 12, 2026, through PDR Ltd. d/b/a PublicDomainRegistry.com, a registrar frequently associated with high-risk domains. Infrastructure analysis reveals the site resolves to the IP address 172.67.161.90, which is hosted behind Cloudflare, a common tactic to obscure origin servers and evade detection. Security vendors have flagged this domain extensively, with 10 out of 95 engines on VirusTotal identifying it as malicious. Additionally, it appears on four security blocklists and is actively blocked by multiple browser-based protection tools, further confirming its classification as a high-risk impersonation threat. Users who have visited treasurypool-firelight.foundation or interacted with its content should take immediate action to mitigate potential damage. First, cease all interaction with the domain and avoid entering any credentials or sensitive information. If login details or recovery phrases were submitted, assume they are compromised and initiate a full security review of all associated accounts. This includes revoking access to any connected wallets or applications, generating new recovery seeds, and monitoring for unauthorized transactions. It is also recommended to scan local devices for malware, as phishing sites often deploy additional payloads. Finally, report the domain to relevant security communities and the impersonated brand to aid in broader threat mitigation efforts.
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 の評判はこのドメインに起因しません。
connie.ns.cloudflare.comlogan.ns.cloudflare.comLocation describes the IP network.
c09291494f8a4a86d48c45df4e5d49d40f4e8b2b8e78773c9dd67288fb9eda22Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of treasurypool-firelight.foundation · checked Jun 26, 2026
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='treasurypool-firelight.foundation', port=80): Max retries exceeded with url: / (Caused by
treasurypool-firelight.foundation
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
1→10
No threat flag
View source10/92 engine detections
View sourcetreasurypool-firelight.foundation
View sourcePD-20260512-370F41
保存された類似ドメイン:74 件
コミュニティの 1 人が報告・初回確認 2026年5月12日
PD-20260512-370F41 Recipient: abuse@publicdomainregistry.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 ↗
treasurypool-firelight.foundation)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.