VirusTotal
7 / 92 engine detections
レポートを開く“walletflower · launch on pump.fun without connecting a wallet”
Backpackなりすまし: walletflower.fun — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 7/92 (alphaMountain.ai, CyRadar, DNS8, Forcepoint ThreatSeeker, Fortinet)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 92 engine detections
レポートを開く悪意あり
レポートを開くDBL_PHISH
5 community references
レポートを開く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
walletflower.fun poses as a tool that lets users launch tokens on pump.fun without connecting a wallet, a pitch designed to lower the guard of DeFi users who are wary of wallet-connection risks. The site targets crypto users active on pump.fun, a popular Solana-based token launchpad. PhishDestroy first identified it on 2026-10-17, one day after the domain was registered, and as of 2026-10-18 the site remains fully live and serving active content.
The page title — "walletflower · launch on pump.fun without connecting a wallet" — is the lure: it promises a friction-free token launch that supposedly requires no wallet connection, which is exactly what a cautious user wants to hear. In practice, drainer sites of this type do the opposite: at some point in the flow they prompt the victim to sign a transaction or approve a contract, and that interaction hands the attacker permission to sweep tokens and NFTs from the connected wallet. The victim loses assets directly from their wallet without any further action on their part, and the transfer is irreversible on-chain.
VirusTotal returned 7 detections from 92 engines as of 2026-10-18, with flagging vendors including Kaspersky, Fortinet, Forcepoint ThreatSeeker, OpenPhish, CyRadar, DNS8, and alphaMountain.ai. Spamhaus DBL classifies the domain as DBL_PHISH, an independent confirmation of phishing intent. The domain has also generated 5 OTX threat-intelligence pulses and appears on the PhishDestroy blocklist. Seven detections out of 92 engines is a moderate signal; the Spamhaus and OTX corroboration strengthens the case significantly.
The domain was registered on 2026-10-16 through Cloudflare, Inc. and is hosted on the same company's network, AS13335, on a US-based IP. The TLS certificate is issued by Google Trust Services under the WE1 intermediate, giving the site a padlock that lends it false legitimacy. The one-day gap between registration and first detection is consistent with a purpose-built scam domain.
If you visited the site but did not connect a wallet or sign anything, no immediate action is required beyond avoiding the site. If you connected a wallet, immediately revoke all token approvals granted to any contract associated with this site using a trusted approval-revocation tool, then transfer remaining assets to a fresh wallet address. If you signed a transaction, assume your assets are at risk and act without delay. Security teams and wallet providers should add walletflower.fun to blocklists and alert users who may have interacted with pump.fun-adjacent tooling.
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 の評判はこのドメインに起因しません。
randy.ns.cloudflare.comvivienne.ns.cloudflare.comLocation describes the IP network.
5b266368d5f18c7472a40aed02c0c7ce6d103319a24d1cdfb077f7a20236eac4www.walletflower.funSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.walletflower.funDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of walletflower.fun · checked Oct 17, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://walletflower.fun/Content-Type: text/html; charset=utf-8Cache-Control: no-cacheContent-Encoding: gzipServer: cloudflare4df9b4057332d32747a68167900086971450fae152fbccba75fca59889f010fdsummary_large_imageh2=":443"; ma=60no-cachea4c1057e8bb823fb-FRAkeep-alivegziptext/html; charset=utf-8Sat, 17 Oct 2026 17:28:44 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=0rjBgEIASiPTPOgDff7FkHlK8ZrKKvqg2KjuzSfqKWZoZVJi1%2F1%2Fv9eg2UkDk%2BgYIx26o9CdkaJ2pazUVIJ3ntJxeEXPLT%2FxLK3WweToWsmMVI5b7%2BflDPQU4a3k4%2B2tzu8cloudflarechunkedValues retained by the collector; long values may be shortened during collection.
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.
不明→live_content
content_served
不明→live_content
content_served
6→7
5→6
4→5
不明→live_content
content_served
2→4
到達可能
No threat flag
View source5 community references
View source7/92 engine detections
View sourcePage captured
View sourcewalletflower.fun
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
walletflower.fun
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.
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 ↗
walletflower.fun)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.