VirusTotal
8 / 89 engine detections
فتح التقرير“Coinbase - Tickets”
انتحال Coinbase: 427334-coinbase.com — المحتوى غير متوفر. ملخص الأدلة: VirusTotal 8/89 (ChainPatrol, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
8 / 89 engine detections
فتح التقرير2 threat-system alerts
فتح التقريرThreat flag recorded
فتح التقريرDBL_PHISH
ضار
فتح التقرير4 community references
فتح التقريرprovider verdict: clean
فتح التقرير80/100
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
427334-coinbase.com was a phishing page that impersonated Coinbase behind the page title "Coinbase - Tickets", a fake customer-support ticket desk. It targeted Coinbase customers who were looking for help with their accounts, or who had been told they had an open case. PhishDestroy first flagged it on 2026-09-17. The site has been offline since 2026-09-19, and its DNS was still inactive when last checked on 2026-10-19.
Fake ticket portals depend on urgency. A victim receives a message about a security alert, a frozen balance or a pending case, and a numbered link sends them to a page that looks like Coinbase support. The page then asks them to "verify" their identity by entering their email, password and 2FA codes, and sometimes recovery phrases or ID documents. The numeric prefix in the domain suits this lure because it reads like a case reference. With those details, attackers can take over the account and move the funds out before the victim realises what has happened.
Eight of 89 VirusTotal engines flagged the domain as of 2026-09-17: ChainPatrol, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Google Safe Browsing, Gridinsoft and Kaspersky. That count is modest, but the vendors include both crypto-focused and mainstream security engines. Google Safe Browsing classed it as social engineering. urlscan.io returned a malicious verdict and detected Coinbase branding. Spamhaus lists it in its DBL as phishing, it appears on the MetaMask, SEAL and PhishDestroy blocklists, and four AlienVault OTX pulses reference it.
The domain was registered through OwnRegistrar, Inc. on 2026-09-16 and was being flagged a day later. It went dark within three days of registration, which fits a disposable domain built for a short campaign. Traffic ran through Cloudflare, with the resolving address geolocated to Canada. Because Cloudflare's network sits in front of the site, the real origin server stays hidden.
If you typed your Coinbase credentials into this page, change your password immediately and reset 2FA, preferably to a hardware key or an authenticator app. Then review your active sessions, API keys and withdrawal addresses, and remove anything you do not recognise. If you shared a recovery phrase, treat that wallet as compromised and move the funds to a new one. Remember that Coinbase support will never ask for passwords, 2FA codes or seed phrases. Defenders should block the domain and look for lookalike domains that combine numbers with brand names in mail and DNS logs.
Last checked
لا تُنسب سمعة Edge-IP إلى هذا المجال.
clark.ns.cloudflare.commolly.ns.cloudflare.comLocation 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.
Google PageSpeed Insights — mobile performance audit of 427334-coinbase.com · checked Sep 17, 2026
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.
427334-coinbase.com
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
غير معروف→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
يمكن الوصول إليه→غير متوفر
No flag recorded→Flag recorded
يمكن الوصول إليه
Threat flag recorded
View source4 community references
View source8/89 engine detections
View sourcePD-20260917-772F3F
427334-coinbase.com
View sourcePage captured
View source٢٥٥ نطاقًا متشابهًا محفوظًا
عرض 100 من 255
PD-20260917-772F3F Recipient: abuse@ownregistrar.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 ↗
427334-coinbase.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.