This domain, bepsend.network, is flagged as a crypto drainer impersonating Trust Wallet, a legitimate cryptocurrency wallet service. The site poses a significant risk to users by mimicking Trust Wallet’s interface, specifically targeting those attempting to send Binance Coin (BNB). The goal is to trick victims into entering sensitive wallet credentials or authorizing malicious transactions, resulting in the unauthorized transfer of cryptocurrency to attacker-controlled addresses. Given the domain’s focus on BNB transactions, users of Binance Smart Chain (BSC) are the primary targets, and financial loss is the likely outcome for those who interact with the site. Analysis indicates that bepsend.network was registered on May 4, 2026, through NameCheap, Inc., a registrar frequently abused for malicious domains due to its accessibility and low cost. The domain resolves to the IP address 216.150.1.1, which has been associated with other phishing campaigns. VirusTotal reports that 2 out of 95 security vendors flag this domain as malicious, a low detection rate that suggests the threat may still be evading some automated defenses. Additionally, the domain appears on one security blocklist and was blocked by PhishDestroy, further confirming its malicious intent. The page title, "Send BNB | Trust Wallet," directly mimics Trust Wallet’s branding to deceive users. If you visited bepsend.network or interacted with its content, immediate action is required to mitigate potential damage. First, disconnect any connected wallets from the site and revoke any suspicious transaction approvals using a blockchain explorer or wallet management tool. Scan your device for malware, as phishing sites may deliver additional payloads. Monitor your wallet for unauthorized transactions and consider transferring remaining funds to a new, secure wallet if compromise is suspected. Report the domain to relevant security teams and blocklists to prevent further victimization. Users should also verify the authenticity of any cryptocurrency-related site by cross-referencing official domains and enabling multi-factor authentication where possible.
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.
RegistrationCreated May 4, 2026 (163d)—Expires May 4, 2027
Time to First Unavailability14 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedMay 30, 2026
DOM Analysisanalyzed May 30, 2026score 71/1001 brand signal
IoC Extractionscanned Aug 1, 20261 wallet · 0 Telegram IoC
Submitted URLhttps://bepsend.network/
Case ID
ICANN OVERSIGHT
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:09:05 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-07-08 16:17:36 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-08 16:17:36 UTC → 2026-09-30 16:14:55 UTC · 2,015.96hmidpoint estimate ≈ 2026-08-19 16:16:15 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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-06-26 01:49:43 UTC
VirusTotal scanner detections updated from 0 to 2. Added scanner alerts: Gridinsoft, SOCRadar.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
bepsend.network detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Jun 13, 2026
Time to First Unavailability
344 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
5 evidence signal groups linked1 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · bepsend.network
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
