Malicious Code Injection in good_ocelot_requirement Package
Summary
MAL-2025-94713: Malicious code in good_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 good_ocelot_requirement package is part of the npm ecosystem, commonly used for managing dependencies in JavaScript applications. This package, like many others, is intended to facilitate the development process by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system, leading to significant security concerns.
Vulnerability Detail
The vulnerability originates from the good_ocelot_requirement package being associated with a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry, potentially affecting other developers and applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall good_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 remove the good_ocelot_requirement package from your project until a secure version is released. You can do this by executing the following command: npm uninstall good_ocelot_requirement.
Conclusion
The good_ocelot_requirement package has been identified as a vector for malicious code injection, posing significant risks to applications that utilize it. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their projects.
See every vulnerability recorded for good_ocelot_requirement →
FAQ
It is an npm package used for managing dependencies in JavaScript applications, but it has been compromised with malicious code.
The malicious code can modify your package.json file, potentially leading to security breaches and instability in your application.
You should uninstall the package immediately and monitor for any updates or patches that address this vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
