Malicious Code Exploit in ruling_narwhal_requirement Package
Summary
MAL-2025-96421: Malicious code in ruling_narwhal_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 ruling_narwhal_requirement package is part of the npm ecosystem, often utilized 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 automatically generate and publish derivative packages with altered names and configurations, which can lead to significant security risks for developers and their projects.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the ruling_narwhal_requirement package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores through the creation of numerous derivative packages, which can clutter the npm registry and potentially introduce security risks to users who unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ruling_narwhal_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 ruling_narwhal_requirement package from your project by executing the command: 'npm uninstall ruling_narwhal_requirement'. This will prevent any potential exploitation until a patched version is available.
Conclusion
The ruling_narwhal_requirement package poses a significant security risk due to its malicious code that alters package configurations and publishes derivative packages. It is crucial for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for ruling_narwhal_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity.
You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
