VirusTotal
12 / 91 engine detections
打开报告“Hellcase – CS2 Cases, Upgrades”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@registrar.eu.
The latest stored availability evidence still shows the domain reachable; 4 months 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.
钓鱼: hellcase.london — 隐形 · 可达 (HTTP 200). 证据摘要: VirusTotal 12/91 (alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker); URLQuery 1 alert; 2…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
12 / 91 engine detections
打开报告1 threat-system alert
打开报告16 community references
打开报告provider verdict: clean
打开报告14 已检查 — 未发现拦截
No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Nextron YARA rules | hellcase.london/templates/hellcase/js/index.js |
malware | Unique code from Jetriz, Swid & Jeniva of the Tetris framework |
PhishDestroy threat report
This domain is currently flagged as a high‑risk generic phishing site. The site resolves to 188.114.97.3, which belongs to Cloudflare, Inc. in Canada and is protected by a Let’s Encrypt/E8 certificate. HTTP requests return status 200 and the service supports HTTP/3, indicating a modern web stack. Technology fingerprints include PHP behind Cloudflare. The public page title reads “Hellcase – CS2 Cases, Upgrades”. Infrastructure analysis shows the domain was registered through Hosting Concepts B.V. d/b/a Registrar.eu. Reputation data lists the domain on three security blocklists and it appears in two AlienVault OTX threat pulses. VirusTotal scans have recorded 15 detections out of 91 scanners, and the domain is specifically blocked by PhishDestroy, MetaMask, and SEAL. Gridinsoft assigns a trust score of 0 / 100. The combination of multiple vendor detections, blocklist listings, and low trust score supports a high confidence that the site is being used for phishing. However, the exact content and phishing payload have not been publicly disclosed, so the precise lure and target audience remain unknown. Defenders should consider adding the domain to deny‑list controls, monitor DNS queries for the IP address, and enforce TLS inspection to capture any credential submissions. Ongoing observation of related traffic and correlation with user reports is recommended to confirm exploitation attempts.
Last checked
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.
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.
Edge-IP 声誉不属于此域。
woz.ns.cloudflare.comLocation describes the IP network.
901a5d9ac19d705351375f781c2e268b430d0f00991c3ce91a2be4b80ec99545Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of hellcase.london · checked Jun 26, 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.
content_divergence · alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
hellcase.london
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
14→15
16 community references
View source12/91 engine detections
View sourceNo threat flag
View sourcePD-20260609-F4F5EF
hellcase.london
View source由 1 名社区成员报告;首次发现于 2026年6月9日
PD-20260609-F4F5EF Recipient: abuse@registrar.eu Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (GB): Computer Misuse Act 1990 Fraud Act 2006 Communications Act 2003 - Section 127 UK law criminalizes unauthorized computer access, fraud, and malicious communications. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
hellcase.london)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.