VirusTotal
13 / 93 engine detections
Abrir relatório“RustHollow | Community for RUST Skin Designers”
Imitação de Steam: rusthollow.design — Conteúdo indisponível. Resumo das evidências: VirusTotal 13/93 (ADMINUSLabs, alphaMountain.ai, BitDefender, CyRadar…
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
13 / 93 engine detections
Abrir relatório1 community reference
Abrir relatórioprovider verdict: clean
Abrir relatórioNo threat flag
Abrir relatórioNo malicious flag
Abrir relatórioResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
As of July 23, 2026, the domain rusthollow.design is flagged for brand impersonation, specifically targeting the Steam community. The domain was registered through Web Commerce Communications Limited on November 10, 2025, and has since been taken offline. Infrastructure analysis reveals that the domain was hosted in Russia under the AS57724 DDOS-GUARD LTD network, resolving to the IP address 185.178.208.158. The domain is associated with nameservers ns1.ddos-guard.net and ns2.ddos-guard.net, which are known for providing DDoS protection services but can also be used by malicious actors to evade detection.
Gridinsoft has assigned this domain a trust score of 0/100, indicating a high level of suspicion. The domain appears on one security blocklist, PhishDestroy, and has been flagged by 13 out of 93 security vendors, further corroborating its malicious nature. Analysis indicates that the page title for the domain was 'RustHollow | Community for RUST Skin Designers,' which could be used to mislead visitors into believing it is an official or affiliated community for the game RUST.
The lack of an SSL certificate adds to the domain's suspicious profile, as legitimate sites typically use SSL to secure connections. Despite the domain being currently offline, defenders should remain vigilant and block access to prevent any potential residual threats. The exact content and functionality of the site have not been analyzed, but the available evidence strongly suggests that it was used for brand impersonation, posing a risk to Steam users and the broader gaming community.
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.
ns1.ddos-guard.netns2.ddos-guard.netLocation describes the IP network.
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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='rusthollow.design', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
rusthollow.design
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/56de1e8a-ce8f-4129-9179-fb4ff2a59a03
No threat flag
View sourcePage captured
View source1 community references
View source13/93 engine detections
View sourcerusthollow.design
View sourceDenunciado por 1 membro da comunidade; visto pela primeira vez em 10/11/2025
Listed domains receive at least one abuse report; this entry has no retained notification history.
Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.
Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.
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 ↗
rusthollow.design)Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.
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
Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública
Digitalize agoraEnvie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade
DenunciarRelatórios recentes de phishing e alterações de disponibilidade observadas
MonitorarMonitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo
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.