Analysis of www.aavev4.com shows a confirmed brand‑impersonation infrastructure targeting the Aave cryptocurrency platform. The domain was registered on September 13, 2025 through Dominet (HK) Limited and resolves to the IPv4 address 110.238.104.176, which is assigned to AS136907 HUAWEI CLOUDS in Singapore. The hosting environment serves content over Nginx with HTTP/3 enabled, enforces HSTS, and runs a Vue.js front‑end. The site presented the page title "AAVE V4" and was classified as a crypto scam, indicating an attempt to lure victims into fraudulent Aave‑related transactions.
TLS was provided by a Let’s Encrypt certificate (R13), confirming the presence of HTTPS at the time of observation. Security telemetry shows that one of ninety‑five VirusTotal scanners flagged the domain, and it appears on a single external blocklist. The phishing‑specific blocklist PhishDestroy has already listed the domain, and the current operational status is offline, suggesting the site has been taken down or is temporarily inactive.
Defenders should continue to block the domain and its associated IP address at perimeter and endpoint controls, monitor for any re‑registration of the same name or similar variations, and add the observed nameservers (ns7.alidns.com, ns8.alidns.com) to threat‑intel feeds. Given the elevated risk rating, security teams should also audit internal logs for any prior connections to the domain or IP, and consider issuing user awareness alerts about unsolicited Aave‑related communications that reference the "AAVE V4" branding. Ongoing surveillance of the hosting ASN and related HUAWEI CLOUDS assets is recommended to detect potential re‑use of the infrastructure for future crypto‑focused campaigns.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-6647.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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 16, 2025
DOM Analysisanalyzed Jul 27, 2026score 71/1001 brand signal
Submitted URLhttps://www.aavev4.com/
ICANN OVERSIGHT
Accreditation and RAA context
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
110.238.104.176
Network ASN
AS136907
Organization
HUAWEI CLOUDS
Observed location
Singapore, SG
Server header
nginx
Nameservers 2
ns7.alidns.com
ns8.alidns.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / R13
Valid from
2026-01-13 10:03:00
Valid until
2026-04-13 10:02:59
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-03-11 12:43:50 UTC
Collection source
PhishDestroy collector
Certificate fingerprint1f0300c4cc107a64a1749784607a15a2aad6a99b59b286a708425045961c6f6fCertificate names · 1 SANs
aavev4.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:31:28 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-15 22:18:16 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.
Technologies · 4 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.
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.
Domain Status Transition2026-09-25 01:31:05 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
duplicate-disabled-6647.invalid detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Jun 6, 2026
Time to First Unavailability
3921 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+
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.
4 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(HK)
