Malicious Code Injection in various_ocelot_requirement Package
Summary
MAL-2025-97234: Malicious code in various_ocelot_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 'various_ocelot_requirement' package is part of the npm ecosystem, typically used for managing dependencies in JavaScript applications. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. It is designed to automatically publish variants of itself with altered names and configurations, making it susceptible to exploitation.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'various_ocelot_requirement' package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants to the npm registry, leading to potential pollution of the registry and compromising the integrity of the software supply chain. The ramifications include unauthorized access to sensitive data and the potential for further exploitation of dependent applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall various_ocelot_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 prevent the installation of this malicious package by using the following command to uninstall it: 'npm uninstall various_ocelot_requirement'. Additionally, consider using npm audit to identify and address vulnerabilities in your dependencies.
Conclusion
The 'various_ocelot_requirement' package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial to take immediate action by updating or removing the package to mitigate risks associated with this vulnerability.
See every vulnerability recorded for various_ocelot_requirement →
FAQ
The malicious code modifies the package.json file to remove private flags and generates random package names, leading to unauthorized republishing on the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any installation.
The risks include potential unauthorized access to sensitive data, pollution of the npm registry, and exploitation of dependent applications.
Regularly audit your dependencies using tools like npm audit and monitor for updates or patches to known vulnerabilities.
If you cannot update the package, consider removing it from your project and replacing it with a safer alternative.
