VirusTotal
13 / 94
“BECU Online Banking | Secure Credit Union”
13 / 94
6 threat-system alerts
Reportprovider verdict: malicious
Report5/15
checked — no match recorded
no community references
Reportstored report
Report Analysis completed
ReportChecked; no threat flag recorded
Report| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | becucu.credit |
malicious | Sinkholed |
| OpenDNS | becucu.credit |
phishing | Phishing Block |
| Cloudflare DNS | becucu.credit |
malicious | Sinkholed |
| Hagezi Threat Feed | becucu.credit |
malicious | Sinkholed |
| Quad9 DNS | becucu.credit |
malicious | Sinkholed |
| DNS4EU | becucu.credit |
malicious | Sinkholed |
Analysis of becucu.credit shows a recently registered domain (created 07 Mar 2026) that was used to host a fraudulent banking login page, as indicated by the page title “BECU Online Banking | Secure Credit Union”. The site resolved to IP 5.252.116.244, an address owned by AS207569 I‑SERVERS LTD in Russia. The hosting stack included Nginx behind Cloudflare, with front‑end libraries Chart.js, Tailwind CSS, Unpkg, Tippy.js, Lightbox and jsDelivr, all of which are commonly found in compromised or copycat pages. DNS is served by three dnspod.com name servers (a.dnspod.com, b.dnspod.com, c.dnspod.com).
No TLS certificate was presented, and the site was taken offline at the time of reporting, but historical scans show that 13 of 94 VirusTotal security vendors flagged the domain as malicious. Gridinsoft assigned a trust score of 0/100, and the domain appears on a single external blocklist, with PhishDestroy already enforcing a block. The lack of SSL, low trust score, and multiple vendor detections collectively confirm the presence of a banking phishing infrastructure.
Uncertainty remains regarding the current activity of the underlying server, as the site is offline and no live payloads can be observed. Defenders should continue to block becucu.credit at DNS, proxy, and endpoint layers, monitor for any resurgence of the IP address or associated name servers, and update detection rules to include the observed technology fingerprint. Threat intelligence feeds should be updated to reflect the confirmed banking phishing classification, and any inbound traffic from the associated IP range should be treated as high‑risk.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='becucu.credit', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
Google PageSpeed Insights — mobile performance audit of becucu.credit · checked Mar 8, 2026
16 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Reported by 1 community member, first seen Mar 7, 2026
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive