Skip to security report
Domain security and threat intelligence
zz.aavu.exchange favicon

zz.aavu.exchange

“Aave Dashboard”

Resolved IP
172.67.179.240
Threat verdict Critical
Availability Content unavailable Content was unavailable in the latest observation Observed
Source: HTTP probe
VirusTotal detections: 1/95 Brand impersonation: Aave
Sep 18, 2025 Aave CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 1. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
VirusTotal
1 det.
URLScan
URLScan
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed

Source evidence

5 sources

VirusTotal

1 / 95

Report

OTX

no community references

Report

CF Radar

provider verdict: clean

Report

URLScan capture

stored report

Stored URLScan capture preview
Report

Google Safe Browsing

Checked; no threat flag recorded

Report

Evidence Summary

Critical
VirusTotal
1/95
URLScan
Stored capture

The domain zz.aavu.exchange, impersonating the brand Aave, has a high threat score of 70/100 and is currently down. It has been flagged as malicious by one out of 95 security vendors, with SOCRadar being the notable vendor. The domain is listed on one public blocklist, while Google Safe Browsing has not flagged it. This domain is associated with the Angel Drainer, indicating a specific type of crypto scam.

Registrar information is not available, suggesting potential use of privacy protection or that it has been scrubbed. The hosting IP is 172.67.179.240, and the domain was first seen on 2025-09-18. Given the high threat level, block the domain at the perimeter and flag the IP as an indicator of compromise.

Detection-evasion analysis

Cloaking and traffic-distribution check

Not observed No cloaking was observed in the stored scan

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan

Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='zz.aavu.exchange', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting

Stored Capture · 2 captures

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Time to First Unavailability 157 days
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 DetectedSep 18, 2025
DOM Analysisanalyzed Mar 24, 2026score 20/1002 brand signals
Submitted URLhttps://zz.aavu.exchange/
Page Title
Aave Dashboard
Impersonates
Aave Ethereum

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.179.240
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

viewdns.info · 172.67.179.240rapiddns.io

Latest Classified Outcome 2026-10-10 20:20:48 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-11 01:11:04 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-04-08 08:45:00 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-04-08 08:45:00 UTC → 2026-09-30 16:14:55 UTC · 4,207.50h midpoint estimate ≈ 2026-07-05 00:29:57 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 95 security vendors flagged this domain
View on VT
Last analyzed
SOCRadar

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
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.
  1. Cloudflare Radar Scan 2026-03-07 16:50:08 UTC
    Cloudflare Radar scan registered: View Radar report.

Threat Response Pipeline

Discovery
Analysis
Monitoring

11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
zz.aavu.exchange detected and queued for full analysis
Sep 18, 2025
URLScan.io Capture
Stored URLScan report with capture artifacts
Mar 5, 2026
Cloudflare Radar Report
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.
VirusTotal
1/95 recorded on VirusTotal
Feb 23, 2026
Drainer Identified
Angel Drainer wallet drainer — impersonating Aave
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Mar 5, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 12, 2026
Cloudflare Radar Scan
Scanned with Cloudflare Radar; network analysis completed.
Mar 7, 2026
DestroyList Published
Sep 18, 2025
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Feb 23, 2026
Time to First Unavailability
3778 hours elapsed from detection to the first unavailable observation.
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Lookalike domains

95 stored lookalike domains

aavef.com addition Internal report xn--ave-ila.com homoglyph Internal report 1ave.com replacement a1ve.com replacement a2ve.com replacement aa.ve.com subdomain aaev.com transposition aage.com replacement aav4.com replacement aavi.com vowel-swap aavo.com vowel-swap aavr.com replacement
Show all (83)
aavs.com replacement aavw.com replacement aove.com vowel-swap auve.com vowel-swap avae.com transposition awve.com replacement ayve.com replacement azve.com replacement oave.com vowel-swap save.com replacement uave.com vowel-swap wave.com replacement 1aave.com insertion 2ave.com replacement a-ave.com hyphenation aa6e.com bitsquatting aaave.com repetition aabe.com replacement aace.com replacement aacve.com insertion aare.com bitsquatting aate.com bitsquatting aauc.com homoglyph aaue.com homoglyph aav.com omission aav3.com replacement aava.com bitsquatting aavbe.com insertion aavc.com homoglyph aavce.com insertion aavd.com bitsquatting aavec.com addition aaved.com addition aavee.com addition aaveg.com addition aavek.com addition aavel.com addition aaven.com addition aaveo.com addition aaveq.com addition aaver.com addition aaves.com addition aavet.com addition aavex.com addition aavey.com addition aavg.com bitsquatting aavm.com bitsquatting aavu.com bitsquatting aavve.com repetition aavz.com replacement aawe.com bitsquatting acve.com bitsquatting aeve.com bitsquatting aive.com bitsquatting aqave.com insertion aqve.com bitsquatting asave.com insertion asve.com replacement ave.com omission awave.com insertion ayave.com insertion azave.com insertion cave.com bitsquatting eave.com bitsquatting iave.com bitsquatting qaave.com insertion saave.com insertion waave.com insertion xn--80aap9w.com cyrillic xn--aa-g7r68c.com homoglyph xn--aa-g7r83g.com homoglyph xn--aav-5qa.com homoglyph xn--aav-mra.com homoglyph xn--ae-dla019z.com homoglyph xn--ae-dla4955b.com homoglyph xn--ae-dla6031a.com homoglyph xn--ae-e5s275e.com homoglyph xn--ae-tfb535y.com homoglyph yaave.com insertion yave.com replacement zaave.com insertion aavea.com addition aavew.com addition

Community reports

Reported by 1 community member, first seen Sep 18, 2025

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

4 evidence signal groups linked 0 reports recorded Content unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If a wallet, seed phrase, or account was exposed, report the incident immediately. Revoke approvals and move remaining assets to a new wallet created on a trusted device.

Europol
Find the official reporting channel for your EU country
National police directory
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Guaranteed crypto recovery is a fraud indicator. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing

Recommendations & Advice for Victims

An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with zz.aavu.exchange — act now.

What should I do immediately?
Urgent
  • Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
  • Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines

According to the FBI, the most important details are transaction data:

  • Cryptocurrency addresses — scammer's wallet (e.g., 0x5856...35985)
  • Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
  • Transaction ID (hash) — the unique blockchain transaction identifier
  • 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 zz.aavu.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)
  • Europol — European cybercrime reporting (EU)
  • Chainabuse — flag scam wallets across exchanges & platforms
  • Your crypto exchange — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
  • 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 crypto scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
  • 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
  • Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
  • Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Read every approval — verify permissions before signing. Reject unlimited approvals
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/zz.aavu.exchange"
  title="PhishDestroy threat report for zz.aavu.exchange"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>