Is virtual-vote.pages.dev a scam? TrustSniffer's high-risk assessment: 0/100

Overview

The site is a single-page web property at a subdomain of a free, shared developer-hosting platform. It presents itself with the page title "Create, co-own, interact with AI Agents | Virtuals Protocol". Its only visible content is a short block of marketing-style text, with no further pages or product detail. Its apparent purpose is to look like an entry point to an AI-agent tokenisation and ownership platform, presumably a voting or participation front end, though the page does not say what it does or who runs it.

Scam/Impersonation Risk

Contradictory signals are present, and they define the risk profile. Multiple independent threat-intelligence engines classify the domain as malicious or suspicious, and a separate external blacklist also lists it. These are converging, confirmed blacklist detections, not isolated anomalies. The site also borrows the name of an established AI-agent protocol in its page title. It runs from a generic, freely registrable subdomain, not from any domain that brand would be expected to control. This is a classic pattern in crypto-themed lookalike and phishing campaigns, where a brand-styled "vote", "claim" or "participate" page is used to lure visitors into signing transactions or disclosing credentials. No affiliation with the named protocol is evidenced. The page itself gives no detail on what a visitor would vote on or receive. Behavioural testing found no wallet-connection prompts, no wallet-drainer behaviour, no clipboard manipulation, no hidden or externally posting credential forms, and no cloaking. It also found that all external network calls went to recognised services. Absence of those behaviours in a short test does not offset the reputation detections, because malicious payloads on such pages are often activated later or only for specific visitors. No identity contradiction between legal entities was observed. The risk comes entirely from the reputation and branding signals. Evidence:

• Homepage: the title text presents the page under a well-known AI-agent protocol's branding, while the domain is a shared-platform subdomain with a high lookalike similarity to its parent hosting domain.
• Threat-intelligence reputation: multiple engines return malicious and suspicious verdicts, and an external blacklist flags the domain. No Google Safe Browsing hit was recorded.
• Domain provenance: the domain is about 119 days old (~0.33 years), and the web archive holds 1 snapshot, dated 2026-07-05, so only 1 year of history is tracked.
• Brand recognition: DeFiLlama has no listing for the site, so there is no TVL or protocol recognition to support the protocol-style branding.

Regulatory Verification Notes

The captured homepage contains very little text. It names no operating company, registration number, licence, jurisdiction or terms of service, and it has no visible legal or about pages. Because the site invites participation in a token or AI-agent ecosystem, which is a financial-adjacent activity, the lack of any identifiable operator is a material disclosure gap. On its own this would be a verification matter. Here it adds to the confirmed reputation detections and does not stand alone. No third-party broker or regulatory-register entry matches the domain, so there is no external regulatory standing to rely on. Independent confirmation of who operates the site has not been established. Evidence:

• Homepage: no company name, licence number, registered address or regulator reference appears in the captured page text.
• Legal pages: no terms, privacy policy or about page was captured for the site.
• Hosting: served from AS13335 (Cloudflare, Inc., US).
• Transport security: a domain-validated TLS certificate issued by WE1, valid to 2027-01-18. This confirms encryption only, not the operator's identity.

What to Verify Next

The reputation detections should be treated as the working assumption until the operator proves otherwise. The brand named in the page title should be reached only by typing its official address manually or through a bookmark saved earlier, never through this site. A visitor should check whether the official channels of that project list or reference this vote or participation page. The same applies to any message, post or advertisement that directed the visitor here, since the source of the referral often reveals the campaign. If the destination claims to relate to a protocol, a visitor should confirm contract addresses and any governance announcements through the official documentation, and not through links on this page. Official support channels should be confirmed through an independent route. Evidence:

• Homepage: the branded title is the only link to a named project, and it is unsupported by any visible attribution.
• Domain history: the domain's short life and single archived capture leave no earlier record that could corroborate legitimate use.
• Reputation checks: the current detections should be re-queried with the threat-intelligence sources before any later reassessment.

Summary Verdict

The overall posture is one of critical risk. Independent, convergent reputation detections combine with a very young domain, thin history and an unverified operator. Confirmed adverse signals decisively outweigh the neutral and technically sound features observed, so the site does not read as an established or reliable entity.

Infrastructure Integrity

The site is delivered through a trusted CDN and WAF, and all observed addresses are edge servers, so the origin server is not exposed to direct view. This protects the site against some attacks and indicates a standard, mainstream deployment. It is a mitigating factor only: it also prevents independent verification of the true hosting origin, and it cannot offset the reputation findings. A valid certificate and recognised network ownership are routine for sites on this platform and do not indicate legitimacy.

Closing Assessment

The site should not be used for login, credential entry, wallet connection, transaction signing or any payment. If it must be examined, this should be done read-only from an isolated environment. Anyone who has already interacted with it should revoke any token approvals granted and change any credentials that were entered. The incident should be reported to the security team or the impersonated brand's official support channel.