PhishDestroy first recorded baltex.exchange on 2026-09-26. Stored VirusTotal result: 16/92 engines flagged. Malicious: 15. Suspicious: 1. Analysis time (as stored): 2026-10-08 00:38 UTC. Retrieved (as stored): 2026-10-21 18:07 UTC. Google Safe Browsing flags it.
Stored VirusTotal result: 16/92 engines flagged. Malicious: 15. Suspicious: 1. Analysis time (as stored): 2026-10-08 00:38 UTC. Retrieved (as stored): 2026-10-21 18:07 UTC. Use caution — do not enter credentials or personal information.
Risk signals
VirusTotal detections: 16/92Google Safe Browsing: threat flag recorded
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded baltex.exchange on 2026-09-26. Stored VirusTotal result: 16/92 engines flagged. Malicious: 15. Suspicious: 1. Analysis time (as stored): 2026-10-08 00:38 UTC. Retrieved (as stored): 2026-10-21 18:07 UTC. Google Safe Browsing flags it. Risk: critical (evidence score 100/100). Registrar: Tucows. Status: Content unavailable. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
baltex.exchange presents itself as "Baltex – Instant Crypto Swaps | Fast & Secure Exchange," a quick coin-swap service aimed at crypto holders who want to trade one token for another without signing up. PhishDestroy classifies it as an impersonation phishing page and first flagged it on 2026-09-26. On 2026-10-19 the site was still online and serving its content.
How the scam works
Instant-swap fakes copy the familiar flow of a real exchanger. The visitor picks a pair, enters an amount and a receiving address, and is shown a deposit address to send coins to. On a fraudulent page, nothing comes back. The "swap" is a one-way transfer to the operators, and on-chain payments cannot be reversed. Pages like this can also collect wallet addresses, email contacts or login details that feed later scams, and they lean on words like "Fast & Secure" to rush people past any doubts.
Evidence
Our classification is backed by outside detections. Google Safe Browsing lists the domain for social engineering, the category browsers use to show a full-page warning. On 2026-10-01, 15 of 91 VirusTotal engines flagged it, including BitDefender, ESET, Fortinet, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF and Google Safe Browsing. Spamhaus DBL lists it as spam, and the domain appears in four AlienVault OTX threat pulses. That means several independent analysts have connected it to malicious activity.
Infrastructure
The domain was registered through Tucows Domains Inc. on 2026-09-17, only nine days before PhishDestroy detected it. That short gap fits a site built for a quick campaign rather than a long-running business. Traffic goes through Cloudflare, with the address located in Canada, so the real origin server is hidden behind the proxy.
What to do
Do not send any coins to a deposit address shown on baltex.exchange. If you already did, record the transaction hash, the amounts and the addresses. Report the theft to your exchange and local police, and ignore anyone who later demands a "fee" to release or recover the funds. If you entered an email address or password, change that password wherever you reused it and turn on two-factor authentication. Security teams should block the domain at DNS and proxy level, add it to mail and web filters, and report it to Cloudflare and Tucows so it can be taken down while it remains live.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Open report Page code check by a separate monitor · 30 / 100 · 2026-09-26 10:20 UTC
This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Heuristic score
30
Analyzed at
2026-09-26T10:20:05Z
Source timestamp
2026-09-26 12:20:05
Technical metadata
PhishDestroy narrative
Narrative generation metadata
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
AI title
baltex.exchange — Baltex Impersonation Phishing
AI description
baltex.exchange is an impersonation phishing page posing as the Baltex instant crypto swap service to steal funds and data from crypto traders.
AI summary
Overview baltex.exchange presents itself as "Baltex – Instant Crypto Swaps | Fast & Secure Exchange," a quick coin-swap service aimed at crypto holders who want to trade one token for another without signing up. PhishDestroy classifies it as an impersonation phishing page and first flagged it on 2026-09-26. On 2026-10-19 the site was still online and serving its content. How the scam works Instant-swap fakes copy the familiar flow of a real exchanger. The visitor picks a pair, enters an amount and a receiving address, and is shown a deposit address to send coins to. On a fraudulent page, nothing comes back. The "swap" is a one-way transfer to the operators, and on-chain payments cannot be reversed. Pages like this can also collect wallet addresses, email contacts or login details that feed later scams, and they lean on words like "Fast & Secure" to rush people past any doubts. Evidence Our classification is backed by outside detections. Google Safe Browsing lists the domain for social engineering, the category browsers use to show a full-page warning. On 2026-10-01, 15 of 91 VirusTotal engines flagged it, including BitDefender, ESET, Fortinet, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF and Google Safe Browsing. Spamhaus DBL lists it as spam, and the domain appears in four AlienVault OTX threat pulses. That means several independent analysts have connected it to malicious activity. Infrastructure The domain was registered through Tucows Domains Inc. on 2026-09-17, only nine days before PhishDestroy detected it. That short gap fits a site built for a quick campaign rather than a long-running business. Traffic goes through Cloudflare, with the address located in Canada, so the real origin server is hidden behind the proxy. What to do Do not send any coins to a deposit address shown on baltex.exchange. If you already did, record the transaction hash, the amounts and the addresses. Report the theft to your exchange and local police, and ignore anyone who later demands a "fee" to release or recover the funds. If you entered an email address or password, change that password wherever you reused it and turn on two-factor authentication. Security teams should block the domain at DNS and proxy level, add it to mail and web filters, and report it to Cloudflare and Tucows so it can be taken down while it remains live. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a0dd0d-f2d7-7134-b6e0-dd5f3c4c17e5/ VirusTotal report: https://www.virustotal.com/gui/domain/baltex.exchange Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=baltex.exchange Archived copy: https://web.archive.org/web/20260926093331/https://baltex.exchange/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
Last: 2026-10-03T01:50:18Z; First: 2026-09-19T15:24:27Z; Changes: 2; Days archived: 3; Scans per day: 0.15; Avg page bytes: 84117
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Questions about baltex.exchange
Is baltex.exchange legit?
PhishDestroy rates baltex.exchange as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-09-26. Stored VirusTotal result: 16/92 engines flagged. Malicious: 15. Suspicious: 1. Analysis time (as stored): 2026-10-08 00:38 UTC. Retrieved (as stored): 2026-10-21 18:07 UTC. Google Safe Browsing flags it. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is baltex.exchange safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on baltex.exchange. A confirmed blockchain transaction cannot be reversed.
What should I do if I used baltex.exchange?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
Issued by Let's Encrypt / YE1· stored validity ends in 41 days
Social preview cardbaltex.exchange: Phishing site — Flagged by Google Safe Browsing, 15/91 VirusTotal engines. PhishDestroy risk score 100/100 (critical).v f206d79a4f36
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 Detected2026-09-26
DOM Analysisanalyzed 2026-10-09score 100/10054 brand signals
IoC Extractionscanned 2026-09-270 wallet · 1 Telegram IoC
Submitted URLhttps://baltex.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
Shared CDN edge
Resolved IP
104.21.4.253
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
bailey.ns.cloudflare.com
dylan.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE1
Valid from
2026-10-05 06:06:49
Valid until
2027-01-03 06:06:48
Hostname match
Yes
Validity
Within stored validity dates
Collection time
2026-10-11 04:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprintfe81230838cdcb1b172e5e94aca8de8939d66a624f61a71aa680007a906dd626Certificate names · 2 SANs
*.baltex.exchange
baltex.exchange
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAIN
RDAP registration
Observed timelinelast reachable: 2026-10-22 10:34 UTClast content: 2026-10-22 10:34 UTCcurrent episode first observed: 2026-10-22 20:55 UTCobserved RIP window: 2026-10-22 10:34 UTC → 2026-10-22 20:55 UTC · 10.35hmidpoint estimate ≈ 2026-10-22 15:44 UTC · precision medium · 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.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 02:32 UTC.
Recorded events: 19. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Time to First Unavailability
Hours from detection to the first unavailable observation: 630
Recorded activity
7 entries
Lifecycle
Domain registered
Added to PhishDestroy+8 d 16 h
First abuse report sent+1 min
VirusTotal analysis with detections+11 d 15 h
Reported 8 d 16 h after registration
AlienVault OTX
5 community references
+20 d 9 h
Google Safe Browsing
Threat flag recorded
+27 h 23 min
VirusTotal
16/92 engine detections
+11 d 15 h
Abuse report sent
PD-20260926-D40D9E · Receipt 72622
compliance@tucows.com
same minute
Wayback Machine
Page archived
+1 min
Added to PhishDestroy
baltex.exchange
same minute
URLScan
Page captured
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches1
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
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.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
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 baltex.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)
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
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 →
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.