VirusTotal
6 / 89 engine detections
فتح التقرير“Desktop Browser Required”
تصيد: shuck-niche.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 6/89 (alphaMountain.ai, Emsisoft, Fortinet, URLQuery…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
6 / 89 engine detections
فتح التقريرضار
فتح التقريرno community references
فتح التقرير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
shuck-niche.pages.dev is an impersonation phishing page on Cloudflare's free Pages platform. It posed as a legitimate service to win visitors' trust and collect what they typed in. PhishDestroy first saw it on 2026-09-11. It has been offline since 2026-09-19, and the content is now blocked by the hosting provider, a state confirmed again on 2026-10-19.
Impersonation pages copy the look and wording of a trusted service, then ask the visitor to sign in, verify an account or confirm details. Anything entered goes to the operator, who can then take over the account or reuse the data in follow-up fraud. Here, the page title read "Desktop Browser Required", which shows a device-requirement notice rather than a branded login screen, while our analysis classified the site as impersonation phishing.
Six of 89 VirusTotal engines flagged the address when it was checked on 2026-09-20: alphaMountain.ai, Emsisoft, Fortinet, URLQuery, VIPRE and Webroot. That is a modest count, but these vendors run separate detection pipelines and reached the same verdict independently. PhishDestroy lists the domain on its own blocklist, which is the source of this classification.
The pages.dev subdomain was created on 2026-09-08, and PhishDestroy detected it three days later. That short gap fits the typical pattern for throwaway phishing sites, which go live quickly and are used before reputation systems catch up. The site was served through Cloudflare's network from an address located in Canada. Its certificate came from Google Trust Services, so it showed a valid padlock, which proves nothing about whether a site is legitimate.
If you entered a password on this page, change it right away on the real service and on any other account that uses the same password. Turn on two-factor authentication and sign out of all active sessions. Then review recent account activity for logins or changes you don't recognize. If you shared personal or payment details, watch for targeted phishing follow-ups and contact your bank if card data was involved. Defenders should block the subdomain, search mail and proxy logs for visits on or after 2026-09-08, and treat other freshly created pages.dev links in unsolicited messages with extra suspicion.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
3dd0e2a47ccc9af03c1d31aa1e1f1cc35edbb7ea06c2c72fd374a8cabf06c404Saved 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
shuck-niche.pages.dev
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
1→6
يمكن الوصول إليه→غير متوفر
يمكن الوصول إليه
No threat flag
View source6/89 engine detections
View sourceshuck-niche.pages.dev
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 ↗
shuck-niche.pages.dev)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.