VirusTotal
6 / 92 engine detections
Відкрити звітфішинг: libopex.com — Останній відомий активний (HTTP 301). Зведення доказів: VirusTotal 6/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
6 / 92 engine detections
Відкрити звіт3 community references
Відкрити звітprovider verdict: clean
Відкрити звіт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
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.
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.
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.
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.
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.
Репутація Edge-IP не пов’язана з цим доменом.
marek.ns.cloudflare.comLocation describes the IP network.
4405becab851b9f25e2a39b641e43c7328bd9c20941f77d48eb9d5658d2d7f82Saved 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.
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
2→3
Невідомо→redirected
http_redirect
No threat flag
View source6/92 engine detections
View source3 community references
View sourcelibopex.com
View source1 повідомлення спільноти
КатегоріяPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as other. Threat detected at 2026-10-19T18:08:52.149Z.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
libopex.com
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 ↗
libopex.com)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.