Malicious Code Injection in Comprehensive Rook Requirement Package
Summary
MAL-2025-93693: Malicious code in comprehensive_rook_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 'comprehensive_rook_requirement' package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing of variants with altered metadata.
Vulnerability Detail
The vulnerability stems from the package's association with a malicious campaign that modifies the 'package.json' file to remove private flags, changes version numbers, and generates random package names. This results in the continuous republishing of these variants, which pollutes the npm registry and can lead to security risks for developers who unknowingly use these compromised packages. The malicious payload is embedded within the package, making it a significant threat to the integrity of npm.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall comprehensive_rook_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 measure, you can avoid using the 'comprehensive_rook_requirement' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'comprehensive_rook_requirement' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the integrity of their applications.
See every vulnerability recorded for comprehensive_rook_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.
Using this package can lead to security risks, including the potential for your project to be associated with malicious activities and the pollution of the npm registry.
You should remove the package immediately and check for any other dependencies that may have been affected.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
