Skip to security report
Domain security and threat intelligence
botalpha.exchange favicon

botalpha.exchange

“BOT ALPHA”

Registrar
NameCheap
Resolved IP
144.172.107.221
Registered
Aug 22, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 12/89 Spamhaus DBL: DBL_SPAM Stored blocklist matches: 2 URLQuery threat systems: 1 alert Automated brand label: MetaMask
OTX: 4 refs Sep 1, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 12. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
URLQuery
threat alerts
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 12 / 89 · OTX 4 references 9 sources

VirusTotal

12 / 89 engine detections

Open report

URLQuery

1 threat-system alert

Open report

Gridinsoft

49/100

Spamhaus DBL

DBL_SPAM

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.

Network Security Intelligence
Threat Detection Systems 1 alert
Detection System Indicator Verdict Alert
DNS4EU botalpha.exchange malicious Sinkholed

Analysis

Critical
VirusTotal
12 / 89
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

botalpha.exchange is an impersonation phishing site that presented itself as "BOT ALPHA" on an exchange-themed domain. It was aimed at crypto users drawn in by a trading-bot or exchange brand. PhishDestroy first flagged it on 2026-09-01. The site has been offline since 2026-09-29 and was still unreachable when last checked on 2026-10-19.

How the scam works

Impersonation pages like this borrow a recognisable name, here "BOT ALPHA", and pair it with a convincing domain so visitors believe they are on the genuine platform. The aim is to get victims to hand over something of value. That can be login details, a wallet connection, or deposits into what looks like a trading account but is controlled by the operators. Money or credentials given to such a page go straight to the scammers, and on-chain transfers cannot be reversed.

Evidence

Twelve of 89 VirusTotal engines flagged the domain as of 2026-09-12. The vendors include Kaspersky, BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. Crypto-specific defences reached the same verdict: MetaMask's blocklist and SEAL both list it alongside PhishDestroy, so many wallet users would see a warning before interacting. Spamhaus carries it in its domain blocklist as spam. Four AlienVault OTX threat pulses reference it, which shows other researchers tracked it independently.

Infrastructure

The domain was registered through NameCheap, Inc. on 2026-08-22, just ten days before PhishDestroy detected it. That short gap is typical of throwaway phishing domains set up for a single campaign. It was hosted on RouterHosting LLC in the United States and used a free Let's Encrypt certificate. The padlock in the browser therefore said nothing about the site's legitimacy. It stayed live for about four weeks after detection before going dark.

What to do

If you deposited funds on this site, assume they are gone. Ignore any later request for "fees" or "taxes" to unlock a withdrawal, since paying more never recovers the money. If you entered a password or seed phrase, change the password everywhere it was reused and turn on 2FA. If you shared a seed phrase, move your assets to a fresh wallet immediately. If you connected a wallet, review and revoke any token approvals you granted. Defenders should block the domain and IP 144.172.107.221, and watch for lookalike BOT ALPHA domains registered on other extensions.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 3 captures

Observed page title
BOT ALPHA
Automated brand references
MetaMask
TLS Certificate
Issued by Let's Encrypt · stored validity ends in 81 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Sep 2, 2026
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar NameCheap (Unknown)
RegistrationCreated Aug 22, 2026 (59d · New) — Expires Aug 22, 2027
Time to First Unavailability 27 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 1, 2026
Submitted URLhttp://botalpha.exchange/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
144.172.107.221
Network ASN
AS14956
Organization
FranTech Solutions
Observed location
Las Vegas, US
Server header
Microsoft-IIS/10.0

Nameservers 1

  • ns2.botalpha.exchange

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-08-24 03:49:35
Valid until
2026-11-22 03:49:34
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-01 22:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint893e6f5ea664f1848c7738e9615c0f0f3a1c36a19a387fa675b2811f3221ae34
Certificate names · 1 SANs
  • www.botalpha.exchange

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.botalpha.exchangeDomain record

The original observation time is not recorded for these hostnames.

Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 10 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
SOCRadar
Sophos
VIPRE
Webroot

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 botalpha.exchange · checked Sep 1, 2026

59
Needs Work
Performance
FCP
6.26s
First Contentful Paint
LCP
13.36s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
6.36s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

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.

botalpha.exchange
Saved result
Cloaked / Filtered
Stored observation history3

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

    Reachable→Unavailable

  2. VirusTotal · Detection count

    0→3

  3. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    12/89 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Abuse report sent

    PD-20260901-9267E6

    abuse@namecheap.com
  5. Added to PhishDestroy

    botalpha.exchange

    View source
  6. 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

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260901-9267E6 Recipient: abuse@namecheap.com
PDF notice generated Notice text archived (289 chars)
Abuse notice text as sent to the provider
Registrar: Namecheap Inc (United States)
Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Deep Analysis
Help & reporting

Were You Affected by This Site?

8 evidence signal groups linked 1 stored notification records Content unavailable
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 botalpha.exchange)
  • 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/botalpha.exchange"
  title="PhishDestroy threat report for botalpha.exchange"
  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>