bep[.]network
“Send BNB | Trust Wallet”
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.
Threat Response Pipeline
Public Blocklist Status
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
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.
VirusTotal Analysis
Evidence & External Reports
PD-20260624-A89244 Recipient: abuse@namecheap.com Were You Affected by This Site?
If a wallet, seed phrase, or account was exposed, report the incident immediately. Revoke approvals and move remaining assets to a new wallet created on a trusted device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive
Recommendations & Advice for Victims
An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with bep.network — act now.
What should I do immediately?
Urgent
- Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
- Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
- Change all passwords — email, exchange accounts, anything that shares the same password
- Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
- Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
According to the FBI, the most important details are transaction data:
- Cryptocurrency addresses — scammer's wallet (e.g.,
0x5856...35985) - Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
- Transaction ID (hash) — the unique blockchain transaction identifier
- Exact dates & times — of each transaction and first contact with scammer
- Screenshots — scam website, chat messages, emails, wallet transactions, social media
- All URLs & domains used by the scammer (including
bep.network) - Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
- FBI IC3 — Internet Crime Complaint Center (US federal reporting)
- Europol — European cybercrime reporting (EU)
- Chainabuse — flag scam wallets across exchanges & platforms
- Your crypto exchange — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
- Local police — creates an official record, even if they can't act immediately
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 crypto scams typically work?
- Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
- Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
- Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
- Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
- Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
- AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
- Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
- Bookmark official sites — never click links from emails, DMs, or ads
- Read every approval — verify permissions before signing. Reject unlimited approvals
- Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
- "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines