VirusTotal
16 / 89 engine detections
Open reportbuorex.win is a crypto casino scam detected by PhishDestroy on 2026-09-06. Risk: critical (100/100). Status: Content unavailable. Hosting: CLOUDFLARENET - Cloudflare, Inc., US. VirusTotal: 16/89 engines flag it. Do not enter credentials or connect a wallet.
“Buorex: Most Popular Online Crypto Casino Based on Blockchain”
16 / 89 engine detections
Open reportMalicious
Open report4 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
buorex.win presented itself as "Buorex: Most Popular Online Crypto Casino Based on Blockchain", a gambling site pitched at cryptocurrency holders. PhishDestroy classifies it as a fraudulent gambling operation and first flagged it on 2026-09-06. The site went offline on 2026-09-11, and as of 2026-10-19 the domain no longer resolves.
Fake crypto casinos borrow the look and vocabulary of legitimate betting platforms, such as "provably fair" blockchain games, instant payouts and large welcome bonuses, to persuade visitors to deposit coins. Balances on the site are numbers the operator controls. Players may see early wins, but withdrawals stall behind fees, wagering requirements or account "verification" that never ends. The "most popular" claim in the page title is a credibility hook for a brand nobody has heard of. Victims lose whatever they deposited and anything they paid to unlock a withdrawal.
On 2026-09-08, 16 of 89 VirusTotal engines flagged the domain, including BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, CyRadar and the Vietnamese anti-scam project Chong Lua Dao. That is a broad spread of independent vendors for a site that was only days old. urlscan.io rated the page malicious and matched it to its generic crypto and crypto-scam patterns. Beyond PhishDestroy, the domain is blocked by MetaMask and SEAL, and it appears in four AlienVault OTX threat pulses.
The domain was registered on 2026-03-11, about six months before PhishDestroy detected it, so it either sat idle or ran without attracting attention for most of that period. It was served through Cloudflare (CLOUDFLARENET, US) at 104.21.58.96. This means the IP belongs to Cloudflare's shared network and does not reveal the operator's real server. The site lasted only five days after detection before going dark.
If you deposited funds on buorex.win, do not send any further payment labelled as a withdrawal, tax or unlock fee. That money will not be returned either. Record your transaction hashes and the deposit addresses you sent to, report them to the exchange you sent from, and file a report with local cybercrime authorities. If you connected a wallet to the site, review and revoke any token approvals it requested. Ignore anyone who contacts you offering to recover the funds, because recovery offers are a common follow-up scam. Defenders should block the domain and watch for the same casino branding reappearing on new domains.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a074ea-3143-73a8-9303-b151b2fb1be7 |
|---|---|
| Final url | https://buorex.win/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://buorex.win/",
"from": "http://buorex.win/",
"status": 307
}
] |
| Ip | 104.21.58.96 |
| Contacted domains | [
"static.ads-twitter.com",
"connect.facebook.net",
"static.cloudflareinsights.com"
] |
| Contacted IP addresses | [
"146.75.28.157",
"57.144.70.128",
"104.16.79.73",
"104.21.58.96"
] |
| Asns | [
"54113",
"32934",
"13335"
] |
| Countries | [
"US"
] |
| Document hash | 2b39b82ae49a09a798b086e51a87331dbf9af0078223f3d0914a381c6b272f8b |
| Script hashes | [
"d872665bddf3245bfbdfa8b534199f4e10ac5e4cf2952b4c8adaef5ccfafa881",
"e5b9e2570593ab1e59ae6a397baec8491e4c3d5e4628aa1439940ac0e2aee2fe",
"d3844f2db215d099728ef83a3b5cb3cb82279b669b231f54d2cdbbd958949f1d",
"90a949795e63ad10200d2f57df2706979fd66bd412caea2130a9c707e21c5d5b",
"dccd0125f7ca7c6c5f3f8ae7d813743257cb55899fcab2d63b70fdf06b2a05e2",
"4974bda3ce7194ae592697daaccd424e6e8e231bf15187182bf4d16522e9bffb",
"a80e2f887fe98f5dd1f607d951147f5de620031519c6419ed1fb86e7b6621686",
"350d0346dafe74b5900d0d7611ce83ebaa276b6ad5c2aaaddb31d84d925d768e",
"3513d69dd757c29044eb92ab6a908ba6755e0845c38105ab2e196b0c75b96583",
"237ff25124f0ca73e06c9e1d59caadd016273fa9b5b6bf211c991cc8d34d1b92"
] |
| Globals | [
"__next_f",
"__cfBeacon",
"webpackChunk_N_E",
"next",
"_N_E_STYLE_LOAD",
"__core-js_shared__",
"HowlerGlobal",
"Howler",
"Howl",
"Sound",
"fbq",
"_fbq",
"twq",
"loadTtq",
"mb_setLanguage",
"twttr",
"mb_lang",
"mb_openLangModal"
] |
| Tls | {
"san": [
"*.buorex.win",
"buorex.win"
],
"cipher": "AES_128_GCM",
"issuer": "YE2",
"subject": "buorex.win",
"protocol": "TLS 1.3",
"valid_to": "2026-12-04T00:07:00Z",
"valid_from": "2026-09-05T00:07:01Z"
} |
| Domain age days | 178 |
| Apex age days | 178 |
| Tls age days | 1 |
| Tls valid days | 89 |
| Requests | 81 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 100,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"genericcrypto",
"cryptoscam"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"Generic Crypto",
"Crypto Scam"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=UTF-8"
} |
Observed: · Retrieved:
| Uuid | 457bf8e4-a047-4c32-8986-0e2f26983e0d |
|---|---|
| Final url | https://buorex.win/ |
| Status | 200 |
| Redirected | https-only |
| History | [
{
"url": "http://buorex.win/",
"status": 307
},
{
"url": "https://buorex.win/",
"status": 200
}
] |
| DOM structure hash | eb8349f8ea987fb83e1c8a6c0fb1ccc20875e1798e21232ae18d2813d36b20cb |
| Document hash | 2b39b82ae49a09a798b086e51a87331dbf9af0078223f3d0914a381c6b272f8b |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "buorex.win",
"type": "A",
"value": "104.21.58.96"
},
{
"name": "buorex.win",
"type": "A",
"value": "172.67.203.39"
}
] |
| Dnssec valid | false |
| Ip | 104.21.58.96 |
| Registration record | {
"registrar": "Gname.com Pte. Ltd.",
"created": "2026-03-11T19:22:59Z",
"updated": "2026-05-10T19:23:03Z",
"expires": "2027-03-11T19:22:59Z",
"nameservers": [
"wells.ns.cloudflare.com",
"aron.ns.cloudflare.com"
]
} |
No. PhishDestroy classifies buorex.win as a crypto casino scam (risk: critical, 100/100); it was first detected on 2026-09-06. VirusTotal: 16/89 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on buorex.win. 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.
aron.ns.cloudflare.comwells.ns.cloudflare.comLocation describes the IP network.
*.buorex.winbuorex.winSaved 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 buorex.win · checked Sep 6, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Reachable→Unavailable
2→16
0→2
Reachable
4 community references
View sourceNo threat flag
View source16/89 engine detections
View sourcebuorex.win
View sourcePage captured
View source1 community report
CategoryOTHER
Suspected abuse at buorex.win
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
buorex.win
“Suspected abuse at buorex.win”
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 ↗
buorex.win)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.