Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
ネットワークセキュリティインテリジェンス Registrar context
Registrar contextTrustname
Stored registration data identifies Trustname / Fewmoretaps OÜ (IANA 4318) as the registrar. PhishDestroy maintains a separate registrar investigation; that material is contextual and is not an independent detection for this domain.
bafowex.com is a suspicious domain on the PhishDestroy blocklist. We have not yet tied it to a specific brand or scheme. PhishDestroy first saw it on 2026-10-07, one week after it was registered. As of 2026-10-19 the site was still online, and visiting it redirects the browser to another destination rather than serving a page of its own.
How the scam works
The domain answers with a redirect, so bafowex.com acts as a gateway rather than the final page. Fresh throwaway domains that forward visitors elsewhere are commonly used in crypto fraud to pass people on to fake trading platforms, wallet-connect prompts or login pages, while keeping the landing site out of view. Whatever the destination turns out to be, the risk comes from what a visitor does there: entering credentials, typing a recovery phrase, approving a wallet transaction or sending a deposit.
Evidence
On 2026-10-19, VirusTotal showed 6 of 92 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That is a minority of engines, but these are six independent vendors reaching the same conclusion about a domain only a few weeks old. The domain also appears in three AlienVault OTX threat pulses, which means other researchers have filed it alongside related malicious indicators. Apart from PhishDestroy, no other blocklist lists it so far.
Infrastructure
The domain was registered on 2026-09-30 through Fewmoretaps OU, trading as Trustname.com, and PhishDestroy detected it seven days later. That short gap fits a domain set up for immediate use rather than one with an established history. Traffic goes through Cloudflare's network (AS13335, United States), so the public address belongs to the proxy and does not reveal the real server behind the redirect.
What to do
Do not open bafowex.com or follow wherever it sends you. If you entered a password on the destination page, change it everywhere you reused it and turn on app-based two-factor authentication. If you typed a seed phrase or connected and signed with a wallet, treat that wallet as exposed and move your funds to a new one. If you sent money, keep the transaction details and report them to your exchange and local authorities. Security teams should block the domain at DNS and proxy level, watch for redirect chains that start from it, and report it to the registrar and to Cloudflare.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-20 10:06:47 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-20 10:06:47 UTC
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.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(BY)
PhishDestroy Investigation
