VirusTotal
15 / 89 engine detections
فتح التقرير“Home - fawypea.pro”
تصيد: fawypea.pro — آخر نشاط معروف (HTTP 301). ملخص الأدلة: VirusTotal 15/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Forcepoint ThreatSeeker); CF…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
15 / 89 engine detections
فتح التقريرضار
فتح التقرير4 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
fawypea.pro is an impersonation phishing site aimed at crypto users who believe they are dealing with a legitimate service. PhishDestroy first flagged it on 2026-09-10. As of 2026-10-19 the domain was still alive and serving a redirect, so visitors are being forwarded on rather than shown a dead page. Its page title, "Home - fawypea.pro", is a generic homepage label and does not name the brand being copied.
Impersonation pages borrow the look, wording and flow of a known platform so the visitor drops their guard. The victim is then pushed to log in, verify an account, or claim a reward or refund. Anything typed in, such as passwords, one-time codes, recovery phrases or identity documents, goes straight to the operators. They use it to take over accounts or empty balances. The active redirect means the domain may act as a doorway that passes traffic to the actual capture page.
On 2026-09-18, 15 of 89 VirusTotal engines classified the site as malicious. That is a meaningful share for a domain this young. The flagging vendors include alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. These are independent engines that reached the same verdict separately. The domain also appears in 4 AlienVault OTX threat pulses, so other researchers have tracked it as well. It sits on the PhishDestroy blocklist.
The domain was registered through NameCheap, Inc. on 2026-03-03, about six months before it surfaced as a phishing site. That gap fits domains that are registered early and kept in reserve until a campaign needs them. Traffic runs through Cloudflare's network in the US, which hides the server actually hosting the content. The Let's Encrypt certificate is free and issued automatically, so the browser padlock proves nothing about who runs the site.
If you entered a password on fawypea.pro, change it right away on the real service and on any account that shares it, then turn on app-based 2FA. Review your active sessions and sign out any device you do not recognise. If you typed a recovery phrase, treat that wallet as compromised and move your funds to a newly created wallet. Never pay any "verification" or "unlock" fee the site or its contacts ask for. Defenders should block the domain at DNS and proxy level and search logs for users who were redirected through it.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
henrik.ns.cloudflare.comLocation describes the IP network.
25c0c18cea2f089c41edc750c61d02760b8fb53012e2c2b823c1ee2dcc3a6597Saved 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.
fawypea.pro
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
4 community references
View sourceNo threat flag
View source15/89 engine detections
View sourcePage captured
View sourcefawypea.pro
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 ↗
fawypea.pro)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.