Zum Sicherheitsbericht springen
Domänensicherheit und Bedrohungsinformationen
helplistings.blog favicon

helplistings.blog

“Vote”

Registrar
Hosting Concepts
Resolved IP
85.239.149.60
Registered
14.10.2026
PhishDestroy assessment Kritisch
Verfügbarkeit Letzter bekanntermaßen aktiv Letzte gespeicherte Erreichbarkeitsbeobachtung Beobachtet · HTTP probe
VirusTotal-Erkennungen: 11/92 Spamhaus DBL: DBL_SPAM Gespeicherte Sperrlistenübereinstimmungen: 2 Automatische Markenkennung: Coinmarketcap Junge Domäne: 5 Tage alt
16.10.2026 1 Report Sent
API
Diese Domain wurde als bösartig markiert.
Sicherheits-Engines melden eine Entdeckung: 11. Öffentliche Blocklisten, die eine Übereinstimmung melden: 2. Seien Sie äußerst vorsichtig – Geben Sie keine Anmeldeinformationen oder persönlichen Daten ein.
ABUSE NOTICE · 72H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

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.

Elapsed since first report
3 days
Reports sent
1
Latest case ID
PD-20261016-EDF743
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Reports sent
view timeline
Berichtsübersicht

Coinmarketcap-Imitation: helplistings.blog — Letzter bekanntermaßen aktiv (HTTP 200). Zusammenfassung der Beweislage: VirusTotal 11/92 (ChainPatrol…

Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.

Source evidenceVirusTotal 11 / 92 7 sources

Spamhaus DBL

DBL_SPAM

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Kritisch
VirusTotal
11 / 92
Page captures
3

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Gelistet View source
PhishDestroy PhishDestroy list View source
SEAL Gelistet View source

Last checked

Gespeicherte Aufnahme · 3 captures

Observed page title
Vote
Automated brand references
Coinmarketcap
TLS-Zertifikat
Ausgestellt von Let's Encrypt / YR2 · stored validity ends in 84 days

Domain details

Domain
URLScan verdict Analyse abgeschlossen score 0 report ↗
IP-Reputation abuse score 2/100 2 reports Open ProxyPort ScanHackingExploited Host checked 16.10.2026
Registrar Hosting Concepts NL(NL)
ICANN-RegistrierungsstelleICANN Lookup (RDAP) →
RegistrierungErstellt 14.10.2026 (5d · Brand New!) — Expires 14.10.2027
HTTP-Status200
Technische DetailsProvenance & timestamps
Erstmals entdeckt16.10.2026
DOM Analysisanalyzed 17.10.2026score 100/1001 brand signal
Submitted URLhttp://helplistings.blog/
Favicon Hash
Fall-ID
ICANN OVERSIGHT

Akkreditierung und RAA-Kontext

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft Nichts wird automatisch gesendet.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
85.239.149.60
Network ASN
AS207043
Organization
Dedik Services Limited
Observed location
Frankfurt am Main, DE
Server header
SimpleHTTP/0.6 Python/3.10.12

Nameserver 2

  • amos.ns.cloudflare.com
  • nina.ns.cloudflare.com

Location describes the IP network.

TLS-Zertifikat

Issuer
Let's Encrypt / YR2
Valid from
2026-10-14 19:10:35
Valid until
2027-01-12 19:10:34
Validity
Within stored validity dates
Collection time
2026-10-16 22:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprint6b558ee9d9823e8833f312dc2601b05979cc7e341da7e013539ed49f3cbfe665

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 22:30:03 UTC

Primary outcome Aktive Inhalte reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Aktive Inhalte Ordinary HTTP content served 90% 2026-10-19 22:30:03 UTC
RDAP registration Unbekannt
Observed timeline last reachable: 2026-10-19 22:35:33 UTC last content: 2026-10-19 22:30:03 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Abgleich mit Bedrohungsdaten · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Live-fetched via CF worker proxy pool · cached 24h
Technologien · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Diese Domain melden Reichen Sie Beweismaterial ein und helfen Sie mit, andere zu schützen

VirusTotal-Analyse

11 / 92 Sicherheitsanbieter haben diese Domain markiert
View on VT
Last analyzed First positive detection Previous stored snapshot: 3 detections
ChainPatrol
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
SOCRadar
URLQuery

Archivierte Beweise

Wayback Machine Snapshot
Zur Beweisüberprüfung steht ein historischer Schnappschuss zur Verfügung
View Archive
Website-Performanceanalyse

Google PageSpeed Insights — mobile performance audit of helplistings.blog · checked Oct 16, 2026

100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.75s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://helplistings.blog/
Vote
Community listing vote on CoinMarketCap.
Reaktion
HTTP 200
HTML body
11.0 KB
Compressed
3.6 KB
Links
1 internal · 0 external
Selected response headers
Server: SimpleHTTP/0.6 Python/3.10.12
Content-Type: text/html; charset=utf-8
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 54e8edf66a7f7fad7d975470fa2ea7cc036757ba7897d05f8edf87f37cd47aab
Open Graph title: Vote
Open Graph description: Community listing vote on CoinMarketCap.
Twitter card: summary_large_image
Saved response-header values · 4
Content-Length
11274
Content-Type
text/html; charset=utf-8
Date
Fri, 16 Oct 2026 19:29:21 GMT
Server
SimpleHTTP/0.6 Python/3.10.12

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  2. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  3. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    11/92 engine detections

    View source
  3. Abuse report sent

    PD-20261016-EDF743

    abuse@dedik.io
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    helplistings.blog

    View source

Community-Erkenntnisse

1 Community-Meldung

KategoriePHISHING

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=

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

helplistings.blog

Nachweise und externe Berichte

Community Scam Report — ChainAbuse
1 report filed for helplistings.blog (1 written by a person) · category: Phishing · source checked
“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”
— reported by Anonymous on Oct 17, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Momentaufnahme der übermittelten Beweise
Sent: Ledger records: 1 Case ID: PD-20261016-EDF743 Recipient: abuse@dedik.io
PDF notice generated
Eingehende Analyse
Help & reporting

Wurden Sie von dieser Website betroffen?

5 evidence signal groups linked 1 stored notification records Letzter bekanntermaßen aktiv
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Official reporting routes

Vorsicht vor Betrügern, die mit der Rückforderung von Geldern locken! Kriminelle nehmen unter Umständen erneut Kontakt zu Opfern auf und geben dabei vor, Ermittler, Anwälte oder Beitreibungsbeamte zu sein. Zahlen Sie keine Vorabgebühren und geben Sie keine Anmeldeinformationen weiter. Erfahren Sie mehr über Betrug im Zusammenhang mit Wiederaufbaumaßnahmen →

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.

97-Länder-Verzeichnis

Template-based draft · optional AI wording assistance requires separate consent

KI-gestützter Entwurf – Vorfalldetails werden vom KI-Anbieter verarbeitet · Überprüfen Sie es und reichen Sie es selbst ein
After a phishing incident

Empfehlungen und Ratschläge für Betroffene

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Was soll ich sofort tun?

Dringend

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Alle Passwörter ändern — E-Mail, Exchange-Konten, alles, wofür dasselbe Passwort verwendet wird
  • 2FA aktivieren mit einer Authentifizierungs-App (nicht per SMS). Deaktivieren Sie die SMS-basierte Wiederherstellung
  • Karten einfrieren Falls Sie auf der Phishing-Seite Ihre Bankdaten eingegeben haben

Welche Informationen sollte ich für meinen Bericht sammeln?

FBI-Richtlinien

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Genaue Daten und Uhrzeiten — jeder Transaktion und des ersten Kontakts mit dem Betrüger
  • Screenshots — betrügerische Websites, Chat-Nachrichten, E-Mails, Wallet-Transaktionen, soziale Medien
  • Alle URLs und Domains die der Betrüger verwendet (einschließlich helplistings.blog)
  • Kommunikation — E-Mails, SMS, Telefonnummern, Benutzernamen, die der Betrüger verwendet hat

Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.

Wo soll ich den Betrugsfall melden?

  • FBI IC3 — Internet Crime Complaint Center (Meldestelle der US-Bundesbehörden)
  • Europol — Meldungen zu Cyberkriminalität in Europa (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Ortspolizei — sorgt für eine offizielle Dokumentation, auch wenn sie nicht sofort handeln können

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Gefälschte Websites — pixelgenaue Kopien legitimer Websites mit leicht abgeänderten Domains
  • Schweineschlachtung — über Wochen hinweg über Telegram, WhatsApp und Dating-Apps aufgebautes Vertrauen, dann wurde Geld gestohlen
  • Betrugsmaschen im Zusammenhang mit der Rückforderung von Geldern — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Durch KI gestützte Betrugsmaschen — Deepfakes, automatisiertes Phishing und KI-generierte Websites, die es erschweren, Betrugsversuche zu erkennen

Wie kann ich mich in Zukunft schützen?

  • Offizielle Websites als Lesezeichen speichern — Klicken Sie niemals auf Links in E-Mails, Direktnachrichten oder Anzeigen
  • Domains überprüfen — nachsehen, ob PhishDestroy Bevor Sie Kontakt aufnehmen: Überprüfen Sie HTTPS, die Rechtschreibung und das Alter der Domain.
  • „Zu schön, um wahr zu sein“ = Betrug — garantierte Renditen, Prominente als Werbeträger, dringende Fristen

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Bleiben 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

Echtzeit-Bedrohungsfeed Einspruch gegen diesen Eintrag einlegen
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Diesen Bericht einbetten

Teilen Sie diese Bedrohungsinformationen auf Ihrer Website oder in Ihrem Blog

embed.html
<iframe
  src="https://phishdestroy.io/de/embed/domain/helplistings.blog"
  title="PhishDestroy threat report for helplistings.blog"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>