Domain bnkrevent.network was flagged by PhishDestroy as an active credential theft site impersonating financial event portals. This domain, registered on March 21, 2026, is currently unresolved but configured to harvest user credentials under the guise of a banking event platform. The domain resolves to IP 188.114.96.3 and leverages a Let's Encrypt SSL certificate to enhance credibility. No public documentation confirms the deployment of a crypto drainer or specific brand impersonation, but behavioral patterns align with credential phishing campaigns targeting banking and financial services users.
Technical indicators for bnkrevent.network include a VirusTotal detection score of 2/95, indicating no antivirus or security vendor has flagged the domain as malicious at the time of analysis. The domain is registered through PDR Ltd. d/b/a PublicDomainRegistry.com, a registrar frequently abused by low-cost phishing operations. The IP address 188.114.96.3 is part of a range associated with hosting providers that tolerate malicious activity. The domain’s recent creation date—March 21, 2026—suggests a hastily deployed campaign intended to evade historical blocklists. Google Safe Browsing (GSB) status remains pending, and no current blocklist entries are recorded for this domain.
This campaign is assessed as ACTIVE with an under-investigation risk level. PhishDestroy recommends immediate blocking of bnkrevent.network at the network and endpoint levels. Users should be warned against accessing the domain and instructed to report any suspicious login prompts. The risk remains elevated due to the domain’s clean VirusTotal status, lack of GSB flagging, and absence from blocklists, enabling it to bypass automated defenses. Continuous monitoring for new artifacts and campaign expansion is advised.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bnkrevent.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
DOM Analysisanalyzed 2026年7月29日score 71/1001 brand signal
Submitted URLhttp://bnkrevent.network/
ケース ID
ICANN OVERSIGHT
認定と 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 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:08:04 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-05-23 19:14:36 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-23 19:14:36 UTC → 2026-09-30 16:14:55 UTC · 3,117.01hmidpoint estimate ≈ 2026-07-27 17:44:45 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.
使用技術 · 12 identified
A
Apple iCloud Mail
N
Node.js
Programming languages
JavaScript runtime built on Chrome V8 engine for server-side development.
S
Salesforce
Google Sign-in
A
Apple Sign-in
A
Amazon Web Services
PaaSIaaS
Cloud computing platform offering compute, storage, and networking services.
S
Stripe
Payment processor — credit card and alt-payment acceptance.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
