VirusTotal
11 / 92 engine detections
Raporu aç“Vote”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dedik.io.
The latest stored availability evidence still shows the domain reachable; 3 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.
Coinmarketcap taklidi: helplistings.blog — Bilinen son aktif (HTTP 200). Kanıt özeti: VirusTotal 11/92 (ChainPatrol, alphaMountain.ai, BitDefender, CRDF…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
11 / 92 engine detections
Raporu açSuspicious
Raporu açDBL_SPAM
Scan report
Raporu açno community references
Raporu açNo threat flag
Raporu açNo malicious flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
helplistings.blog is an impersonation phishing page that poses as a legitimate service to win visitors' trust and harvest what they enter. It is listed on the MetaMask and SEAL blocklists, which points to crypto users as a likely audience. PhishDestroy first detected it on 2026-10-16, two days after the domain was registered. As of 2026-10-19 the site was still online and serving its phishing content.
The page carries the title "Vote", a common hook in impersonation schemes. Victims receive a link asking them to cast a vote, support a nominee or confirm participation. The page then asks them to log in or verify their identity through what looks like a trusted brand. Any credentials, recovery details or wallet connections entered there go straight to the operators. Victims typically lose control of their accounts, which are then used to spread the same lure to their contacts, or lose the assets those accounts protect.
On VirusTotal, 3 of 92 engines flagged the domain as of 2026-10-16: alphaMountain.ai, Gridinsoft and SOCRadar. That detection count is low, which is typical for a domain this new, so most vendor filters will not yet block it. The domain also appears on the PhishDestroy, MetaMask and SEAL blocklists. Spamhaus DBL lists it under DBL_SPAM.
The domain was registered on 2026-10-14 through Hosting Concepts B.V. d/b/a Registrar.eu. It resolves to 85.239.149.60, which sits on the DEDIK SERVICES LIMITED network in Germany. The site uses a TLS certificate from Let's Encrypt (YR2), so the padlock in the browser says nothing about whether the site is legitimate.
If you opened the page but entered nothing, close it and do not follow the voting prompt again. If you typed a password or code, change it immediately on the real service, enable two-factor authentication and sign out of all other sessions. If you connected a wallet, disconnect the site. If you entered a seed phrase or private key, treat the wallet as compromised and move your funds to a new wallet created from a fresh seed. Warn any contacts who sent you the link, since their accounts may already be hijacked. Defenders should block the domain and its IP at DNS and proxy level, search mail and chat logs for the domain, and report it to the registrar and hosting provider for takedown.
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.
amos.ns.cloudflare.comnina.ns.cloudflare.comLocation describes the IP network.
6b558ee9d9823e8833f312dc2601b05979cc7e341da7e013539ed49f3cbfe665Saved 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 helplistings.blog · checked Oct 16, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://helplistings.blog/Server: SimpleHTTP/0.6 Python/3.10.12Content-Type: text/html; charset=utf-854e8edf66a7f7fad7d975470fa2ea7cc036757ba7897d05f8edf87f37cd47aabsummary_large_image11274text/html; charset=utf-8Fri, 16 Oct 2026 19:29:21 GMTSimpleHTTP/0.6 Python/3.10.12Values retained by the collector; long values may be shortened during collection.
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.
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
No threat flag
View source11/92 engine detections
View sourcePD-20261016-EDF743
Page captured
View sourcehelplistings.blog
View source1 topluluk raporu
KategoriPHISHING
Fake "vote to list $TOKEN on the CoinMarketCap Top 100 Leaderboard" posts flood X from what look like hijacked accounts (about 117,000 posts since Oct 12 by X's counts), each linking to helpvote.help (current), helplistings.blog, helplists.blog or listsupport.help with ?contract=
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
helplistings.blog
“Fake "vote to list $TOKEN on the CoinMarketCap Top 100 Leaderboard" posts flood X from what look like hijacked accounts (about 117,000 posts since Oct 12 by X's counts), each linking to helpvote.help (current), helplistings.blog, helplists.blog or listsupport.help with ?contract=<token>. The vote page loads a script that reads its command server from BSC contract 0x1AC7d768E37B147c993dE943D704c4e92d7861A1 via getter 0xb68d1809, then downloads and runs remote JavaScript. Owner 0xb88eca7852a5e9b63”
PD-20261016-EDF743 Recipient: abuse@dedik.io Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
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 ↗
helplistings.blog)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
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
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin
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.