VirusTotal
8 / 89 engine detections
Open reportbullverse.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”
8 / 89 engine detections
Open reportDBL_PHISH
4 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
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.
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.
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.
Stored page, network and scanner observations, grouped by source and observation time.
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"
} |
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"
]
} |
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.
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.
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.
Last checked
Edge-IP reputation is not attributed to this domain.
carlos.ns.cloudflare.comwalk.ns.cloudflare.comLocation describes the IP network.
17d5f30b706e39a9aa8157210fe0e18f23cf2b582fb424c20e531dad785e3fa4bullverse.ws*.bullverse.wsSaved 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 bullverse.ws · checked Sep 1, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
bullverse.ws
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content
content_served
5→Observation retained
3→5
2→3
0→2
Reachable
4 community references
View sourceNo threat flag
View source8/89 engine detections
View sourcebullverse.ws
View sourcePage captured
View source79 stored lookalike domains
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
bullverse.ws)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.