VirusTotal
6 / 91 engine detections
فتح التقرير“huddleoo.cc is registered at Namecheap”
انتحال ["namecheap"]: huddleoo.cc — آخر نشاط معروف (HTTP 302). ملخص الأدلة: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
6 / 91 engine detections
فتح التقريرDBL_PHISH
4 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
huddleoo.cc is an impersonation phishing domain that uses Namecheap branding. Its listing on MetaMask's and SEAL's blocklists shows that crypto wallet users are among its targets. PhishDestroy first flagged it on 2026-09-15. As of 2026-10-19 the domain was still live and answering with a redirect, so visitors can still be sent onward.
The page carries the title "huddleoo.cc is registered at Namecheap", which mimics the registrar's own branded page so the domain looks routine and harmless. We classify the domain as impersonation phishing, even though that title resembles an ordinary parked-domain notice. Schemes like this use a familiar brand to lower suspicion, then redirect visitors to a page that asks for account logins, seed phrases or wallet signatures. Victims can lose control of their accounts or the funds in a connected wallet.
Six of 91 VirusTotal engines flag the domain as of 2026-09-29: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That number is modest, but the domain is also listed by MetaMask and SEAL, both of which focus on crypto threats, and Spamhaus has added it to its DBL under the phishing category. Four AlienVault OTX threat pulses reference it as well. Together these show that several independent teams have identified the domain as phishing.
The domain was registered on 2026-07-12 through NameCheap, Inc., about two months before PhishDestroy flagged it. It resolves to 162.255.119.118 on Namecheap's network in the US, so registration and hosting sit with the same company whose name appears in the page title. A domain that has been live for weeks before detection has had time to circulate in messages and ads.
Do not follow links to huddleoo.cc or wherever it redirects. If you entered a Namecheap or exchange login there, change that password right away, turn on app-based 2FA, and check your account for unfamiliar sessions, contact changes or domain transfers. If you connected a wallet or signed anything after landing on it, revoke the token approvals you granted. If you typed in a seed phrase, move your funds to a new wallet immediately. Defenders should block the domain and its IP at DNS and proxy level and add it to mail and chat filters.
Last checked
dns1.registrar-servers.comdns2.registrar-servers.comeforward1.registrar-servers.compriority 10eforward3.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location 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.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
huddleoo.cc
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
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
3→5
يمكن الوصول إليه
4 community references
View source6/91 engine detections
View sourceNo threat flag
View sourcehuddleoo.cc
View sourcePage captured
View sourceListed 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 ↗
huddleoo.cc)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.