VirusTotal
19 / 91 engine detections
レポートを開く“Flare: The blockchain for data”
認証情報フィッシング: phase2-flare.foundation — コンテンツが利用できません. 証拠の概要: VirusTotal 19/91 (ADMINUSLabs, ChainPatrol, alphaMountain.ai, BitDefender, Cluster25); URLScan…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
19 / 91 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
PhishDestroy identifies phase2-flare.foundation as a recently activated crypto drainer posing as Flare Network infrastructure. This domain is engineered to trick users into connecting wallets under the guise of 'Phase 2' incentives or airdrops, where approved transactions can silently drain tokens or NFTs without additional confirmations. The threat actor leverages urgency and technical branding to bypass user skepticism, capitalizing on the credibility of the Flare ecosystem. This domain was flagged for crypto drainer activity and placed on 2 security blocklists. It resolves to IP 104.21.35.164 and uses a Let’s Encrypt SSL certificate (issued May 10, 2026). The domain is registered via PDR Ltd. d/b/a PublicDomainRegistry.com and currently shows 0 detections on VirusTotal out of 95 engines. Notably, it is already blocked by MetaMask and the SEAL security system, indicating proactive detection by browser-based crypto defenses. If you visited phase2-flare.foundation, disconnect your wallet immediately and revoke any unauthorized smart contract approvals using tools like Etherscan’s Approval Checker or Revoke.cash. Do not interact with any prompts or wallet connection requests from this domain. Monitor your wallet transactions and report suspicious activity to your wallet provider or security team.
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-08-01 04:11:41 UTC
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 の評判はこのドメインに起因しません。
chan.ns.cloudflare.comcharles.ns.cloudflare.comLocation describes the IP network.
8b91e3ef7f3fd95f2c6c2941b1689a0b069942c37078c1b12ed91d7f46e82246Saved 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='phase2-flare.foundation', port=80): Max retries exceeded with url: / (Caused by NewConnect
phase2-flare.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
到達可能→利用不可
19/91 engine detections
View sourceNo threat flag
View sourcephase2-flare.foundation
View sourcePD-20260511-A25B62
コミュニティの 1 人が報告・初回確認 2026年5月11日
PD-20260511-A25B62 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 ↗
phase2-flare.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.