VirusTotal
8 / 89 engine detections
فتح التقرير“Suspected Phishing | Cloudflare”
تصيد: briidge-base.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 8/89 (alphaMountain.ai, ESET, Forcepoint ThreatSeeker…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
8 / 89 engine detections
فتح التقريرThreat flag recorded
فتح التقريرno community references
فتح التقريرprovider verdict: clean
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
briidge-base.pages.dev is an impersonation phishing page. Its name, with a doubled "i" in "bridge", is built to pass for a bridge to the Base network at a glance, so it targets crypto users moving assets between chains. PhishDestroy first saw it on 2026-09-03. The site has been offline since 2026-09-14, and on 2026-10-19 it was still dead, with its content blocked by the hosting provider.
Fake bridge pages copy the look of a real cross-chain tool and ask visitors to connect a wallet and approve a transfer. The prompts that appear are typically token approvals or signatures that hand control of the victim's assets to the operator, or a direct transfer to an address the scammer controls. Bridge users are attractive targets because they expect to sign several transactions and often move large balances at once. The page title now reads "Suspected Phishing | Cloudflare", which is the provider's warning page. That differs from the bridge impersonation we classified.
On 2026-09-16, VirusTotal showed 8 of 89 engines flagging the domain. The vendors were alphaMountain.ai, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing, Sophos and VIPRE. Google Safe Browsing lists it under SOCIAL_ENGINEERING, so Chrome and other browsers that use that feed warn visitors. Beyond PhishDestroy, it appears on the MetaMask and SEAL blocklists, two wallet-focused feeds whose listings point directly at crypto theft.
The page was deployed as a free subdomain on Cloudflare Pages rather than as a registered domain. A setup like that takes minutes and costs nothing, which makes it easy to replace once blocked. It resolved to 172.66.47.71 on Cloudflare, Inc.'s network, geolocated to CA. It stayed online for about eleven days after PhishDestroy first saw it, until the provider pulled its content.
If you connected a wallet to this page, review its token approvals with a revocation tool and cancel any granted to contracts or addresses you do not recognize. If you signed a transfer or approval, move remaining funds to a fresh wallet. If you typed in a seed phrase, treat the wallet as compromised and abandon it. Always reach bridges through bookmarks or the project's official channels, never through search ads or links in direct messages. Defenders should block the domain and watch for similar misspelled "bridge" and "base" subdomains on free hosting platforms.
Last checked
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
Google PageSpeed Insights — mobile performance audit of briidge-base.pages.dev · checked Sep 14, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
4→8
يمكن الوصول إليه→غير متوفر
No flag recorded→Flag recorded
يمكن الوصول إليه
Threat flag recorded
View source8/89 engine detections
View sourcebriidge-base.pages.dev
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
briidge-base.pages.dev
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 ↗
briidge-base.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.