Malicious Code Injection in qualified_cattle_requirement Package
Summary
MAL-2025-96136: Malicious code in qualified_cattle_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 qualified_cattle_requirement package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a dependency for JavaScript projects, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the qualified_cattle_requirement package, which is designed to automatically generate and publish derivative packages with randomized names. This is achieved through scripts that modify the package.json file by removing private flags, changing version numbers, and creating random package names. The ramifications include the pollution of the npm registry, potential security risks for developers using these packages, and the inflation of developer reputation scores for the tea protocol token rewards. This malicious behavior can lead to unintended consequences for projects relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall qualified_cattle_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 qualified_cattle_requirement package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unexpected changes or additions.
Conclusion
The qualified_cattle_requirement package has been identified as a source of malicious code that can compromise the integrity of projects using it. Developers should take immediate action to remove this package and monitor their dependencies for any related vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your projects.
See every vulnerability recorded for qualified_cattle_requirement →
FAQ
It is an npm package that has been compromised to include malicious code aimed at manipulating package metadata and inflating developer reputation scores.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.
Using compromised packages can lead to security vulnerabilities, data breaches, and the potential for your project to be affected by malicious scripts that can alter your codebase.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.
Immediately uninstall the qualified_cattle_requirement package and review your project for any potential impacts. Consider replacing it with a safer alternative.
