amazon-library-support.netlify.app is a free Netlify subdomain on the PhishDestroy blocklist. Its name pairs the Amazon brand with "library support" wording, a combination with no clear legitimate purpose on a third-party hosting platform. PhishDestroy first saw it on 2026-08-31. It has been offline since 2026-09-12 and was still dead at the last check on 2026-10-19, with nothing served at its root.
How the scam works
PhishDestroy has not assigned this site to a specific scheme, and no page content survived to show what it presented. The risk the evidence points to is a brand-themed support page: a visitor arriving from a link or search result sees Amazon's name in the address and is pushed to sign in, share personal or payment details, or contact a fake helpline. Pages like this are built quickly on free hosting and taken down or abandoned within days, which matches this site's short lifespan.
Evidence
When VirusTotal scanned the site on 2026-09-13, 18 of 89 engines marked it malicious. That is a meaningful minority for a short-lived subdomain. The vendors flagging it include BitDefender, ESET, Fortinet, Emsisoft, Criminal IP, alphaMountain.ai, CyRadar and the Vietnamese anti-scam project Chong Lua Dao. Among the lists checked, only PhishDestroy carries it.
Infrastructure
The site sits on Netlify's platform as a subdomain, so no separate domain had to be registered. Anyone can create one in minutes, which makes this setup convenient for disposable pages. Its IP address, 35.157.26.135, falls within Amazon.com, Inc.'s cloud network in Germany. That reflects where Netlify hosts its content, not any connection to Amazon's retail business. It was active for less than two weeks after PhishDestroy first detected it.
What to do
If you entered an Amazon email and password on this site, change that password immediately and enable two-step verification. Review your account's recent orders, saved addresses and payment methods. If you gave card details, ask your bank to block the card, and treat any follow-up calls or messages claiming to be Amazon support as suspect. Defenders should block the full hostname and alert on other Netlify subdomains that combine Amazon branding with support or account terms.
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.
(US)
