Malicious Code Injection in liable_mongoose-appteadev Package
Summary
MAL-2025-105111: Malicious code in liable_mongoose-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
Background
The liable_mongoose-appteadev package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. These packages are designed to manipulate developer reputation scores through automated publishing of derivative packages, which can lead to significant security risks.
Vulnerability Detail
The vulnerability originates from the package being part of a token reward scheme that employs malicious scripts to modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to trust legitimate packages. The ramifications include potential exposure to malicious code and compromised application integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall liable_mongoose-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, you can avoid using the liable_mongoose-appteadev package altogether. If it is already in use, consider replacing it with a reputable alternative that provides similar functionality without the associated risks.
Conclusion
The liable_mongoose-appteadev package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for liable_mongoose-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the injection of malicious code, compromising the security and integrity of your application.
You should remove the package from your project and consider using a safer alternative.
Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
