Analysis of bep.network indicates a newly registered domain created on 22 March 2026 that is being used for brand impersonation of TrustWallet. The site presented the page title “Send BBN | Trust Wallet”, aligning with the targeted brand. The domain is registered through NameCheap, Inc., and delegated to four Amazon Route 53 nameservers (ns-1323.awsdns-37.org, ns-2022.awsdns-60.co.uk, ns-61.awsdns-07.com, ns-683.awsdns-). DNS resolution points to the IP address 13.35.58.95, which belongs to Amazon.com, Inc. (AS16509) and is geolocated in Germany. The SSL certificate presented is an Amazon‑issued RSA‑2048 M01 certificate, confirming the hosting provider’s involvement but offering no legitimacy to the content.
Reputation signals are uniformly negative. Gridinsoft assigned a trust score of 0 / 100, and the domain appears on a single security blocklist. VirusTotal reports three detections out of ninety‑one scanned vendors, and AlienVault OTX references the domain in one threat‑intelligence pulse. PhishDestroy has also blocked the domain. The site’s current HTTP status is offline, indicating that the malicious content has been taken down or the infrastructure has been abandoned.
For defenders, the evidence suggests that bep.network was actively used to lure victims into sending Binance Coin (BNB) under the guise of a Trust Wallet transaction. Monitoring should include adding the domain and its IP address to blocklists, configuring DNS sink‑hole rules for the associated nameservers, and alerting users of Trust Wallet about the specific “Send BNB | Trust Wallet” page title that may appear in phishing emails. Since the domain is already offline, retrospective log analysis can help identify any compromise attempts that referenced the domain or its IP. Ongoing vigilance is recommended because the same registration and hosting patterns have been reused in other Trust Wallet impersonation campaigns.
Extracted from stored page analysis
Observed indicators
1 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Yang kami hitung
Waktu yang berlalu sejak laporan penyalahgunaan pertama kali disimpan hingga pengamatan pertama bahwa konten tersebut tidak tersedia. Hal ini tidak dapat menentukan penyebabnya.
Isi setiap laporan
Catatan laporan keluar yang disimpan dapat merujuk pada bukti yang tersedia pada saat itu, seperti keputusan vendor, data pendaftaran, detail hosting, klasifikasi, atau tangkapan layar. Halaman ini tidak menyimpulkan secara pasti muatan yang dikirimkan, penerimaan, pengakuan, atau tindakan oleh penerima.
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi24/06/2026
DOM Analysisanalyzed 24/06/2026score 76/1001 brand signal
IoC Extractionscanned 29/07/20261 wallet · 0 Telegram IoC
Submitted URLhttps://bep.network/
ID kasus
ICANN OVERSIGHT
Akreditasi dan konteks RAA
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS tidak aktifreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationTidak diketahuiProbe Inconclusive20%2026-10-19 01:07:58 UTC
RDAP registrationTidak diketahui
Observed timelinelast reachable: 2026-07-08 22:17:00 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-08 22:17:00 UTC → 2026-09-30 16:14:55 UTC · 2,009.97hmidpoint estimate ≈ 2026-08-19 19:15:57 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bep.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
bep.network
Stored observation history10
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Hubungan yang disimpan dikelompokkan berdasarkan atribut pencocokan tepat. Penyedia atau registrar bersama saja tidak membuktikan kepemilikan bersama.
Peta infrastruktur · bep.network
Setiap jalur merupakan salah satu alasan mengapa sebuah domain terhubung ke host ini. Ukuran node menandai deteksi VirusTotal, sedangkan node bergaris putus-putus menunjukkan bahwa node tersebut sudah offline. Daftar lengkapnya tercantum di bawah ini.
Konten cocok4
Hash favicon yang sama atau judul halaman yang sama dengan host ini.
Didaftarkan melalui penyedia layanan pendaftaran yang sama. Sebuah penyedia layanan pendaftaran melayani jutaan pelanggan yang tidak saling terkait, sehingga hal ini sekadar mengelompokkan laporan-laporan tersebut, bukan membuktikan adanya hubungan.
6 evidence signal groups linked1 stored notification recordsKonten tidak tersedia
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Waspadalah terhadap penipu yang mengatasnamakan pemulihan! Penjahat dapat menghubungi korban lagi sambil berpura-pura menjadi penyelidik, pengacara, atau agen pemulihan. Jangan membayar biaya di muka atau membagikan kredensial.Pelajari lebih lanjut tentang penipuan dalam proses pemulihan →
Laporkan kepada Pihak Berwenang di Daerah Anda
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Direktori 97 negara
Template-based draft · optional AI wording assistance requires separate consent
Draf yang dibantu AI — detail insiden diproses oleh penyedia AI · Tinjau dan kirimkan sendiri
After a phishing incident
Rekomendasi & Saran bagi Para Korban
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Apa yang harus saya lakukan segera?
Mendesak
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Ubah semua kata sandi — email, akun Exchange, apa pun yang menggunakan kata sandi yang sama
Aktifkan 2FA menggunakan aplikasi otentikator (bukan SMS). Nonaktifkan pemulihan berbasis SMS
Kartu pembeku jika Anda telah memasukkan detail perbankan di situs phishing tersebut
Informasi apa saja yang sebaiknya saya kumpulkan untuk laporan saya?
Pedoman FBI
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Tanggal dan waktu yang tepat — dari setiap transaksi dan kontak pertama dengan penipu
Tangkapan layar — situs web penipuan, pesan obrolan, email, transaksi dompet digital, media sosial
Semua URL & domain digunakan oleh penipu (termasuk bep.network)
Komunikasi — email, pesan teks, nomor telepon, dan nama pengguna yang digunakan oleh penipu tersebut
Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
Ke mana saya harus melaporkan penipuan ini?
FBI IC3 — Pusat Pengaduan Kejahatan Internet (Laporan tingkat federal AS)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Polisi setempat — membuat catatan resmi, meskipun mereka tidak dapat bertindak segera
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Situs web palsu — salinan yang persis sama dengan situs asli, dengan domain yang sedikit diubah
Pemotongan babi — kepercayaan yang dibangun selama beberapa minggu melalui Telegram/WhatsApp/aplikasi kencan, lalu uangnya dicuri
Penipuan pemulihan — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
Penipuan yang didukung oleh kecerdasan buatan — deepfakes, serangan phishing otomatis, dan situs yang dihasilkan oleh kecerdasan buatan (AI) yang membuat penipuan semakin sulit dideteksi
Bagaimana cara saya melindungi diri di masa depan?
Tandai situs resmi — jangan pernah mengklik tautan dari email, pesan langsung (DM), atau iklan
Memverifikasi domain — periksa PhishDestroy Sebelum berinteraksi. Periksa HTTPS, ejaan, dan usia domain
"Terlalu bagus untuk jadi kenyataan" = penipuan — imbal hasil yang dijamin, dukungan dari selebriti, tenggat waktu yang mendesak
About this reportSources, observation dates and corrections
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.
