hmelef.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; 13 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.
hmelef.ru — Serverfehler (HTTP 502). Markenidentität: Unknown; Betrugstyp: Impersonation. Zusammenfassung der Beweislage: VirusTotal 16/89 (ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, ESET); Google Safe Browsing flagged; Spamhaus DBL_PHISH; PhishDestroy score 100/100. Registrar: BEGET-RU.
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
Zusammenfassung der Beweislage
PhishDestroy first observed hmelef.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).
Positive findings are stored from 3 sources: VirusTotal, Google Safe Browsing, and Spamhaus DBL. VirusTotal recorded 16 detections among 89 engines: ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing, Gridinsoft, Lionic, Seclookup, SOCRadar, Sophos, VIPRE, Webroot on Sep 15, 2026 at 18:04 UTC. Google Safe Browsing flagged the domain: Social Engineering on Sep 20, 2026 at 16:01 UTC. Spamhaus DBL: DBL_PHISH on Sep 6, 2026 at 22:30 UTC. Non-positive and contextual checks: AlienVault OTX listed 5 community pulse references (not vendor detections) on Sep 15, 2026 at 18:05 UTC. The separate external-blocklist snapshot contained no matches on Sep 20, 2026 at 14:20 UTC. URLQuery recorded no positive detection; no observation timestamp was retained. URLScan completed without a malicious verdict (score 0) on Sep 7, 2026 at 17:08 UTC.
HTTP 502 server error was recorded on Sep 20, 2026 at 10:23 UTC. Registration records for the domain list BEGET-RU as the registrar and Aug 27, 2023 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 100/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan.
The content indicators and 3 positive source findings support the current Unknown-themed impersonation classification.
Erkenntnisse zur Netzwerksicherheit
Forensic History & Detection Timeline
-
VirusTotal Detections Update Sep 7, 2026 · 01:41 UTCVirusTotal scanner detections updated from 15 to 16. Added scanner alerts: SOCRadar.
-
Status Check Sep 6, 2026 · 21:50 UTCTelemetry event observed.
-
Threat First Observed Sep 6, 2026 · 21:46 UTCDomain ingestion complete. Initial state is marked as alive pointing to IP
5.101.159.26.
Pipeline zur Reaktion auf Sicherheitsbedrohungen
Status der öffentlichen Sperrliste
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: transient_502: raw=transient_502; http=502; via=http_proxy; server=nginx
VirusTotal-Analyse
Nachweise und externe Berichte
PD-20260906-BAF18E 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.
Wurden Sie von dieser Website betroffen?
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.
Melden Sie sich bei Ihren örtlichen Behörden
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
Jede beliebige Domain prüfen
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenPhishing melden
Melden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenEchtzeit-Bedrohungsfeed
Aktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBleiben Sie auf dem Laufenden, bleiben Sie sicher
Beobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt