VirusTotal
12 / 91 engine detections
Bericht öffnen“Liberty Crest Bank, N.A. - Dedicated to innovating, simplifying, and humanizing digital banking.”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@whiteprivacy.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Phishing: glochase.elafure.com — Letzter bekanntermaßen aktiv (HTTP 200). Zusammenfassung der Beweislage: VirusTotal 12/91 (alphaMountain.ai, BitDefender…
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
12 / 91 engine detections
Bericht öffnen1 threat-system alert
Bericht öffnenDBL_PHISH
Schädlich
Bericht öffnenno community references
Bericht öffnenprovider verdict: clean
Bericht öffnen80/100
Bericht öffnenNo threat flag
Bericht öffnenResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | glochase.elafure.com |
malicious | Sinkholed |
PhishDestroy threat report
glochase.elafure.com is an impersonation phishing page dressed up as Liberty Crest Bank, N.A. It uses the bank's own marketing line in its title: "Dedicated to innovating, simplifying, and humanizing digital banking." It targets people who bank online and expect a familiar sign-in screen. PhishDestroy first flagged it on 2026-09-18. As of 2026-10-19 the site was still alive and its content was reachable through a redirect.
Victims usually reach a page like this through an email or text warning about a locked account, a suspicious payment or a required verification. The link lands on a copy of the bank's login portal. Anything typed there goes straight to the operators: username, password, one-time codes and often card or identity details. With those, criminals can log into the real account, approve transfers or reuse the password on other services before the victim notices.
Twelve of 91 VirusTotal engines flagged the domain as of 2026-09-29. The flagging vendors include alphaMountain.ai, BitDefender, CRDF, CSIS Security Group, ESET, Forcepoint ThreatSeeker, Fortinet and G-Data. urlscan.io returned a malicious verdict and matched the page to a generic banking brand template, which fits a fake bank login. Spamhaus lists the domain in its DBL as phishing, and it is on the PhishDestroy blocklist. Several independent vendors reached the same verdict, so this is not a single isolated report.
The parent domain elafure.com was registered on 2025-12-13 through TuringSign Inc. d/b/a Cosmotown, roughly nine months before PhishDestroy detected the phishing subdomain. Registering a neutral-looking domain and adding a bank-themed subdomain later is a common way to avoid fresh-domain filters. The server sits on a network registered to New Dhaka Hardware in Bangladesh, while the IP geolocates to the US. The free Let's Encrypt certificate gives the page a padlock, which shows encryption only and does not prove the site is legitimate.
If you entered credentials here, contact Liberty Crest Bank through the number on your card or statement. Change your online banking password and any reused passwords, and reset or re-enroll your two-factor authentication. Review recent transactions and ask the bank to block or reissue cards if you typed card details. Watch for follow-up calls or messages posing as the bank's fraud team. Defenders should block the domain and its parent at mail and web gateways, search logs for visits, and report the page to the impersonated bank.
Stored page, network and scanner observations, grouped by source and observation time.
Beobachtet: · Retrieved:
| Uuid | 01a0b498-775a-73fc-b105-43c238e8da85 |
|---|---|
| Final url | https://glochase.elafure.com/ |
| Status | 200 |
| Ip | 163.61.188.2 |
| Ptr | s3.whitelabelclouds.com |
| Contacted domains | [
"widget-v3.smartsuppcdn.com",
"www.gstatic.com",
"fonts.gstatic.com",
"cdn.jsdelivr.net",
"websocket-visitors.smartsupp.com",
"translations.smartsuppcdn.com",
"translate-pa.googleapis.com",
"bootstrap.smartsuppchat.com",
"translate.googleapis.com",
"fonts.googleapis.com",
"www.smartsuppchat.com",
"translate.google.com",
"code.jquery.com",
"cdn-cgi"
] |
| Contacted IP addresses | [
"2a02:6ea0:c77a::48",
"2001:4860:4841:400::",
"2a02:6ea0:c700::101",
"63.179.80.202",
"2a00:1450:4001:c1f::5f",
"2a00:1450:4001:c1f::5e",
"142.251.13.94",
"2a00:1450:400a:1001::5f",
"2a02:6ea0:c700::11",
"2a00:1450:4001:c25::64",
"2606:4700::6811:d005",
"2a04:4e42:600::411",
"163.61.188.2"
] |
| Asns | [
"60068",
"15169",
"16509",
"13335",
"54113",
"153568"
] |
| Countries | [
"DE",
"US",
"CH",
"BD"
] |
| Linked domains | [
"translate.google.com",
"www.youtube.com",
"www.cnbc.com",
"www.investopedia.com",
"www.airtreks.com",
"facebook.com",
"twitter.com",
"instagram.com",
"linkedin.com"
] |
| Social | [
"https://www.youtube.com/watch",
"https://facebook.com",
"https://twitter.com",
"https://instagram.com"
] |
| Document hash | 5b89bf8f6b5497f4275385698b20615b2aed66a9b4d959aa86b315fcf0d6e038 |
| Script hashes | [
"ce9d07500ad91ec2b524c270764ec4c9a33e78320d8d374ec400ede488f6251b",
"120666e01d671db172cecd87aaaed5cb0feb2da24d971c291fe1b8e0f64b18ac",
"5932ef8c9c2d361a85d8834d47f508dbd305fda081fb646c18f7fbe76839080a",
"01f88dcee3ea695865770808ba43f18d9b0a0db51696c39d69ea2a607c108e78",
"4460f1596174d06cca957fdaca2c71e1a377cf1d6f07ee4c75ffb3bf3fc97a03",
"4e0781bdd2cbb5db04da3b5e059eeca34e325fabb893bee7457b5babf5b7c029",
"b98842a571aa1f32f8797a9d08186bb021f258925a8db4fe57d60129b858b1ec",
"8f195573d6fa06641814b476fea2b92579c983cac46d683f356238207692c9f5",
"c563abe9b3e16a2461415597e352e306678e093e2078d6f3b9618d902b1ad2c7",
"b57506318dccce1f06d2545f2db1bead5d46acb07df071aee7651d2c3013105d"
] |
| Globals | [
"_smartsupp",
"smartsupp",
"$",
"jQuery",
"SMARTSUPP_LOADED",
"$smartsupp",
"uidEvent",
"bootstrap",
"AOS",
"Odometer",
"_gsScope",
"_gsQueue",
"GreenSockGlobals",
"com",
"_gsDefine",
"Ease",
"Power4",
"Strong",
"Quint",
"Power3",
"Quart",
"Power2",
"Cubic",
"Power1",
"Quad",
"Power0",
"Linear",
"TweenLite",
"TweenPlugin",
"TweenMax",
"TimelineLite",
"TimelineMax",
"BezierPlugin",
"CSSPlugin",
"BackOut",
"BackIn",
"BackInOut",
"Back",
"SlowMo",
"SteppedEase"
] |
| Cookies | [
"XSRF-TOKEN",
"globalchase_session"
] |
| Storage keys | [
"cuex_theme"
] |
| Tls | {
"san": [
"glochase.elafure.com",
"www.glochase.elafure.com"
],
"cipher": "AES_128_GCM",
"issuer": "YR2",
"subject": "www.glochase.elafure.com",
"protocol": "TLS 1.3",
"valid_to": "2026-12-17T05:46:51Z",
"valid_from": "2026-09-18T05:46:52Z"
} |
| Domain age days | 61 |
| Apex age days | 279 |
| Tls age days | 0 |
| Tls valid days | 89 |
| Requests | 102 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 97,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"genericbanking"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"Generic Banking"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"server": "LiteSpeed",
"content-type": "text/html; charset=UTF-8"
} |
Beobachtet: · Retrieved:
| Uuid | b9bcf78f-0bd1-4d26-b941-baf0c65f8f75 |
|---|---|
| Final url | https://glochase.elafure.com/ |
| Status | 200 |
| Weitergeleitet | https-only |
| History | [
{
"url": "http://glochase.elafure.com/",
"status": 307
},
{
"url": "https://glochase.elafure.com/",
"status": 200
}
] |
| DOM structure hash | 232349e1ce5ea531d15701888f8a183d352fc6626d5cab9a5dbffa96267b4c73 |
| Document hash | 5b89bf8f6b5497f4275385698b20615b2aed66a9b4d959aa86b315fcf0d6e038 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "glochase.elafure.com",
"type": "A",
"value": "163.61.188.2"
}
] |
| Dnssec valid | false |
| Ip | 163.61.188.2 |
| Registration record | {
"registrar": "TuringSign Inc. d/b/a Cosmotown",
"created": "2025-12-13T10:54:02Z",
"updated": "2025-12-13T10:54:02Z",
"expires": "2026-12-13T10:54:02Z",
"nameservers": [
"dns1.lytehosting.com",
"dns2.lytehosting.com",
"dns3.lytehosting.com",
"dns4.lytehosting.com"
]
} |
dns1.lytehosting.comdns2.lytehosting.comdns3.lytehosting.comdns4.lytehosting.comLocation describes the IP network.
3ea88ae3c8b8562cf2af87a22c9ac2afa77a1aa32f5a74df5371460cf8eb3a67www.glochase.elafure.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.glochase.elafure.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of glochase.elafure.com · checked Sep 18, 2026
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.
glochase.elafure.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unbekannt→live_content
content_served
redirected→live_content
content_served
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
Unbekannt→live_content
content_served
11→12
10→11
9→10
6→9
Erreichbar
No threat flag
View source12/91 engine detections
View sourcePD-20260918-2A7E37
glochase.elafure.com
View sourcePage captured
View sourcePD-20260918-2A7E37 Recipient: abuse@whiteprivacy.com Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
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 ↗
glochase.elafure.com)Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.
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
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenMelden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenAktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBeobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt
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.