VirusTotal
17 / 91 engine detections
Abrir relatórioPhishing: litigteleg.rest — Último ativo conhecido (HTTP 200). Resumo das evidências: VirusTotal 17/91 (ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua…
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
17 / 91 engine detections
Abrir relatórioMalicioso
Abrir relatório4 community references
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
litigteleg.rest is an impersonation phishing page that poses as a legitimate service to trick visitors into handing over access. The "teleg" in its name suggests Telegram as the lure, a common target in crypto-related account theft. PhishDestroy first flagged it on 2026-09-23. The site was still online and serving content when last checked on 2026-10-19.
Impersonation pages copy the look of a trusted brand's login or verification screen closely enough that the visitor doesn't question it. Whatever is typed in, such as a phone number, password, one-time login code or cloud password, goes straight to the operator. With a messaging account, that is enough to take over the session, read private chats and impersonate the victim to their contacts, often to push fake crypto deals or request funds. The damage spreads beyond the first victim because their trusted network becomes the next audience.
On 2026-10-02, 17 of 91 VirusTotal engines classified the domain as malicious. They include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, ADMINUSLabs, CyRadar and the Vietnamese anti-scam group Chong Lua Dao. That is a substantial consensus across unrelated vendors. Four AlienVault OTX threat pulses also reference the domain, and it is listed on the PhishDestroy blocklist.
The domain was registered through Namecheap on 2026-03-28, almost six months before PhishDestroy detected it. That gap suggests it may have been held in reserve or rotated into use quietly. Traffic runs through Cloudflare on an address geolocated to Canada, which places a proxy in front of the real origin server. Its Let's Encrypt certificate gives the page a browser padlock, which proves only an encrypted connection, not that the site is genuine.
If you entered a phone number, login code or password here, open your messaging app's settings now, end every active session you don't recognize, and set or change your two-step verification password. Change the password on any other account that shares it. Warn your contacts that messages from you since your visit may not be yours, and treat any crypto or payment request from them through that channel as suspect. Defenders should block the domain at DNS and proxy level, watch for lookalike names built on the same "teleg" pattern, and report it to Cloudflare and Namecheap so the content can be pulled.
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.
A reputação do Edge-IP não é atribuída a este domínio.
jermaine.ns.cloudflare.comLocation describes the IP network.
b4fd5424fd3a991afb2b1fb760b4ee7a5bbc79614e6345ad77575fad6ff2eff0Saved 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 litigteleg.rest · checked Sep 23, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Acessível→Indisponível
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Indisponível→Acessível
Acessível→Indisponível
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
Desconhecido→live_content
content_served
No threat flag
View source17/91 engine detections
View source4 community references
View sourcelitigteleg.rest
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
litigteleg.rest
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 ↗
litigteleg.rest)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.