VirusTotal
3 / 91 engine detections
レポートを開く“Send BNB | Trust Wallet”
Trust Walletなりすまし: bep.network — コンテンツが利用できません. 証拠の概要: VirusTotal 3/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft); PhishDestroy score 76/100.…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 91 engine detections
レポートを開くchecked — no detections recorded
レポートを開く1 community reference
レポートを開く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
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.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0xccD642c9acb072F72F29b77E422f5c024ecF5cBaFormat validated · Domain analysisIoC extraction recorded 2026-07-29 02:51:46 UTC
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.
ns-1323.awsdns-37.orgns-2022.awsdns-60.co.ukns-61.awsdns-07.comns-683.awsdns-21.netLocation describes the IP network.
3e6b5e556a2ad812ea41a395a3e511d64ae25d2b6b213ba3b243d3f935be426aSaved 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.
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
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Page captured
View source3/91 engine detections
View source1 community references
View sourceNo threat flag
View sourcePD-20260624-A89244
bep.network
View source保存された類似ドメイン:104 件
104 件中 100 件を表示
PD-20260624-A89244 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
bep.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.