Skip to security report
Domain security and threat intelligence
auth-bitbuy--cdn---newzenler.webflow.io favicon

auth-bitbuy--cdn---newzenler.webflow.io

In short

auth-bitbuy--cdn---newzenler.webflow.io is a phishing page detected by PhishDestroy on 2026-09-11. Risk: critical (100/100). Registrar: Webflow. Status: Content unavailable. Hosting: Cloudflare, Inc. VirusTotal: 17/89 engines flag it. Google Safe Browsing flags it. PhishDestroy detected it 7 days before Google Safe Browsing flagged it (in PhishDestroy’s checks). Do not enter credentials or connect a wallet.

“Log In | Bitbuy”

Registrar
Webflow
Resolved IP
104.18.36.248
Registered
May 8, 2013
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 17/89 Stored blocklist matches: 2 Scam type: Impersonation Google Safe Browsing: threat flag recorded
Sep 11, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 17. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Source evidenceVirusTotal 17 / 89 · Google Safe Browsing: flagged 6 sources

VirusTotal

17 / 89 engine detections

Open report

Google Safe Browsing

Threat flag recorded

Open report

OTX

no community references

Open report

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

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing

Analysis

Critical
VirusTotal
17 / 89
Page captures
2

PhishDestroy threat report

Overview

This Webflow-hosted page impersonated Bitbuy, the Canadian cryptocurrency exchange, and carried the title "Log In | Bitbuy" to pass as the real sign-in screen. Its long, cluttered subdomain mixes "auth", "bitbuy" and "cdn" so that a quick glance suggests official authentication infrastructure. PhishDestroy first saw it on 2026-09-11. It has been offline since 2026-09-19 and still served no content at its last check on 2026-10-19.

How the scam works

Victims usually arrive through a link in an email, text message or ad warning about their Bitbuy account. They land on a page that copies the exchange's login form. Anything typed there, including email, password and often a one-time 2FA code, goes to the operators instead of Bitbuy. With a live session, attackers can log in, change security settings and withdraw the victim's crypto or fiat balance before the owner notices.

Evidence

Seventeen of 89 VirusTotal engines flagged the page when it was checked on 2026-09-20. The vendors include crypto-focused ChainPatrol alongside BitDefender, ESET, Emsisoft, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai and CyRadar. Google Safe Browsing classifies it as social engineering, which triggers warnings in mainstream browsers. MetaMask and SEAL list it next to PhishDestroy, so wallet users and the security community have independently confirmed the verdict.

Infrastructure

Rather than registering its own domain, the operator built the page on a free Webflow subdomain. This lets a phishing page go live in minutes and borrow the trust of a well-known platform. Traffic was served through Cloudflare's network with a location in Canada, matching Bitbuy's home market. The site lasted about eight days after PhishDestroy first saw it, which is typical of disposable pages on site-builder platforms.

What to do

If you entered your Bitbuy login on this page, change your password immediately through the official Bitbuy app or a bookmarked address. Reset your 2FA, review recent logins and withdrawals, and contact Bitbuy support to lock the account if you see anything unfamiliar. Change the password anywhere you reused it, and watch for follow-up messages pretending to be Bitbuy support. Defenders should block lookalike Webflow subdomains that combine exchange brand names with words like "auth" or "cdn", and report new instances to Webflow and the targeted brand.

Collected source details

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

URLScan · 2026-09-11T09:53:52Z

Observed: · Retrieved:

Uuid
01a08fe3-2cb5-73aa-8464-b1b7d35b90cf
Final url
https://auth-bitbuy--cdn---newzenler.webflow.io/
Status
200
Ip
172.64.151.8
Contacted domains
[
    "cdn.prod.website-files.com",
    "d3e54v103j8qbb.cloudfront.net"
]
Contacted IP addresses
[
    "13.226.247.129",
    "104.18.160.117",
    "172.64.151.8"
]
Asns
[
    "16509",
    "13335"
]
Countries
[
    "US"
]
Linked domains
[
    "biby-buy.xyz",
    "webflow.com"
]
Document hash
324dd713ea15c10ca87f999499481295023b5e56b19f6f950cdb13db13afb8bf
Globals
[
    "$",
    "jQuery",
    "tram",
    "Webflow"
]
Tls
{
    "san": [
        "webflow.io",
        "*.webflow.io"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "webflow.io",
    "protocol": "QUIC",
    "valid_to": "2026-10-23T03:21:05Z",
    "valid_from": "2026-07-25T02:21:21Z"
}
Domain age days
0
Apex age days
0
Tls age days
48
Tls valid days
90
Requests
8
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "content-security-policy": "frame-ancestors 'self' https://*.webflow.com http://*.webflow.com http://*.webflow.io http://webflow.com https://webflow.com"
}
Cloudflare Radar · 2026-09-18T18:11:47Z

Observed: · Retrieved:

