Malicious Code Injection in dear_kangaroo_requirement Package
Summary
MAL-2025-93932: Malicious code in dear_kangaroo_requirement (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 dear_kangaroo_requirement package is part of the npm ecosystem, often used in JavaScript projects for managing dependencies. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with altered metadata.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the dear_kangaroo_requirement package. This code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages. The ramifications include compromised project integrity and potential exposure to further attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dear_kangaroo_requirementIf 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 dear_kangaroo_requirement package from your project by executing: npm uninstall dear_kangaroo_requirement. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The dear_kangaroo_requirement package has been identified as containing malicious code that poses significant risks to developers using it. Immediate action is required to update or remove the package to safeguard your projects. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.
See every vulnerability recorded for dear_kangaroo_requirement →
FAQ
The malicious code can alter your project's package.json, leading to potential security vulnerabilities and the risk of using compromised packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
The payload continuously republishes variants of the package, which can clutter the npm registry and make it difficult to find legitimate packages.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time, ensuring you are alerted to any issues as they arise.
