Which versions of aave-improvement-process are malicious?

The following npm versions of aave-improvement-process are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate aave-improvement-process if I installed it?

Remove aave-improvement-process from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed aave-improvement-process — how do I know if it already compromised me?

If aave-improvement-process was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is aave-improvement-process part of a known attack campaign?

Yes — aave-improvement-process is associated with the RLMA-2025-03757, RLUA-2026-10672 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find aave-improvement-process across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aave-improvement-process (version 99.99.99).

Malicious package

aave-improvement-processnpm

Advisory published Jul 31, 2025Updated Sep 24, 2026

aave-improvement-process is a confirmed malicious npm package (MAL-2025-6395) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aave-improvement-process (npm)

MAL-2025-6395

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall aave-improvement-process

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

d3cb3ab00a483e2407026ddf8f5696e57c852e37c2262b711f8c7142ae73686f

74a098f57f8f9d8439db2b04d98a093783e8dfea3efc6790cd09c6a7a84a0a44

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for aave-improvement-process (version 99.99.99).
If you installed it — respond
Remove aave-improvement-process from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If aave-improvement-process was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. aave-improvement-process on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03757RLUA-2026-10672

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks aave-improvement-process-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database