Critical Malicious Code Vulnerability in aave-improvement-process Package

aave-improvement-process Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6395: Malicious code in aave-improvement-process (npm). Affects aave-improvement-process versions 99.99.99. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The aave-improvement-process package is an npm library designed to facilitate enhancements and proposals within the Aave ecosystem. It serves as a platform for developers to contribute to the evolution of Aave's protocols. However, this package has been found to contain malicious code that poses significant security risks to users and their applications.

Vulnerability Detail

The vulnerability identified as MAL-2025-6395 originates from a malicious version of the aave-improvement-process package (version 99.99.99). This version includes harmful code that could compromise the security of applications utilizing it, potentially leading to unauthorized access, data breaches, or other malicious activities. The presence of this code can severely impact the integrity and confidentiality of user data.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall aave-improvement-process

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can remove the aave-improvement-process package from your project until a secure version is released. You can do this by running: npm uninstall aave-improvement-process.

Conclusion

The aave-improvement-process package has been compromised with malicious code, posing serious risks to users. It is essential to update or remove the package to safeguard your applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for aave-improvement-process →

Share this vulnerability

FAQ

It is an npm library that allows developers to propose and implement improvements within the Aave ecosystem.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can provide real-time alerts for vulnerabilities.

Consider removing the package as a temporary measure until a secure version is available.

Detailed information is available on the ReversingLabs GitHub repository and the Open Source Vulnerability database.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall aave-improvement-process

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback