VirusTotal
2 / 91 engine detections
فتح التقرير“Google”
انتحال Gmail: gigaverse.events — آخر نشاط معروف (HTTP 301). ملخص الأدلة: VirusTotal 2/91 (Chong Lua Dao, Gridinsoft); PhishDestroy score 81/100. مسجّل النطاق…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
2 / 91 engine detections
فتح التقرير23 community references
فتح التقريرprovider verdict: clean
فتح التقريرNo threat flag
فتح التقريرPage capture
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain gigaverse.events was a phishing site engaged in brand impersonation, specifically targeting Google. It posed an elevated risk by mimicking Google's login or service pages to harvest user credentials, a common tactic in credential phishing scams. No crypto drainer kit was associated with this domain. As of the latest verification, gigaverse.events has been taken offline.
Technical indicators for gigaverse.events include 2 of 95 VirusTotal security vendors flagging the domain, including Gridinsoft and SOCRadar. The domain was registered through Cloudflare, Inc., and resolved to the IP address 142.251.40.164, hosted on Google LLC's infrastructure (AS15169) in the US. The SSL certificate was issued by Google Trust Services / WE1, and the observed page title was 'Google'. The domain appeared on 1 security blocklist, specifically PhishDestroy, and used Cloudflare nameservers (brenna.ns.cloudflare.com and hassan.ns.cloudflare.com). Technologies detected included Cloudflare and HTTP/3.
Users who may have interacted with gigaverse.events should immediately change any passwords entered on the site, particularly for Google accounts. Enable two-factor authentication (2FA) on all critical accounts to prevent unauthorized access. Monitor accounts for suspicious activity, such as unauthorized logins or transactions. Report the phishing domain to Google's Safe Browsing team via their reporting tool and to the Anti-Phishing Working Group (APWG) at reportphishing@apwg.org. Additionally, victims can file a complaint with the FBI's Internet Crime Complaint Center (IC3) at ic3.gov.
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 إلى هذا المجال.
brenna.ns.cloudflare.comhassan.ns.cloudflare.comLocation describes the IP network.
1a944c9f88b055c59dad2c7dadd1313d3139825c2111862d71ed8d6e180e9588Saved 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.
redirect: raw=redirect_301; http=301; via=http_proxy; location=https://gigaverse.events/; server=cloudflare
gigaverse.events
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
غير معروف→redirected
http_redirect
غير متوفر→يمكن الوصول إليه
يمكن الوصول إليه→غير متوفر
غير متوفر→يمكن الوصول إليه
يمكن الوصول إليه→غير متوفر
غير متوفر→يمكن الوصول إليه
https://radar.cloudflare.com/scan/e3e80172-3d33-4411-a919-403ddad9601f
يمكن الوصول إليه→غير متوفر
يمكن الوصول إليه→غير متوفر
No threat flag
View source23 community references
View source2/91 engine detections
View sourcePage captured
View sourcegigaverse.events
View sourceأبلغ عنه عضو واحد في المجتمع؛ شوهد أول مرة في 29/11/2025
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 ↗
gigaverse.events)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.