VirusTotal
6 / 89 engine detections
レポートを開くフィッシング: furiesmellow0x69.live — コンテンツが利用できません. 証拠の概要: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); URLQuery 1…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 89 engine detections
レポートを開く1 threat-system alert
レポートを開くDBL_SPAM
4 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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | furiesmellow0x69.live |
malicious | Sinkholed |
PhishDestroy threat report
furiesmellow0x69.live is an impersonation phishing site that posed as a legitimate service to win the trust of crypto users. Its name pairs a random word combination with the "0x" hex prefix familiar from blockchain addresses. PhishDestroy first flagged it on 2026-09-14, one day after registration. The site went offline on 2026-09-18 and its DNS was still inactive at the last check on 2026-10-19.
Impersonation pages copy the look, wording and flow of a service the victim already uses. Their goal is to get the visitor to type in account credentials, a recovery phrase or other secrets, or to approve an action they would refuse on an unfamiliar site. Anything entered goes straight to the operators, who can then take over accounts or empty wallets. The page title showed only a generic "Just a moment..." browser-check screen rather than branded content, while our classification is based on impersonation phishing.
Six of 89 VirusTotal engines flagged the domain on 2026-09-17: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That is a modest share, but these are independent vendors, which matters for a site only a few days old. Spamhaus lists the domain on its DBL as spam, and it appears in four AlienVault OTX threat pulses. PhishDestroy also carries it on its own blocklist.
The domain was registered through OwnRegistrar, Inc. on 2026-09-13 and was serving phishing content within a day. This throwaway pattern is typical of campaigns that burn a domain quickly and move on. Traffic ran through Cloudflare's network, with the address geolocated to Canada, so the origin server stayed hidden behind the proxy. The site was dark within five days of first detection.
If you entered a password on this site, change it at once on the real service and anywhere you reused it. Then turn on or reset two-factor authentication and review recent logins. If you typed a seed or recovery phrase, treat that wallet as compromised and move the funds to a new wallet created from a fresh phrase. Security teams should block the domain, search DNS and proxy logs for hits between 2026-09-13 and 2026-09-18, and contact any users who reached it.
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 の評判はこのドメインに起因しません。
isaac.ns.cloudflare.commeadow.ns.cloudflare.comLocation describes the IP network.
bd6849fa7c4cd98e5460427535e21ea74e1aba6e28131c3c0a7fb0f1628e02d9Saved 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 furiesmellow0x69.live · checked Sep 14, 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.
furiesmellow0x69.live
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
到達可能→利用不可
到達可能
4 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcePD-20260914-7AE38D
furiesmellow0x69.live
View sourcePage captured
View sourcePD-20260914-7AE38D Recipient: abuse@ownregistrar.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 ↗
furiesmellow0x69.live)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.