URLScan
Шкідливий
Відкрити звіт“Cross-chain token swap and bridge — compare routes”
криптофішинг: jumper.ceo — Неперевірений. Зведення доказів: VirusTotal 0/92; URLScan malicious verdict; 3 external blocklist matches (MetaMask, ScamSniffer…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
Шкідливий
Відкрити звіт0 / 92 engine detections
Відкрити звіт2 community references
Відкрити звітprovider verdict: clean
Відкрити звітNo threat flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
jumper.ceo is an impersonation phishing page that borrows the Jumper name and presents itself as a cross-chain token swap and bridge aggregator. It targets DeFi users who move assets between chains and are used to connecting a wallet to compare routes. PhishDestroy first saw it on 2026-10-13. As of 2026-10-19 the domain no longer resolves in DNS, but the name can be pointed at a server again at any time.
The page title, "Cross-chain token swap and bridge — compare routes," copies the pitch of a legitimate bridge aggregator, so a visitor expects to connect a wallet and sign transactions. Fake bridges exploit that expectation. The "swap" or "bridge" prompt is actually a token approval, a permit signature or a direct transfer that gives the operator control over the victim's assets. Once signed, tokens can be drained from the wallet with no further action from the victim, and on-chain transfers cannot be reversed.
VirusTotal returned 0 detections from 92 engines on 2026-10-13, so a clean result there does not mean the site is safe. Crypto-focused sources caught it instead. urlscan.io rated the page malicious and flagged generic crypto branding. The domain is listed by MetaMask, ScamSniffer and SEAL as well as PhishDestroy, which means wallet users with these protections get warned before connecting. It also appears in two AlienVault OTX threat pulses.
The domain was registered through Spaceship, Inc. on 2026-10-03, ten days before PhishDestroy detected it. That short gap is typical of throwaway phishing domains. The .ceo extension stands in for the real project's domain. The site was hosted on VPSPay Networks LTD, a UK-registered network, on a server located in Germany. The DNS record has since gone inactive.
If you connected a wallet to jumper.ceo or signed anything there, use a token-approval tool right away to revoke any approvals or permits you granted. Then move the remaining funds to a fresh wallet. If you entered a seed phrase, treat that wallet as fully compromised and abandon it. Reach Jumper only through a bookmarked official address, never through search ads or links in direct messages. Defenders should block the domain at DNS and proxy level and add it to wallet-protection allowlist checks. They should also watch for the same naming pattern on other new top-level domains.
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.
Location describes the IP network.
Saved 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.
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
2 community references
View sourceNo threat flag
View source0/92 engine detections
View sourcejumper.ceo
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
jumper.ceo
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 ↗
jumper.ceo)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.