ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is domainabuse@tucows.com.
The latest stored availability evidence still shows the domain reachable; 25 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
bvousc.com is a phishing page that impersonates Amazon under the title "Amazon Refund Check". It targets Amazon customers who are told they are owed money back. PhishDestroy first flagged it on 2026-09-25. As of 2026-10-19 the domain itself was still alive, but DNS for its phishing content was inactive, so the lure may be dormant rather than gone.
How the scam works
Refund lures work because they promise a payout instead of demanding one. A message tells the target that an Amazon refund is waiting and links to a page styled as a refund check. To "claim" it, the visitor is asked to sign in with their Amazon credentials and often to confirm card or bank details so the money can be "returned". Whatever is typed goes to the operators. Victims can lose control of their Amazon account and any stored payment methods, and their card details can be misused.
Evidence
On 2026-10-03, 16 of 91 VirusTotal engines classified the domain as malicious, among them ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Emsisoft, Gridinsoft, CRDF and alphaMountain.ai. That is broad agreement across unrelated vendors. urlscan.io returned a malicious verdict and independently recognised Amazon branding on the page. Spamhaus lists the domain in its DBL as a spam domain, which fits a lure distributed by bulk messaging. The domain also appears in five AlienVault OTX threat pulses.
Infrastructure
The domain was registered through TUCOWS.COM, CO. on 2026-09-21, only four days before PhishDestroy detected it. That short gap is typical of throwaway domains set up for a single campaign. It is hosted on the AVA HOST SRL network in Moldova. Its TLS certificate comes from TrustAsia's LiteSSL CA, so the browser padlock only shows that the connection is encrypted. It says nothing about whether the site is really Amazon.
What to do
If you entered your Amazon login here, change that password at once, and change it anywhere you reused it. Turn on two-step verification and review your account for unfamiliar orders, addresses or saved cards. If you gave card or bank details, call your bank to block the card and dispute any charges. Treat any follow-up calls or messages about your "refund" as part of the same scam. Defenders should block bvousc.com and 194.102.104.212 at mail and web gateways and search inbound mail for Amazon refund-themed messages pointing to this domain.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-20 10:07:03 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-02 10:11:28 UTClast content: 2026-10-02 10:11:28 UTCcurrent episode first observed: 2026-10-03 16:16:30 UTCobserved RIP window: 2026-10-02 10:11:28 UTC → 2026-10-03 16:16:30 UTC · 30.08hmidpoint estimate ≈ 2026-10-03 01:13:59 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.
技术 · 5 identified
V
Vue.js
JavaScript frameworks
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — 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.
(KN)
