VirusTotal
12 / 91 engine detections
보고서 열기“Aave Wallet for Desktop | Self-Custody Aave Portfolio”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@key-systems.net.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
aavewallet.org — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: Aave; 사기 유형: Impersonation. 증거 요약: VirusTotal 12/91 (alphaMountain.ai, BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker); URLQuery 1 alert; Spamhaus DBL_SPAM; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. 등록기관: Key-Systems.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
12 / 91 engine detections
보고서 열기1 threat-system alert
보고서 열기DBL_SPAM
no community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | aavewallet.org |
malicious | Sinkholed |
AI-assisted evidence review
aavewallet.org impersonates Aave, the DeFi lending protocol, and presents itself as "Aave Wallet for Desktop | Self-Custody Aave Portfolio." It targets Aave users and crypto holders looking for an official app to manage their positions. PhishDestroy first saw it on 2026-09-19. As of 2026-10-19 the site was still online and serving its content.
Aave is a protocol, not a wallet vendor, so a branded desktop wallet promising self-custody of an Aave portfolio is the lure. Pages like this usually lead visitors to a downloadable installer or to an import screen that asks for a recovery phrase or private key, framed as setting up or restoring the wallet. Anyone who hands over a seed phrase gives the operators full control of that wallet, and they can sweep every asset on every chain it holds. A fake desktop installer can also carry malware that searches the computer for wallet files and stored credentials.
On 2026-09-29, 12 of 91 VirusTotal engines flagged the domain, including alphaMountain.ai, BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. That is a minority of engines, but the names cover both commercial and threat-intelligence vendors. The domain also appears on the MetaMask and SEAL blocklists alongside PhishDestroy, which means wallet users there may see warnings before the page loads. Spamhaus lists it in its Domain Block List as spam (DBL_SPAM).
The domain was registered on 2026-07-11 through Key-Systems GmbH, about 70 days before PhishDestroy detected it. That gap leaves room for the domain to be staged or promoted before it attracts attention. The site is hosted on HIVELOCITY, Inc. infrastructure in the US. Its Let's Encrypt certificate gives it a browser padlock, which proves nothing about who runs the site.
If you downloaded and ran a "desktop wallet" from this site, disconnect the machine from the network, scan it with up-to-date security software, and treat every wallet and saved password on it as exposed. If you entered a recovery phrase or private key, create a new wallet on a clean device and move any remaining funds there immediately. The old phrase cannot be secured again. Use only Aave's official interface reached through a bookmarked address, with a wallet from a trusted vendor. Defenders should block the domain at DNS and proxy level and flag "Aave Wallet" desktop downloads in endpoint and mail filtering.
urlscan.io scan and screenshot: https://urlscan.io/result/01a0b886-8b86-7659-8240-5c58417f46cd/
VirusTotal report: https://www.virustotal.com/gui/domain/aavewallet.org
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=aavewallet.org
Archived copy: https://web.archive.org/web/20260919071007/https://aavewallet.org/
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
Last checked
ns3.my-ndns.comns4.my-ndns.comLocation describes the IP network.
b9f9b24ba7103cc06d3246919271743e863431cf9678e0a56049add93fa4828dwww.aavewallet.orgSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.aavewallet.orgDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of aavewallet.org · checked Sep 19, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
aavewallet.org
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
No threat flag
View source12/91 engine detections
View sourcePD-20260919-DA2ABA
Page captured
View sourceaavewallet.org
View source저장된 유사 도메인 95개
PD-20260919-DA2ABA Recipient: abuse@key-systems.net Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (US): 18 U.S.C. § 1343 - Wire Fraud 18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA) 15 U.S.C. § 45 - FTC Act (Deceptive Practices) Federal laws prohibit wire fraud, computer fraud, and deceptive business practices. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
aavewallet.org)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.