Uuid
ef57fac4-a783-47db-a617-561d0721d099
Final url
https://auth-bitbuy--cdn---newzenler.webflow.io/
Status
404
Redirected
https-only
History
[
    {
        "url": "http://auth-bitbuy--cdn---newzenler.webflow.io/",
        "status": 307
    },
    {
        "url": "https://auth-bitbuy--cdn---newzenler.webflow.io/",
        "status": 404
    }
]
DOM structure hash
4932075438459d054af6b75a0d6585b123ae775f36579c095159b2af33360488
Document hash
90c032f35272ba1a7aa93027ab635e6610d4f24cf9e53c0624d00f065d7c7e7d
Url risks
[
    "Phishing"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "auth-bitbuy--cdn---newzenler.webflow.io",
        "type": "A",
        "value": "104.18.36.248"
    },
    {
        "name": "auth-bitbuy--cdn---newzenler.webflow.io",
        "type": "A",
        "value": "172.64.151.8"
    },
    {
        "name": "auth-bitbuy--cdn---newzenler.webflow.io",
        "type": "AAAA",
        "value": "2a06:98c1:3102::ac40:9708"
    },
    {
        "name": "auth-bitbuy--cdn---newzenler.webflow.io",
        "type": "AAAA",
        "value": "2a06:98c1:3105::6812:24f8"
    }
]
Dnssec valid
false
Ip
104.18.36.248
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2013-05-08T02:20:57Z",
    "updated": "2026-08-12T04:04:30Z",
    "expires": "2028-05-08T02:20:57Z",
    "nameservers": [
        "lamar.ns.cloudflare.com",
        "journey.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-09-12T00:16:25Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 42,
    "malicious": 17,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "BitDefender": "phishing",
    "ChainPatrol": "malicious",
    "alphaMountain.ai": "phishing",
    "Google Safe Browsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "web hosting"
}
Registrar
MarkMonitor Inc.
Created
2013-05-08T02:20:57Z
Expires
2028-05-08T02:20:57Z
Updated
2026-08-12T04:04:30Z
First seen
2026-09-11T09:48:31Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a06:98c1:3105::6812:24f8"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a06:98c1:3102::ac40:9708"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.18.36.248"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.64.151.8"
    }
]
Dns at
2026-09-12T00:16:49Z
Jarm
27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "webflow.io",
        "*.webflow.io"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "7e5a9322f440be460e62bc877c41833c",
    "sha256": "a4ffdefa8d99689893e2aafdf9588b6f8f2f8ec47698ea534dbfa409dbbde19d",
    "subject": "webflow.io",
    "valid_to": "2026-10-23T03:21:05Z",
    "valid_from": "2026-07-25T02:21:21Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2013-05-08T02:20:57Z",
    "updated": "2025-02-25T20:53:31Z",
    "expires": "2028-05-08T02:20:57Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "journey.ns.cloudflare.com",
        "lamar.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}

Questions about auth-bitbuy--cdn---newzenler.webflow.io

Is auth-bitbuy--cdn---newzenler.webflow.io legit?

No. PhishDestroy classifies auth-bitbuy--cdn---newzenler.webflow.io as a phishing page (risk: critical, 100/100); it was first detected on 2026-09-11. VirusTotal: 17/89 engines flag it. Google Safe Browsing flags it. PhishDestroy detected it 7 days before Google Safe Browsing flagged it (in PhishDestroy’s checks). Treat the site as unsafe.

Is auth-bitbuy--cdn---newzenler.webflow.io safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on auth-bitbuy--cdn---newzenler.webflow.io. 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 auth-bitbuy--cdn---newzenler.webflow.io?

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 ↗
Google Safe Browsing Flagged Social engineering checked Sep 20, 2026
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Webflow US(US)
Registration (base domain)webflow.io · Created May 8, 2013 — Expires May 8, 2028
HTTP Status404 Not Found
Time to First Unavailability 8 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 11, 2026
Observed page title
Log In | Bitbuy
TLS Certificate
Issued by Google Trust Services / WE1

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • journey.ns.cloudflare.com
  • lamar.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-07-25 02:21:21
Valid until
2026-10-23 03:21:05
Hostname coverage
Certificate hostname mismatch
Validity
Validity ends today in stored record
Collection time
2026-09-18 19:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta4ffdefa8d99689893e2aafdf9588b6f8f2f8ec47698ea534dbfa409dbbde19d
Certificate names · 1 SAN
  • webflow.io

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-23 01:25:56 UTC

Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Stale Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-10-23 01:25:56 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-11 10:28:08 UTC current episode first observed: 2026-10-01 01:52:48 UTC observed RIP window: 2026-09-11 10:28:08 UTC → 2026-10-01 01:52:48 UTC · 471.41h midpoint estimate ≈ 2026-09-21 06:10:28 UTC · precision low · basis bounded
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

17 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 13 detections
ChainPatrol
alphaMountain.ai
BitDefender
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Kaspersky
LevelBlue
Lionic
Netcraft
Sophos
VIPRE
Webroot
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
471.41
Estimate basis
Bounded by observations
Estimate precision
Low

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

http_other: raw=http_404; http=404; via=http_proxy; server=cloudflare

Browser
Log In | Bitbuy
Crawler
404 - Page not found
auth-bitbuy--cdn---newzenler.webflow.io
Saved result
Cloaked / Filtered
Stored observation history14

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→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  4. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  5. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

Earlier observations 9
  1. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  4. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  5. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  6. VirusTotal · Detection count

    13→17

  7. Availability monitor · Recorded state

    Reachable→Unavailable

  8. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  9. Availability monitor · First collection record

    Reachable

Recorded activity

3 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. VirusTotal

    17/89 engine detections

    View source
  3. Added to PhishDestroy

    auth-bitbuy--cdn---newzenler.webflow.io

    View source

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Content unavailable

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 auth-bitbuy--cdn---newzenler.webflow.io)
  • 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/auth-bitbuy--cdn---newzenler.webflow.io"
  title="PhishDestroy threat report for auth-bitbuy--cdn---newzenler.webflow.io"
  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>