VirusTotal
10 / 91 engine detections
فتح التقرير“Suspected Phishing | Cloudflare”
تصيد WalletConnect: official-brevis.network — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 10/91 (alphaMountain.ai, Bfore.Ai PreCrime…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
10 / 91 engine detections
فتح التقرير3/14
1 community reference
فتح التقرير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
Analysis indicates that official-brevis.network operates as an active brand impersonation infrastructure targeting WalletConnect. The domain presents a high risk due to its explicit mimicry of the brand, enabling potential credential harvesting or malware distribution through deceptive interfaces. Infrastructure analysis reveals Cloudflare hosting combined with HTTP/3 support, which facilitates rapid content delivery while obscuring origin details.
Detection relies on precise metrics from multiple sources. VirusTotal reports 11 out of 95 security vendors flagging the domain. Registration occurred on January 03, 2026 via OwnRegistrar, Inc., with an SSL certificate issued by Google Trust Services. Additional indicators include resolution to IP 172.67.157.136, listing in one AlienVault OTX pulse, and presence on three security blocklists.
If interaction with official-brevis.network has taken place, affected systems require immediate isolation followed by comprehensive malware scanning. All associated authentication tokens and private keys must be regenerated through verified channels. Ongoing monitoring for unauthorized transactions is essential, and similar domains should be reported to threat intelligence platforms to refine blocklist coverage.
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 إلى هذا المجال.
byron.ns.cloudflare.comnoor.ns.cloudflare.comLocation describes the IP network.
eee9e40100b45b2d9ae106a3828519a4bf137b000116c0548ea3a43d1f97b24fSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of official-brevis.network · checked Jun 27, 2026
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
official-brevis.network
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
غير متوفر→يمكن الوصول إليه
6→11
https://radar.cloudflare.com/scan/6b96ec6e-7356-4ea3-b8e4-da0dd1a4721a
https://radar.cloudflare.com/scan/4f4e61b5-903a-4941-86ac-a117d9586c56
يمكن الوصول إليه→غير متوفر
10/91 engine detections
View sourceNo threat flag
View source1 community references
View sourcePage captured
View sourceofficial-brevis.network
View sourceأبلغ عنه عضو واحد في المجتمع؛ شوهد أول مرة في 03/01/2026
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.
يُقدَّر أن $51 billion تدفقت إلى محافظ عملات مشفرة غير مشروعة في عام 2024 (source). إذا كنت قد تفاعلت مع official-brevis.network — تصرف الآن.
Wallet-specific steps below apply if you connected a wallet, signed a transaction, or exposed a wallet secret.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
وفقًا لـ مكتب التحقيقات الفيدرالي (FBI)، وأهم التفاصيل هي بيانات المعاملات:
0x5856...35985)official-brevis.network)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.