Malicious Code Injection in progressive_shrew-appteadev Package
Summary
MAL-2025-107332: Malicious code in progressive_shrew-appteadev (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The progressive_shrew-appteadev package is part of the npm ecosystem, typically used for various development purposes. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability in the progressive_shrew-appteadev package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of derivative packages, polluting the npm registry and potentially compromising the integrity of dependent applications. The malicious payload is designed to exploit the npm ecosystem, making it crucial for developers to be aware of this risk.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall progressive_shrew-appteadevIf 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, consider removing the progressive_shrew-appteadev package from your project if it is not essential. You can do this by executing the following command: npm uninstall progressive_shrew-appteadev. Additionally, monitor your package-lock.json file for any unexpected changes.
Conclusion
The progressive_shrew-appteadev package has been identified as a vector for malicious code injection, posing significant risks to applications relying on it. Developers are urged to update or remove this package and utilize tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for progressive_shrew-appteadev →
FAQ
The vulnerability involves malicious code that modifies package metadata and floods the npm registry with harmful variants.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.
If updating is not possible, consider removing the package from your project and replacing it with a safer alternative.
This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
