Malicious Code Injection in lengthy_kangaroo_blush-2 Package
Summary
MAL-2025-105072: Malicious code in lengthy_kangaroo_blush-2 (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 lengthy_kangaroo_blush-2 package is part of the npm ecosystem, often used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability originates from the package being part of a token reward campaign that utilizes malicious scripts to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may inadvertently expose their projects to malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lengthy_kangaroo_blush-2If 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 lengthy_kangaroo_blush-2 package from your project by executing: npm uninstall lengthy_kangaroo_blush-2. This will prevent any malicious code from executing in your application until a secure version is available.
Conclusion
The lengthy_kangaroo_blush-2 package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to stay vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for lengthy_kangaroo_blush-2 →
FAQ
The malicious code modifies package.json files to remove private flags and republish variants with random names, which can lead to security vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using this package can expose your application to malicious code, potentially compromising your project's security and integrity.
Regularly update your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
Immediately uninstall the package and check for any other dependencies that may have been affected. Consider using a secure alternative.
