bonusmega.ru
“Истёк срок регистрации домена”
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@beget.ru.
The latest stored availability evidence still shows the domain reachable; 14 days 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.
bonusmega.ru — Último ativo conhecido (HTTP 200). Representação da marca: Unknown; Tipo de golpe: Impersonation. Resumo das evidências: VirusTotal 14/89 (alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, Chong Lua Dao, ESET); PhishDestroy score 100/100. Registrador: BEGET-RU.
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
Resumo das evidências
PhishDestroy first observed bonusmega.ru on Sep 6, 2026. Stored content metadata identifies Unknown as the apparent target. The captured page title is “Истёк срок регистрации домена”. Stored page analysis classifies the content as impersonation. Campaign clustering links the hostname to the Unknown kit. Current evidence score: 100/100 (critical).
One source contains a positive finding: VirusTotal. VirusTotal recorded 14 detections among 89 engines: alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, Chong Lua Dao, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Lionic, SOCRadar, Sophos, VIPRE, Webroot on Sep 18, 2026 at 02:09 UTC. Non-positive and contextual checks: AlienVault OTX listed 6 community pulse references (not vendor detections) on Sep 10, 2026 at 22:43 UTC. The separate external-blocklist snapshot contained no matches on Sep 20, 2026 at 22:20 UTC. URLQuery recorded no positive detection; no observation timestamp was retained. Google Safe Browsing returned no flag on Sep 19, 2026 at 16:00 UTC. URLScan completed without a malicious verdict (score 0) on Sep 6, 2026 at 23:08 UTC.
HTTP 200 was recorded on Sep 20, 2026 at 22:12 UTC. Registration records for the domain list BEGET-RU as the registrar and Aug 27, 2025 as the creation date. At collection time, the hostname resolved to 5.101.159.26 on AS198610 (Beget LLC). The recorded endpoint location is St Petersburg, RU. The stored server header is nginx. DOM analysis on Sep 6, 2026 at 22:22 UTC returned 98/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan.
Stored content provides classification context, but only one source contains a positive finding.
Inteligência de segurança de rede
Forensic History & Detection Timeline
-
VirusTotal Detections Update Sep 11, 2026 · 00:42 UTCVirusTotal scanner detections updated from 16 to 14. Resolved alerts: CyRadar, Seclookup.
-
Threat First Observed Sep 6, 2026 · 21:58 UTCDomain ingestion complete. Initial state is marked as alive pointing to IP
5.101.159.26.
Pipeline de resposta a ameaças
Status da lista de bloqueios pública
Evasion analysis
Cloaking suspected: scanner and victim titles differ
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
- Stored cloaking flag
- Not yet scanned
- Last cloaking scan
- Server header seen by scanner
nginx
Scanner note: alive_content: raw=ok; http=200; via=http_proxy; server=nginx
Análise do VirusTotal
Evidências e relatórios externos
PD-20260906-887AF7 Recipient: abuse@beget.ru Abuse notice text as sent to the provider
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 (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. 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.
Você foi afetado por este site?
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.
Notifique as autoridades locais
Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.
Verificar qualquer domínio
Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública
Digitalize agoraDenunciar phishing
Envie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade
DenunciarFeed de ameaças em tempo real
Relatórios recentes de phishing e alterações de disponibilidade observadas
MonitorarMantenha-se informado, mantenha-se seguro
Monitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo