Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
网络安全情报 Registrar context
Registrar contextTrustname
Stored registration data identifies Trustname / Fewmoretaps OÜ (IANA 4318) as the registrar. PhishDestroy maintains a separate registrar investigation; that material is contextual and is not an independent detection for this domain.
libopex.com is on the PhishDestroy blocklist as a suspicious domain tied to crypto fraud risk. It does not yet have a confirmed scheme type or impersonated brand. PhishDestroy first saw it on 2026-10-07, only ten days after it was registered. On 2026-10-19 the site was still alive and its content was reachable, but visitors were being redirected rather than shown a page of their own.
How the scam works
The domain's main behavior is a redirect: anyone who opens libopex.com is passed on to another destination. Short-lived redirect domains like this are commonly used as a disposable front door. A link circulates in ads, messages or social posts, and the domain forwards visitors to the page where the actual fraud happens. That page could be a fake login, a wallet-connection prompt or a bogus investment offer. Because the final destination can be swapped at any time, the risk is whatever sits at the end of the redirect. Typical losses include account credentials, recovery phrases or funds sent under false pretenses.
Evidence
On 2026-10-19, VirusTotal showed 6 of 92 engines flagging the domain. The six were alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That is a minority of engines, but it is an independent signal from vendors with separate detection pipelines, which matters for a domain this young. The domain also appears in 3 AlienVault OTX threat-intelligence pulses, meaning other researchers have linked it to tracked activity. Apart from PhishDestroy, no other blocklists list it.
Infrastructure
The domain was registered on 2026-09-27 through Fewmoretaps OU d/b/a Trustname.com and was flagged within about ten days. That quick turnaround fits throwaway domains spun up for a single campaign. It sits behind Cloudflare (AS13335) on a US-located address. Because of this, the visible IP belongs to Cloudflare's network and does not reveal the server hosting the actual content.
What to do
If you clicked through libopex.com, think about where it sent you and what you did there. If you entered a password, change it on that service and on any account that reuses it, and turn on two-factor authentication. If you typed a wallet recovery phrase anywhere along the way, treat that wallet as compromised and move remaining funds to a newly created wallet. If you sent money, contact your exchange or bank promptly and report the transaction. Defenders should block libopex.com at DNS and proxy level and watch logs for clients that followed the redirect. They should also report the domain to its registrar and to Cloudflare's abuse channel.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-20 10:06:52 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-20 10:06:52 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(BY)
PhishDestroy Investigation
