Skip to security report
Domain security and threat intelligence
bullverse.ws favicon

bullverse.ws

In short

bullverse.ws is a MetaMask impersonation page detected by PhishDestroy on 2026-09-01. Risk: critical (95/100). Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 8/89 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“Bullrun”

Resolved IP
172.67.167.222
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 8/89 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: MetaMask
OTX: 4 refs Sep 1, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 8. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Source evidenceVirusTotal 8 / 89 · OTX 4 references 6 sources

VirusTotal

8 / 89 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

4 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
8 / 89
OTX
4 community refs
Page captures
2

PhishDestroy threat report

Overview

bullverse.ws is an impersonation phishing page that presents itself under the name "Bullrun" to pass as a legitimate crypto project. It targets crypto holders and wallet users, which is why wallet-focused blocklists have picked it up. PhishDestroy first detected it on 2026-09-01. As of 2026-10-19 the site was still online and serving its phishing content.

How the scam works

Impersonation pages like this copy the name, look and messaging of a real or hyped project so visitors believe they are on the official site. The "Bullrun" branding draws people in with the usual lures, such as a token claim, an airdrop, early access or a reward. The visitor is then pushed to connect a wallet, sign a transaction or hand over account details. Once that happens, attackers can move assets out of the wallet or take over the account. Funds lost this way are rarely recovered.

Evidence

Eight of 89 VirusTotal engines flagged the domain as of 2026-09-15: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, LevelBlue, SOCRadar and VIPRE. That count is modest, but the listings carry more weight. MetaMask and SEAL, both focused on crypto threats, list the domain alongside PhishDestroy. Spamhaus classifies it as phishing in its domain blocklist. Four AlienVault OTX threat pulses also reference the domain, so multiple independent researchers have tied it to malicious activity.

Infrastructure

The site sits behind Cloudflare, with its address resolving to Cloudflare's network in Canada. Cloudflare's proxy hides the real origin server from visitors and investigators. The certificate comes from Google Trust Services. The browser padlock only means the connection is encrypted and says nothing about whether the site is honest.

What to do

If you connected a wallet to bullverse.ws, use a revocation tool to check its token approvals and revoke any you do not recognize. If you signed anything you did not fully understand, move the remaining assets to a fresh wallet. If you entered a seed phrase, treat that wallet as compromised and empty it into a new one generated on a clean device. Never reuse that phrase. If you entered account credentials, change the password and enable 2FA. Security teams should block the domain at DNS and proxy level and add it to wallet and email filters. They should also report it to Cloudflare so the content behind its proxy can be taken down.

Collected source details

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

URLScan · 2026-09-01T20:08:36Z

Observed: · Retrieved:

Uuid
01a05e96-6577-703e-90c4-8e89b96c6376
Final url
https://bullverse.ws/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://bullverse.ws/",
        "from": "http://bullverse.ws/",
        "status": 307
    }
]
Ip
104.21.13.9
Contacted domains
[
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "104.16.79.73",
    "104.21.13.9"
]
Asns
[
    "13335"
]
Document hash
19e08557d1572a7e0b0c2b937b27d89f841827aeb7f8fa776c1c8f60b5c1ed35
Globals
[
    "short",
    "setStatus",
    "call",
    "telemetry",
    "top5ByValue",
    "getPricedErc20s",
    "telemetryAsset",
    "pickTopErc20",
    "scanAll",
    "doConnect",
    "pad64",
    "encodeTransfer",
    "doTransfer",
    "__cfBeacon",
    "$",
    "account",
    "scanning",
    "selectedAsset",
    "publicConfig",
    "connect",
    "transferBtn",
    "status"
]
Tls
{
    "san": [
        "bullverse.ws",
        "*.bullverse.ws"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "bullverse.ws",
    "protocol": "QUIC",
    "valid_to": "2026-11-30T11:09:12Z",
    "valid_from": "2026-09-01T10:10:46Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
90
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8"
}
Cloudflare Radar · 2026-09-01T20:51:57Z

Observed: · Retrieved:

Uuid
f86538f9-0ce0-4dab-9f52-bf62ec5bea48
Final url
https://bullverse.ws/
Status
200
History
[
    {
        "url": "https://bullverse.ws/",
        "status": 200
    }
]
DOM structure hash
0c5d30735cfdf6cedbc5dbc4d6490064d6feb22ff4e20c0065dc8eb75e514217
Document hash
19e08557d1572a7e0b0c2b937b27d89f841827aeb7f8fa776c1c8f60b5c1ed35
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "bullverse.ws",
        "type": "A",
        "value": "104.21.13.9"
    },
    {
        "name": "bullverse.ws",
        "type": "A",
        "value": "172.67.167.222"
    },
    {
        "name": "bullverse.ws",
        "type": "AAAA",
        "value": "2606:4700:3034::6815:d09"
    },
    {
        "name": "bullverse.ws",
        "type": "AAAA",
        "value": "2606:4700:3034::ac43:a7de"
    }
]
Dnssec valid
false
Ip
104.21.13.9
Registration record
{
    "registrar": "NameSilo, LLC",
    "created": "2026-09-01T12:00:02Z",
    "updated": "2026-09-01T12:07:05Z",
    "expires": "2027-09-01T12:00:02Z",
    "nameservers": [
        "carlos.ns.cloudflare.com",
        "walk.ns.cloudflare.com"
    ]
}

Questions about bullverse.ws

Is bullverse.ws legit?

No. PhishDestroy classifies bullverse.ws as a MetaMask impersonation page (risk: critical, 95/100); it was first detected on 2026-09-01. VirusTotal: 8/89 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is bullverse.ws safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on bullverse.ws. 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 bullverse.ws?

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 · 2 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
RegistrationExpires Sep 1, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 1, 2026
DOM Analysisanalyzed Oct 9, 2026score 95/1001 brand signal
Submitted URLhttp://bullverse.ws/
Favicon Hash
Observed page title
Bullrun
Automated brand references
MetaMask
TLS Certificate
Issued by Google Trust Services · stored validity ends in 87 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.167.222
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • carlos.ns.cloudflare.com
  • walk.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-09-01 10:10:46
Valid until
2026-11-30 11:09:12
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-10 22:03:00 UTC
Collection source
PhishDestroy collector
Certificate fingerprint17d5f30b706e39a9aa8157210fe0e18f23cf2b582fb424c20e531dad785e3fa4
Certificate names · 2 SANs
  • bullverse.ws
  • *.bullverse.ws

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-22 10:26:26 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:26:26 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:26:26 UTC last content: 2026-10-22 10:26:26 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 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

8 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 8 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
LevelBlue
SOCRadar
VIPRE

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 bullverse.ws · checked Sep 1, 2026

100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
0.77s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.14s
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.

Check for cloaking

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

Page titles differ

alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare

Browser
Bullrun
Crawler
FASTPANEL
bullverse.ws
Saved result
Cloaked / Filtered
Stored observation history24

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 19
  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. VirusTotal · Detection count

    5→Observation retained

  16. VirusTotal · Detection count

    3→5

  17. VirusTotal · Detection count

    2→3

  18. VirusTotal · Detection count

    0→2

  19. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    8/89 engine detections

    View source
  4. Added to PhishDestroy

    bullverse.ws

    View source
  5. URLScan

    Page captured

    View source

Lookalike domains

79 stored lookalike domains

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

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 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.

Official reporting routes

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 bullverse.ws)
  • 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

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.

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/bullverse.ws"
  title="PhishDestroy threat report for bullverse.ws"
  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>