VirusTotal
7 / 89 engine detections
فتح التقرير“Suspected Phishing | Cloudflare”
انتحال Across Protocol: access-brdge.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 7/89 (BitDefender, ESET, Fortinet…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
7 / 89 engine detections
فتح التقريرno community references
فتح التقريرprovider verdict: clean
فتح التقريرNo threat flag
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
access-brdge.pages.dev is an impersonation phishing page hosted as a free Cloudflare Pages project. Its name, with "bridge" misspelled as "brdge", is built to pass a quick glance from users expecting a legitimate access or bridge service. PhishDestroy first flagged it on 2026-08-09. The site has been offline since 2026-09-13 and was still down at the last check on 2026-10-19.
Impersonation pages like this copy the look of a service the victim already trusts, then ask for whatever unlocks their assets. That can be a login, a wallet connection, a signature or a recovery phrase, and once it is handed over the attacker can empty the account. The page title now reads "Suspected Phishing | Cloudflare". That is Cloudflare's own warning interstitial, not the content we classified as impersonation. Anyone who reached it after the block saw a warning rather than the lure.
Seven of 89 VirusTotal engines flag the site as of 2026-09-13: BitDefender, ESET, Fortinet, G-Data, LevelBlue, SafeToOpen and Sophos. The count is modest, but it comes from several independent vendors with their own detection pipelines. The strongest signal is Cloudflare itself replacing the page with a phishing warning. Among blocklists, it currently appears on PhishDestroy's.
The Pages project dates to 2025-10-09, about ten months before PhishDestroy caught it. A long gap like that suggests the address was either kept idle or ran unnoticed for a while. It sits on Cloudflare's network, resolving to an address geolocated in Canada, behind a standard Google Trust Services certificate. The padlock in the browser therefore said nothing about the page's legitimacy. Free pages.dev subdomains cost nothing to create, so similar copies can reappear under new names.
If you entered a password on this site, change it wherever you reuse it and turn on app-based two-factor authentication. If it asked you to connect a wallet or sign anything, revoke the token approvals granted around that time with a reputable approval checker. If you typed a seed phrase, treat that wallet as compromised and move the funds to a new one created from scratch. Defenders should block the hostname and watch for lookalike pages.dev names built around "bridge" or "access" misspellings. Report any new copies to Cloudflare for takedown.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
828f41bac08c6ed858011686dd3ed359ca7869d390b8a075d4d9dab8b3b31f82Saved 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.
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
يمكن الوصول إليه→غير متوفر
No threat flag
View source7/89 engine detections
View sourceaccess-brdge.pages.dev
View sourceبلاغ مجتمعي واحد
الفئةIMPERSONATION
Brand abuse: impersonation, fake affiliation, seo poisoning, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
access-brdge.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 ↗
access-brdge.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.