Malicious Code Injection in vicarious_wildebeest_requirement Package
Summary
MAL-2025-97254: Malicious code in vicarious_wildebeest_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 vicarious_wildebeest_requirement package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that exploits npm's publishing system. This package is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the vicarious_wildebeest_requirement package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, often themed around Indonesian culture. The malicious scripts are designed to continuously republish these variants, which can lead to a compromised npm registry, affecting developers who rely on the integrity of the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vicarious_wildebeest_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 avoid using the vicarious_wildebeest_requirement package until a fixed version is released. Additionally, consider using npm audit to identify and mitigate vulnerabilities in your project.
Conclusion
The vicarious_wildebeest_requirement package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to stay informed about such vulnerabilities and take immediate action to mitigate potential risks by updating or removing affected packages.
See every vulnerability recorded for vicarious_wildebeest_requirement →
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 pollution of the npm registry, potentially compromising the integrity of your project's dependencies.
You should immediately update the package to a patched version or remove it from your project to prevent any malicious activity.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
