VirusTotal
9 / 92 engine detections
Відкрити звіт“Pendle - Liberating Yield”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.com.
The latest stored availability evidence still shows the domain reachable; 10 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
підробка під Coingecko: sitemv1bkdqohtfr.cfd — Неперевірений. Зведення доказів: VirusTotal 9/92 (alphaMountain.ai, Emsisoft, Forcepoint ThreatSeeker…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
9 / 92 engine detections
Відкрити звіт2 det.
Відкрити звітШкідливий
Відкрити звіт4 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
sitemv1bkdqohtfr.cfd is an impersonation phishing page that copies Pendle and uses the protocol's own title, "Pendle - Liberating Yield". It targets DeFi users looking to trade or manage yield positions, who may not notice that the random-string .cfd address has nothing to do with the real project. PhishDestroy first flagged it on 2026-10-10. When last checked on 2026-10-19, the site was still responding, but DNS for its content was inactive.
Fake DeFi front-ends like this one copy the look of the real Pendle app and ask the visitor to connect a wallet. The visitor is then asked to approve a token allowance or sign a message presented as a routine step, such as opening a position, claiming yield or verifying the wallet. That approval or signature lets the attacker move the victim's tokens, including the yield-bearing assets and stablecoins Pendle users typically hold. Losses are usually immediate and cannot be reversed on-chain.
Nine of 92 VirusTotal engines flag the domain as of 2026-10-14. They include Netcraft, Fortinet, Forcepoint ThreatSeeker, Emsisoft, alphaMountain.ai, Gridinsoft, LevelBlue and SOCRadar. That count is moderate, but the more telling signal comes from the crypto-specific blocklists. Besides PhishDestroy, the domain is blocked by MetaMask, ScamSniffer and SEAL, the lists wallet users are most likely to be protected by. It also appears in four AlienVault OTX threat pulses, so other researchers have tracked it independently.
The domain was registered through Spaceship, Inc. on 2026-10-09, and PhishDestroy detected it one day later. A meaningless name on a cheap TLD that goes live almost immediately is typical of disposable phishing domains meant to be used for a short time and then replaced. The site sits behind Cloudflare (AS13335, IP 188.114.96.3, US), which hides the server that actually hosts the page.
If you connected a wallet to this site, use a token-approval tool to revoke any allowances it obtained. If you signed anything there, move your remaining assets to a fresh wallet, because some signatures stay valid after the page disappears. Never enter a seed phrase on any Pendle-branded page. If you already have, treat that wallet as compromised and stop using it. Reach Pendle only through a bookmarked official address. Security teams should block this domain and add related .cfd lookalikes using the Pendle title to their watchlists.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/pendle_info_botStored page referenceIoC extraction recorded 2026-10-11 04:01:29 UTC
Last checked
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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 не пов’язана з цим доменом.
destiny.ns.cloudflare.comjake.ns.cloudflare.comLocation describes the IP network.
12432ca45dc161b2ff6e906de81af7ea3900216cc27d55732e909f3a11e37481Saved 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 sitemv1bkdqohtfr.cfd · checked Oct 10, 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
live_content→dns_inactive
dns_nxdomain
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Доступний
No threat flag
View source9/92 engine detections
View source4 community references
View sourcePD-20261010-26760D
sitemv1bkdqohtfr.cfd
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
sitemv1bkdqohtfr.cfd
PD-20261010-26760D Recipient: abuse@spaceship.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 ↗
sitemv1bkdqohtfr.cfd)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.