VirusTotal
3 / 91 engine detections
レポートを開く“SparkDEX”
WalletConnectフィッシング: sparkdex.exchange — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 3/91 (alphaMountain.ai, Bfore.Ai PreCrime, Gridinsoft); PhishDestroy…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 91 engine detections
レポートを開く23 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
This domain is flagged as a crypto drainer phishing site targeting users of the SparkDEX decentralized exchange platform. Analysis indicates infrastructure designed to siphon cryptocurrency assets through fraudulent transaction prompts, likely leveraging brand impersonation to deceive victims into authorizing malicious smart contract interactions. Infrastructure analysis reveals the following technical indicators: the domain sparkdex.exchange was registered on November 29, 2025, through Dynadot LLC and currently resolves to IP address 188.114.96.3. The site employs an SSL certificate issued by Google Trust Services and utilizes Cloudflare for content delivery, including Cloudflare Browser Insights and HTTP/3 protocol support. Detection metrics show 0/95 detections on VirusTotal, a Gridinsoft trust score of 0/100, and inclusion on one security blocklist, specifically PhishDestroy. The page title explicitly mimics SparkDEX branding. Mitigation against this crypto drainer threat requires immediate action from both users and security teams. Users should revoke any smart contract approvals granted to unknown or suspicious domains via wallet interfaces like Etherscan or blockchain explorers. Security teams should block the domain and IP at network perimeter controls, monitor for outbound connections to 188.114.96.3, and alert users about fraudulent SparkDEX impersonation attempts. Wallet providers should consider adding this domain to transaction warning lists for enhanced user protection.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/SparkDexAIStored page referenceIoC extraction recorded 2026-07-29 02:40:16 UTC
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.comhera.ns.cloudflare.comLocation describes the IP network.
dfb6165d2f1ca4b18d184b7d22811ebaaed2f7f65550166ac4adb9edcb4459d8Saved 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 sparkdex.exchange · checked Jun 27, 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.
alive_content: raw=ok; http=200; via=http_proxy; server=Caddy
sparkdex.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
利用不可→到達可能
到達可能→利用不可
3→Observation retained
https://radar.cloudflare.com/scan/9457a960-06b6-4266-a899-0fce8de561dc
No threat flag
View source23 community references
View source3/91 engine detections
View sourcePage captured
View sourcesparkdex.exchange
View sourceコミュニティの 1 人が報告・初回確認 2025年12月18日
Listed domains receive at least one abuse report; this entry has no retained notification history.
このドメインを操作したり、個人情報を入力したり、暗号通貨ウォレットに接続したりした場合は、直ちに行動を起こしてください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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.
推定では $51 billion 2024年に違法な暗号資産ウォレットへと流出した(source). もしあなたが sparkdex.exchange — 今すぐ行動しましょう。
Wallet-specific steps below apply if you connected a wallet, signed a transaction, or exposed a wallet secret.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
によると、 FBI、最も重要な詳細はトランザクションデータです:
0x5856...35985)sparkdex.exchange)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.