Skip to security report
Analytics Dashboard
Domain security and threat intelligence
helpingvotes.forum favicon

helpingvotes.forum

In short

helpingvotes.forum is a MetaMask impersonation page detected by PhishDestroy on 2026-09-27. Risk: critical (90/100). Registrar: Registrar.eu. Status: Last known active. Hosting: DEDIK-IO DEDIK SERVICES LIMITED, GB. VirusTotal: 6/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“Vote”

Registrar
Registrar.eu
Resolved IP
93.152.224.220
Registered
Sep 25, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 6/92 Spamhaus DBL: DBL_SPAM Stored blocklist matches: 2 Automated brand label: MetaMask Young domain: 26 days old
Sep 27, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 6. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
6 / 92
engine detections
Google Safe Browsing
No threat flag
Page captures
10
open gallery
Domain age
26 days
Source evidenceVirusTotal 6 / 92 6 sources

VirusTotal

6 / 92 engine detections

Open report

Spamhaus DBL

DBL_SPAM

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Analysis

Critical
VirusTotal
6 / 92
Page captures
10
Page captures Source results Registration record

PhishDestroy threat report

Overview

helpingvotes.forum is an impersonation phishing page that presents itself under the plain title "Vote" and asks visitors to help someone by casting a vote. PhishDestroy first detected it on 2026-09-27. The wallet-focused MetaMask and SEAL blocklists also list it, which places it in the crypto scam ecosystem. As of 2026-10-19 the site was still online and serving its phishing content.

How the scam works

Voting lures usually arrive as a personal message from a friend or community member asking for a quick vote in a contest or poll. The link opens a page dressed up as a trusted service. To vote, the visitor must log in or connect a wallet. Whatever is entered goes to the operators, who can then take over the account or wallet and send the same "please vote" message to the victim's contacts. Victims lose control of their accounts and, where a wallet is involved, the funds the attackers can reach.

Evidence

On 2026-10-07, 6 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar and Sophos. That count is modest, so many security tools will not block the page yet. Independent listings back the verdict. MetaMask and SEAL list it alongside PhishDestroy, and Spamhaus DBL classifies the domain as spam, which points to it being pushed through unsolicited messages.

Infrastructure

The domain was registered through Registrar.eu on 2026-09-25, only two days before PhishDestroy caught it. That short gap fits a throwaway domain set up for a single campaign. It resolves to 93.152.224.220 on the DEDIK-IO DEDIK SERVICES LIMITED network, a provider registered in Great Britain, with the server located in Germany. A Let's Encrypt certificate gives the page a padlock, which says nothing about whether the site is safe.

What to do

If you entered a password on this page, change it at once on every service that shares it, turn on app-based two-factor authentication and sign out other active sessions. Warn your contacts, because hijacked accounts are used to spread the same vote request. If you connected a wallet, revoke any approvals granted around that time. If you typed a seed phrase, move your funds to a new wallet immediately. Defenders should block the domain and its IP, and treat incoming "vote for me" messages with links as suspicious.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-09-27T02:36:52Z

Observed: · Retrieved:

Uuid
01a0e0b8-da40-744e-8d6c-5785b8aeb935
Final url
https://helpingvotes.forum/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://helpingvotes.forum/",
        "from": "http://helpingvotes.forum/",
        "status": 307
    }
]
Ip
93.152.224.220
Contacted domains
[
    "coinmarketcap.com"
]
Contacted IP addresses
[
    "3.174.46.19",
    "93.152.224.220"
]
Asns
[
    "16509",
    "207043"
]
Countries
[
    "US",
    "DE"
]
Document hash
f57588e96630cf47119a66ea608300ca5ca507a669f1364320e28901d75cdea4
Globals
[
    "requestResize"
]
Tls
{
    "san": [
        "helpingvotes.forum"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "helpingvotes.forum",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-24T21:05:02Z",
    "valid_from": "2026-09-25T21:05:03Z"
}
Domain age days
1
Apex age days
1
Tls age days
1
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 95,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "SimpleHTTP/0.6 Python/3.10.12",
    "content-type": "text/html; charset=utf-8"
}
Cloudflare Radar · 2026-09-27T02:37:24Z

Observed: · Retrieved:

