avano.finance is a high-risk crypto-drainer phishing domain that impersonates the Backpack cryptocurrency wallet brand and deploys the Angel Drainer kit to steal funds from connected wallets. The site, which presented itself as an 'AI Trading Website,' is currently taken offline but was actively used to execute wallet-draining attacks via malicious WalletConnect prompts. Users searching whether avano.finance is safe or a scam should treat it as confirmed malicious.
Technical indicators confirm the threat: 3 of 95 VirusTotal security vendors flagged avano.finance, including CRDF, Gridinsoft (which assigned a trust score of 0/100), and SOCRadar. The domain appears on 2 security blocklists (PhishDestroy and ScamSniffer) and is registered through HOSTINGER operations, UAB. It resolves to the IPv6 address 2a02:4780:44:b5d1:2c6e:1824:55c:37fd, hosted on AS47583 (Hostinger International Limited) in Germany. No SSL certificate was observed, and the nameservers are ns1.dns-parking.com and ns2.dns-parking.com. Google Safe Browsing has not flagged the domain.
Victims of avano.finance or similar crypto-drainer phishing sites should immediately revoke all token approvals using a tool like Revoke.cash or Etherscan's token approval checker. Funds should be moved to a new, secure wallet to prevent further unauthorized transactions. If credentials or wallet phrases were exposed, users must assume compromise and monitor accounts for fraud. Report the domain to platforms like ScamAdviser, PhishTank, or the impersonated brand (Backpack) to aid in takedown efforts.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='avano.finance', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
DOM Analysisanalyzed 2026年4月23日score 25/1004 brand signals
Submitted URLhttps://avano.finance/
ICANN OVERSIGHT
认证和 RAA 背景
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:14:09 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-05-18 02:39:32 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-18 02:39:32 UTC → 2026-09-30 16:14:55 UTC · 3,253.59hmidpoint estimate ≈ 2026-07-24 21:27:13 UTC · precision very low · 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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
您的加密货币交易所 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
加密货币诈骗通常是如何运作的？
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
恶意批准 — “连接钱包”的提示会使攻击者获得无限的代币消费权限
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
(LT)
