VirusTotal
7 / 89 engine detections
レポートを開く“Uniswap | Fast Crypto Exchange | Secure & Fast”
Uniswapなりすまし: unlswap.to — 未検証. 証拠の概要: VirusTotal 7/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); Spamhaus DBL_PHISH; 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 89 engine detections
レポートを開くSuspicious
レポートを開くDBL_PHISH
3 community references
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
unlswap.to is a phishing page posing as Uniswap, the decentralized token exchange. Its domain swaps the "i" in "uniswap" for a lowercase "l", a substitution that is easy to miss in a browser bar or search result. It targets Uniswap users and DeFi traders looking for the real swap interface. PhishDestroy first flagged it on 2026-09-14. As of 2026-10-19 the domain was still registered, but its DNS was inactive and it was not serving page content.
The page presented itself as "Uniswap | Fast Crypto Exchange | Secure & Fast", copying the branding a trader expects to see before swapping. Fake Uniswap fronts like this typically ask the visitor to connect a wallet and then request a token approval, a permit signature or a transaction that looks like a routine swap. Once signed, that permission lets the attacker move the victim's tokens without further prompts. Some variants also show a fake "wallet sync" or error screen that asks for the recovery phrase, which gives away the entire wallet.
On 2026-09-24, VirusTotal showed 7 of 89 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar and VIPRE. That detection rate is modest, so many browsers and security tools may not have warned visitors. Crypto-specific defenses did catch it. MetaMask and the SEAL security alliance both list it alongside PhishDestroy, and Spamhaus carries it in its domain blocklist as a phishing domain. Three AlienVault OTX threat pulses also reference it.
The domain was registered on 2026-07-09, about two months before PhishDestroy detected it. That gap is consistent with a domain set up in advance and put into use later. It sits under the .to country-code zone, administered by the Government of the Kingdom of Tonga. The site was hosted on the Global Layer B.V. network at an address geolocated to Brazil. It used a free Let's Encrypt certificate, so the padlock icon said nothing about whether the site was legitimate.
If you connected a wallet to unlswap.to, use a token-approval checker to review and revoke any allowances or permits you granted there, and do it before moving more funds. If you entered a recovery phrase, treat the wallet as compromised and transfer remaining assets to a new wallet with a fresh seed right away. Reach Uniswap only through a saved bookmark and check the spelling of the domain before signing anything. Defenders should block unlswap.to at DNS and proxy level and add the "unlswap" letter-swap pattern to lookalike-domain monitoring.
Last checked
nancy.ns.cloudflare.comLocation describes the IP network.
af8b9005f663c60a37ad4f25ac43a70e8d4cafb9d281d799327c95fcdc09db67Saved 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 unlswap.to · checked Sep 22, 2026
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.
不明→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
不明→dns_inactive
dns_nxdomain
live_content→dns_inactive
dns_nxdomain
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
No threat flag
View source7/89 engine detections
View source3 community references
View sourceunlswap.to
View source保存された類似ドメイン:79 件
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
unlswap.to
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 ↗
unlswap.to)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.