Uuid
a2523e6a-0edc-4a1d-90e4-d9fced7fb90c
Final url
https://helpingvotes.forum/
Status
200
History
[
    {
        "url": "https://helpingvotes.forum/",
        "status": 200
    }
]
DOM structure hash
bf1f50c49efdc3a8f59c23f3e6d8d1c64a8b3996227f608f3c0d8f6867a700c6
Document hash
f57588e96630cf47119a66ea608300ca5ca507a669f1364320e28901d75cdea4
Domain risks
[
    "New Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "helpingvotes.forum",
        "type": "A",
        "value": "93.152.224.220"
    }
]
Dnssec valid
false
Ip
93.152.224.220
Registration record
{
    "registrar": "Registrar.eu",
    "created": "2026-09-25T21:56:10Z",
    "updated": "2026-09-25T21:56:13Z",
    "expires": "2027-09-25T21:56:10Z",
    "nameservers": [
        "kanye.ns.cloudflare.com",
        "martha.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-21T09:54:19Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 37
}
Reputation
0
Registrar
Registrar.eu
Created
2026-09-25T21:56:10Z
Expires
2027-09-25T21:56:10Z
Updated
2026-09-25T21:56:13Z
First seen
2026-09-25T22:15:45Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "kanye.ns.cloudflare.com"
    },
    {
        "ttl": 60,
        "type": "A",
        "value": "93.152.224.220"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "kanye.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "martha.ns.cloudflare.com"
    }
]
Dns at
2026-10-21T09:58:13Z
Jarm
2ad2ad0002ad2ad00042d42d00000051af7d8070a18e002eaaedf620fa118c
Certificate
{
    "san": [
        "helpingvotes.forum"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "5d2771a6f0eeabaa6713536e594b5ba74a2",
    "sha256": "c1c890596732e0c534cf04257b8254721fe2118292dcc70ec546631270be3475",
    "subject": "helpingvotes.forum",
    "valid_to": "2026-12-24T21:05:02Z",
    "valid_from": "2026-09-25T21:05:03Z"
}
Registration record
{
    "registrar": "Registrar.eu",
    "registrar_iana_id": "1647",
    "registrar_url": "www.registrar.eu",
    "created": "2026-09-25T21:56:10Z",
    "updated": "2026-09-25T21:56:13Z",
    "expires": "2027-09-25T21:56:10Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "kanye.ns.cloudflare.com",
        "martha.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-09-25T21:56:10Z",
        "registration": "2026-09-25T21:56:10Z",
        "registrar expiration": "2027-09-25T21:56:10Z",
        "last update of RDAP database": "2026-10-17T15:16:47Z"
    }
}

Questions about helpingvotes.forum

Is helpingvotes.forum legit?

No. PhishDestroy classifies helpingvotes.forum as a MetaMask impersonation page (risk: critical, 90/100); it was first detected on 2026-09-27. VirusTotal: 6/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is helpingvotes.forum safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on helpingvotes.forum. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used helpingvotes.forum?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

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

Last checked

Stored Capture · 10 captures

Primary capture 1 / 10
SourcePrimary capture
Recorded2026-09-27 02:37 UTC
StateStored capture
Position1 / 10
Open capture Wayback Download
Observed page title
Vote
Automated brand references
Coinmarketcap
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 63 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 2/100 2 reports Open Proxy checked Sep 27, 2026
Registrar Registrar.eu NL(NL)
Abuse contactabuse@dedik.io
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for helpingvotes.forum →
RegistrationCreated Sep 25, 2026 (26d · Very New!) — Expires Sep 25, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 27, 2026
DOM Analysisanalyzed Oct 9, 2026score 90/1001 brand signal
Submitted URLhttp://helpingvotes.forum/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
93.152.224.220
Network ASN
AS207043
Organization
DEDIK-IO DEDIK SERVICES LIMITED, GB
Observed location
Frankfurt am Main, DE
Server header
SimpleHTTP/0.6 Python/3.10.12

Nameservers 2

  • kanye.ns.cloudflare.com
  • martha.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-09-25 21:05:03
Valid until
2026-12-24 21:05:02
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:37 UTC
Collection source
PhishDestroy collector
Certificate fingerprintc1c890596732e0c534cf04257b8254721fe2118292dcc70ec546631270be3475
Certificate names · 1 SAN
  • helpingvotes.forum

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

viewdns.info · 93.152.224.220rapiddns.io

Latest Classified Outcome 2026-10-22 10:28:41 UTC

Primary outcome Live content 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 Live content Ordinary HTTP content served 90% 2026-10-22 10:28:41 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:28:41 UTC last content: 2026-10-22 10:28:41 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.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 7 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
Sophos

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of helpingvotes.forum · checked Sep 27, 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
0.76s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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 history20

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

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 15
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · Recorded state

    live_content

    content_served

  15. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    6/92 engine detections

    View source
  3. URLScan

    Page captured

    View source
  4. Added to PhishDestroy

    helpingvotes.forum

    View source

Lookalike domains

79 stored lookalike domains

etamask.io omission Internal report meetamask.io repetition Internal report megamask.io replacement Internal report metam.ask.io subdomain Internal report metamaak.io replacement Internal report metamadk.io replacement Internal report metamaks.io transposition Internal report metamassk.io insertion Internal report metamsask.io insertion Internal report metamssk.io replacement Internal report metanask.io homoglyph Internal report metanmask.io homoglyph Internal report
Show all (67)
metasmask.io insertion Internal report metramask.io insertion Internal report mewtamask.io insertion Internal report mmetamask.io homoglyph Internal report mtamask.io omission Internal report mwetamask.io insertion Internal report nmetamask.io homoglyph Internal report metamark.io bitsquatting Internal report metamaskj.io addition Internal report metammask.io homoglyph Internal report metamnask.io homoglyph Internal report emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Check for cloaking

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

helpingvotes.forum

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 6 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including helpingvotes.forum)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

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?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/helpingvotes.forum"
  title="PhishDestroy threat report for helpingvotes.forum"
  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>